1.) Are you using rpc/encoded instead of doc/lit or rpc/lit? JAX-WS doesn't support rpc/encoded (unless you want to use the rather unpleasant Provider interface - http://www.jroller.com/gmazza/entry/calling_rpc_encoded_web_services).
2.) What databinding framework are you using? I don't think CXF supports all that XFire does, so that may be another consideration. Are you ready for JAXB? 3.) Can you keep your legacy service running while you implement a noncompatible new series? If you can, that will allow you to take advantage of the best CXF has to offer and get things done right the first time, rather than tying one hand behind your back as you try to maintain backwards compatibility with the older web services stack. 4.) Here's some Maven and Ant scripts that can help simplify your wsdl2java generation: http://www.jroller.com/gmazza/entry/web_service_tutorial HTH, Glen 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 > -- View this message in context: http://old.nabble.com/Switching-from-code-first-to-contract-first-tp28466960p28468632.html Sent from the cxf-user mailing list archive at Nabble.com.
