On 28/01/15 12:20, srinivas thallapalli wrote:
Basically what I am trying to do is, I have some SOAP services and I want
write an engine which can give the REST resources for those SOAP services.
The input to SOAP to REST is only the WSDL.
I am trying to find, if there are any best practices to do this.
Well, we don't support WSDL for describing REST applications, but if you
do WSDL-first for SOAP then you might consider using a no-annotations
feature:
http://cxf.apache.org/docs/jax-rs-advanced-features.html#JAX-RSAdvancedFeatures-RESTfulserviceswithoutannotations
So you'd generate your SOAP interfaces with WSDL and then attach an
additional model that would also get that services exposed over plain
HTTP, without you having to modify the interfaces.
There are limits there but it can work.
The demo is here:
https://github.com/Talend/tesb-rt-se/tree/master/examples/cxf/jaxrs-jaxws-description-first
Sergey
Thanks
--
View this message in context:
http://cxf.547215.n5.nabble.com/Guidelines-to-develop-Rest-interface-for-SOAP-services-tp5753652p5753663.html
Sent from the cxf-user mailing list archive at Nabble.com.
