What I would do in your situation is: Why not paly that migration in small steps and learn. Take one of the CL/SV examples and build it to use RPC Style. Then if CL/SV are running, change the server side only to Document Style and look what happens. Also very informational and nearly a must have with this two examples is the use of a TCP monitor or Wireshark in-between CL/SV to see the wire protocol.
Josef From: JERIL NADAR [mailto:jeril842...@gmail.com] Sent: Freitag, 5. Dezember 2014 13:34 To: java-user@axis.apache.org Subject: Axis 1.4.2 to Axis2 1.6 Migration Hi, I got your mail id from your Axis migration page : http://axis.apache.org/axis2/java/core/docs/migration.html I have one quick question for you. Your help would be highly appreciated. Our project receives Webservice response from an external system. We have webservice clients written to send the request and receive the response/fault message accordingly. Till recently they were using Axis 1.4.2 but now are planning to move to Axis2 1.6. They are ready with the Webservice part and have shared their WSDL file. The operations remains the same but now they have moved from RPC style to Document style. So my question is if we continue to remain with the older client (axis 1.4.2) will it make any difference? If yes, what changes would be required from our side for the client code? Any help would be useful. -- Thanks, Jeril Nadar John 3:16
