Your contract-first solution would be my best suggestion. I just hope that XFire was generating an accurate WSDL.
On Wed, Feb 2, 2011 at 2:04 PM, loic paillotin <[email protected]> wrote: > > Hello, > > Following my previous question, I got my Xfire service to work under CXF > relatively painlessly. > > The problem I have is that the WSDL generated is slightly different which is > a bit of a pain since the client side is a perl client using SOAP::Lite, > that is quite franlky quite painful to adapt to the new WSDL. > > Right now, the only solution I see is adding annotations everywhere to try > make my CXF WSDL conform to the XFire WSDL, hoping that it is even possible. > > Changing the perl client would be a last resort. > > Another idea I had was pretty much start a new service "wsdl first" using my > XFire WSDL, and hook up the generated code to my Xfire implementation. > > Has anybody had this kind of problem and figured out what is the least > painful path? > > Thanks a lot in advance, > > Loïc. > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Porting-a-Xfire-soap-service-to-CXF-what-is-the-best-methodology-tp3368292p3368292.html > Sent from the cxf-user mailing list archive at Nabble.com. >
