Hi Sergey,
I posted directly to the camel mailing list .
=== snippet from response to camel mailing list ====
I added a few features to the CXF code generator in Swagger-Codegen
(bean-validation-api support, CXF3 Swagger2Feature for complimentary
code first support, generate test classes, added pom.xml for server,
spring is used for configuration of CXF3).
However, my PR is still pending:
https://github.com/swagger-api/swagger-codegen/pull/3281
If you like to run it, give it a try.
You can find the current feature list here:
https://github.com/swagger-api/swagger-codegen/wiki/Server-stub-generator-HOWTO
Pls let me know how you are doing with it...
=== snippet from response to camel mailing list ====
This generator could be filling the blanks missing at the wadl2java,
especially as it is way easier to add additional features there (I
understand JAXB processing is a bit more intense).
I added features to generate the complete runnable server including the
beanvalidation-annotations, so you can immediately start coding.
I think it would be nice to add further switches for all the nice
features you added to CXF3 so people can generate the working CXF server
without having to dive into detail immediately... What do you think?
Shall I create a separate post here to discuss it?
BTW I already sent the ICLA, can you give green light to Craig?
I think it would be nice to have a contract first/code first example
with wadl2java and with swagger (using the swagger-codegen), so people
can try both ways.
Best regards,
Johannes
Am 01.09.2016 um 23:03 schrieb Sergey Beryozkin:
Hi Johannes
I believe you are well aware of the current status of Swagger Codegen
supporting CXF - can you please reply to this thread:
http://camel.465427.n5.nabble.com/CXFRS-swagger-integration-td5787041.html
if you can get a chance. Or may be reply here and I will post a link
to it in that thread.
By the way I thought it would generate JAX-RS interfaces only, right ?
And may be the beans out of JSON schemas ?
Thanks, Sergey
