I migrated my web service from axis2-1.2 to axis2-1.6.1 and have the following anomalie now:
There are 3 methodes Login Fktmap Logout Resulting in a Action urn:login, urn:fktmap urn:logout As a response from axis2-1.2 I got always urn:login urn:fktmap urn:logout As a response from axis2-1.6.1 I get new urn:loginResponse urn:fktmapResponse urn:logoutResponse So that has changed from axis2-1.2 to axis2-1.6.1 what ever is correct I don't mind !!! For me the interface between the two has changed dramatically with a for us very unplesant side effect which we don't know how to handle at the moment. Because: My client is a Visual Basic .NET with transport dlls in Visual C#.NET based on WCF 3.5 The generated stub expects urn:login and urn:login with the response too. But now gets urn:loginResponse instead adding "Response" to all action elements And fails to deliver ofcourse. I have fixed my stub to expect for a urn:login action a urn:loginRespons action back and that works BUT - we have a lot of operating servers and we have only 3 client codse release cycles per year! We have now old axis2-1.2 based services behaviour which deliver urn:login action for Request and Response And we have new axis2-1.6.1 based behaviour which concatenates to each request action code the word Response on a return from server. I can not reconstruct my client to deal with 2 DLL's one expecting urn:login the orther expecting urn:loginRespons as action back from server. Question: How can I prevent Axis2-1.6.1, from returning urn:loginResponse but retruning urn:login only NOTE: no WSDL was used for code generation at all, all is just java coded using OMElement very much as the examples in axis2 samples do. Josef
