Hi Jason,
You may find Jibx2Wsdl
(http://jibx.sourceforge.net/fromcode/jibx2wsdl.html) useful as a way of
generating a clean doc/lit WSDL from your existing service. It has some
nice features, including converting JavaDocs for your service class and
methods and data classes into WSDL and schema documentation. There's
also a tutorial on the schema-from-a-data-model part here:
http://www.ibm.com/developerworks/java/tutorials/j-jibx1/
Jibx2Wsdl also generates JiBX bindings for your data classes, and if you
use a compatible web services stack (such as Axis2, or JiBX/WS if you
don't need WS-* technologies) you can use these bindings to work
directly with your existing classes. Support for using JiBX with CXF is
in progress, but probably won't be usable for some time.
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Jason Horne wrote:
I have an existing application that uses XFire 1.2.6 to expose web services via the "code
first" model. We now need to switch to a "contract first" model, without breaking
any clients that are using the existing web services.
Any suggestions on how to go about doing this?
I saved a copy of the XFire-generated WSDL and ran the CXF "wsdl2java" tool
against it, but it seems like there has to be a better way. The application has
interfaces for all of the classes exposed by XFire-can we take advantage of those?
Thanks for any help.
Jason
