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=15191>. 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=15191 WSIF incompatibility with JAX-RPC rules Summary: WSIF incompatibility with JAX-RPC rules Product: Axis-WSIF Version: unspecified Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Basic Architecture AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] WSIF is incompatible with JAX-RPC rules for mapping a WSDL port type to a java interface. When WSIF is used to invoke an operation of the port type, the name of the operation must *exactly* match the name specified in the WSDL. WSIF then uses this information to look up a java method of that name in the available stub interface. The problem here is that if the stub interface was generated using WSDL2Java or some other JAX-RPc compliant tool, the name of the method may not exactly match - JAX-RPC XML to Javanaming rules are applied, which means for example if the operation was called "GetQuote", the generated interface will have a method called "getQuote" (since the rules say that the java method names must begin with a lower-case letter. WSIF will be unable to find a method with the name it thinks should be there. We need to fix WSIF to apply JAX-RPC naming rules when making method invocations on stub interfaces.
