Fir a spring-based API check out https://github.com/springfox/springfox/.
I’m not familiar enough with XMLBeans to tell you if it can work with it. From: 'Karishma Dalal' via Swagger <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, September 27, 2017 at 11:26 To: "[email protected]" <[email protected]> Subject: Re: Generate Swagger documentation during Runtime in J2SE legacy application We use JAVA Spring framework to expose our REST API. On Wed, Sep 27, 2017 at 11:21 AM, Ron Ratovsky <[email protected]> wrote: XMLBeans is used to describe the objects being transferred, not the API. Which framework do you use to expose your REST API? From: 'Karishma Dalal' via Swagger <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, September 27, 2017 at 11:20 To: "[email protected]" <[email protected]> Subject: Re: Generate Swagger documentation during Runtime in J2SE legacy application No, we do not want to describe SOAP, we want to use Swagger for REST. We already have REST in place but we want to provide something meaningful to customers - to describe the API. My point was that we use WSDL behind the scenes to generate XMLBeans. (We can overlook this, it was a workaround) Our next step is to get Swagger JSON from XMLBeans. Thanks, Karishma On Wed, Sep 27, 2017 at 11:12 AM, Ron Ratovsky <[email protected]> wrote: There’s no way to use Swagger/OpenAPI to describe SOAP APIs – it can only be used for REST. From: 'Karishma Dalal' via Swagger <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, September 27, 2017 at 11:07 To: "[email protected]" <[email protected]> Subject: Re: Generate Swagger documentation during Runtime in J2SE legacy application Hi Ron, Thanks for getting back and apologies for the late response. We use WSDL and XSD as service descriptors on JAVA Spring framework - J2SE. I understand WSDL is for SOAP operation but its a legacy tool and WSDL is mandatory for creating bindings. We convert WSDL into XMLBeans. Further, we use Jettison library for conversion of XML to JSON and back. We wish to find a way to generate Swagger JSON from XMLBeans. What can be the best approach to it ? Please suggest! Also please feel free to point if I am missing out on something. Thanks, Karishma On Fri, Sep 15, 2017 at 3:05 AM, Ron Ratovsky <[email protected]> wrote: How are your REST endpoint implemented then? From: 'KD' via Swagger <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Thursday, September 14, 2017 at 01:55 To: Swagger <[email protected]> Subject: Generate Swagger documentation during Runtime in J2SE legacy application Hi Swagger team, I would like to know ways to generate Swagger documentation during Runtime for J2SE legacy application that has REST implementation and support. We have used Jettison as a library for JSON object conversion. We dont have JAX-RS library (Jersey implementation, J2EE) for which I see many plugins available online. We have all the necessary information for Swagger specs that are - host, port, scheme, basePath, paths, operations and definitions. If someone can help me on these lines to generate swagger.json file, that would be great! -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "Swagger" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/swagger-swaggersocket/vp8I52qxZdc/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "Swagger" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/swagger-swaggersocket/vp8I52qxZdc/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "Swagger" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/swagger-swaggersocket/vp8I52qxZdc/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
