Hi dims, I opened a bug report on this: AXIS2-1931 In the meantime I completely got stuck. I'm nearly a newbie and I always used Axis for both server & client side and everything went smooth.
My only workaround is to manually change the JBoss client generated classes ( 44 classes :-( ) substituting "return" with "_return". While it's a temporary solution and it works, it prevents me from automate the creation process with ant. So I though to another naive solution... #1 I start from the wsdl automagically generated by axis. #2 I manually change the parameter named "return" with "_return" inside the wsdl. #3 I put the modified wsdl inside my service under the META-INF folder and I add: <parameter name="useOriginalwsdl">true</parameter> inside the service.xml. #4 I can see the exposed service and my wsdl (slightly modified) #5 I save the wsdl and I generate the client artifacts form the new exposed wsdl. The client generation process goes flawlessly, but... When I try to communicate, on the client side, I get a javax.xml.soap.SOAPException: Could not transmit message. Where I'm wrong? What I'm missing? BTW I noted that while still having my custom wsdl under META-INF, if I set useOriginalwsdl to false, I get exposed a still different wsdl: a sort of mix between my custom and the automatic generated wsdl. Is this correct? I though I should get the automatic one. Thank you in advance -- Davide -- View this message in context: http://www.nabble.com/WSDL-output-parameter-named-%22return%22-tf2913042.html#a8156701 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
