I’ve briefly taken the RAML-to-JAX-RS module and generated some JAX-RS output with it. In the past I’ve worked with SDKs that provided POJO classes that allowed me to construct the request body in code, rather than piecing together an XML or JSON string from dynamic bits building up a final String body to send. Likewise, the SDKs converted responses into POJO objects that made it easy with code to deal with the responses, rather than having to parse xml or json directly. The current RAML-JAX-RS does not generate POJOs from any of the listed schemas in the RAML file. I am therefore starting a project using the RAML-to-Java module, to then get the list of all schemas and “attempt” to generate POJOs from those schemas. Presently I am looking to use the XJC classes in my code if an XSD is listed, and if the schema is json, I am looking to possibly use the jsonschema2pojo.org to try to convert json schema to pojos. I wanted to reach out before I got too involved to make sure another effort isn’t under way already and/or if this is something that would be useful to others. I do understand that some API developers may resort to using something like https://apimatic.io/ which supports RAML files, to generate client SDKs for different languages. However I still find that this is not as useful to me as generating POJOs from our schemas and providing an SDK with the POJOs being used. I also feel that generating POJOs and using them both client side and server side validates the schemas are correct. It also sets up the ability to use the POJOs in generated test automation code as well.
Anyway, wanted to see what others things, if this is something others need or would want, any arguments against it (and why)?