As long as you don't change the WSDL, migration from Axis 1 to Axis 2 should be seamless. (i.e., use the WSDL-First approach to building the new service implementation)
Likewise, just generate a new stub for your client using Axis2. Anne On 7/21/06, Prasad Chaudhari <[EMAIL PROTECTED]> wrote:
Hi All, I have two questions regarding migration.. 1) I have a webservice running in our production using axis1.1. It is a message style simple webservice with a service method definition public void method(SOAPEnvelope req, SOAPEnvelope resp); I have one .NET external client at the moment actively using this webservice. If I rewrite this using axis 2.0, will the existing webservice client (.NET) will work without changing anything? I hope this issue is already addressed as normally applications can have webservices running on axis1.x and they would like to migrate to axis2.0 without bothering their external clients for this change. 2) Also I have a client using axis1.1 which connects to 10 difft. webservices using axis(I do not know version), php and .NET. What will happen if I migrate my client to axis2.0. Will it work with all webservices or there will be compatiblity issue. Best Regards, -Prasad
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
