axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXISCPP-91) An input message part and output message part cannot be the same element
Date Mon, 13 Sep 2004 01:57:37 GMT
The following comment has been added to this issue:

     Author: Samisa Abeysinghe
    Created: Sun, 12 Sep 2004 6:57 PM
Please attach sample WSDL file to help fix the problem
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXISCPP-91
    Summary: An input message part and output message part cannot be the same element
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis-C++
             WSDL generation
             1.1 Final

   Reporter: Steve Cheng`

    Created: Tue, 18 May 2004 10:23 AM
    Updated: Sun, 12 Sep 2004 6:57 PM
Environment: Axis C 1.1.1


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 name="EchoOutput">
		<part element="tns:myBean" name="result"/>

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

Here's the output of running it through wsdl2ws:

############## the type found ={
Exception in thread "main" org.apache.axis.wsdl.wsdl2ws.WrapperFault: unregister
d type {}>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:


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.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message