You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are planning to leverage jsonschema2pojo within a microservice project. The goal is to be able to integrate our individual microservices using only their respective schemata, without sharing any jars between the services. This library is a great fit for that, with one little snafu: our schemata are currently stored behind a RESTful api. Ideally, we'd like to be able to specify a http url as the schema source, and generate the POJOs from there. Something like this:
Currently, this doesn't work because the GenerationConfig interface is expecting a list of java Files. However, since further downstream the ContentResolver seems to accept a URL, this seems like it would be a trivial issue to address.
Is this already being worked on?
The text was updated successfully, but these errors were encountered:
We are planning to leverage jsonschema2pojo within a microservice project. The goal is to be able to integrate our individual microservices using only their respective schemata, without sharing any jars between the services. This library is a great fit for that, with one little snafu: our schemata are currently stored behind a RESTful api. Ideally, we'd like to be able to specify a http url as the schema source, and generate the POJOs from there. Something like this:
Currently, this doesn't work because the GenerationConfig interface is expecting a list of java Files. However, since further downstream the ContentResolver seems to accept a URL, this seems like it would be a trivial issue to address.
Is this already being worked on?
The text was updated successfully, but these errors were encountered: