views:

106

answers:

0

hi,

I've got a problem with axis2' backward compatibility. The problem is next: there's need to migrate from axis1 on axis2 w/o changing clients.

Since I have WSDL this must not be a problem. Right? So, the only things to do: adjust axis2' stuff like libraries and configuration infrastructure.

I created all required infrastructure: libs, xml configs, put this all on right places, checked that axis2 returns given__ WSDL and not automatically generated one. So with this axis2 changes I expected from service usage to get very similar, identical xml-responses - but unfortunatelly w/o a luck. The core problem(and my personal confuse) - axis2 return xml-response which my axis1' clients can't understand, the response is totally different from what specified in given WSDL and from what clients expect.

I'm new in web-services kitchen, so my assumptions could be wrong. Please help.