Hi Glen, We're using document/literal. XFire is using Aegis binding, but we're not wed to that. What do you mean by being "ready" for JAXB? I'm inclined to say "yes" but I don't really know what that would mean. :-)
Keeping the old legacy services running in parallel with the new ones is a possibility, although we'd obviously prefer not to do that. Thanks for the Maven and Ant scripts--those could be helpful. Jason -----Original Message----- From: Glen Mazza [mailto:[email protected]] Sent: Wednesday, May 05, 2010 10:16 PM To: [email protected] Subject: Re: Switching from code-first to contract-first 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
