[AXISCPP-91] An input message part and output message part cannot be the same element

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1 Final
• Fix Version/s: 1.3 Final
• Component/s: WSDL processing - RPC
• Environment: Axis C 1.1.1; Windows
• Assignee: Unassigned
• Reporter: Steve Cheng`
• Created: 18/May/04 17:23
• Updated: 28/Oct/04 09:29
• Resolved: 28/Oct/04 09:29

Description

If the WSDL port operation uses messages that are the same element type, wsdl2ws chokes. Here's an example of such a case:

<message name="EchoInput">
<part element="tns:myBean" name="request"/>
</message>

<message name="EchoOutput">
<part element="tns:myBean" name="result"/>
</message>

<portType name="EchoPortType">
<operation name="echo">
<input message="tns:EchoInput"/>
<output message="tns:EchoOutput"/>
</operation>
</portType>

Here's the output of running it through wsdl2ws:

1

1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. the type found ={http://www.acme.com
                                          }>myBean
                                          Exception in thread "main" org.apache.axis.wsdl.wsdl2ws.WrapperFault: unregister
                                          d type {http://www.acme.com}

                                          >myBean refered
                                          at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceInfo(Unknown Source)
                                          at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.genarateWrappers(Unknown Source)

at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(Unknown Source)

I traced the issue back to WSDL2Ws.getServiceInfo(). There's a call to remove the type that represents the wrapping element:

this.typeMap.removeType(qname);

The typeMap has the type >myBean prior to this call. When the loop iterates through again to process the return type, it can no longer find >myBean.