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=22798>. 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=22798 Just one, buggy, Java mapping of a portType used in two bindings Summary: Just one, buggy, Java mapping of a portType used in two bindings Product: Axis Version: 1.1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: WSDL processing AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have a WSDL that uses a certain port type in multiple bindings --- exercising all four combinations of document vs. rpc and literal vs. encoded. WSDL2Java creates just one mapping for that port type, and that mapping does not compile (it references mappings of some complex types, but those mappings are not generated). The Axis User Guide, in the section on WSDL2Java, quotes JAX-RPC section 4.3.3, alleging that JAX-RPC says the name of the mapping of the port type is derived from the name of the binding if binding information is used. I cannot find that in my copy of JSR 101 Final Release version 1.0. The Axis User Guide goes on to explain that if the mapping of the port typ depends on the binding, then there will be a mapping per binding --- but that's not what happens.
