DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21519>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21519 doc/literal parameters used as service name Summary: doc/literal parameters used as service name Product: Axis Version: 1.1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Basic Architecture AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In the latest cvs build (and 1.1), it's line 181 of RPCProvider.java that seems to be choking -- a call to body.getMethodName() is returning "x" as the methodname whereas x should simply be a parameter and the method name should be "addNumbers". So, that said, given the following message generated by a .NET client (and one generated by an Axis client) -- is Axis acting appropriately when it assumes the method name is "x"? See the attached WSDL as well... It also appears as if Axis is seeing the number of n parameters as n - 1 in/around the same code (args = body.getParams();). .NET -------------------------------- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <soap:Body> <x xmlns="http://test.travelnow.com";>5</x> <y xmlns="http://test.travelnow.com";>2</y> </soap:Body> </soap:Envelope> Axis ----------------------------------- <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <x xsi:type="xsd:int" xmlns="http://test.xml.travelnow.com";>5</x> <y xsi:type="xsd:int" xmlns="http://test.xml.travelnow.com";>2</y> </soapenv:Body> </soapenv:Envelope>
