axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-1338) Code generation drops the element which holds an xsd:anyType element at both client and server sides
Date Thu, 12 Oct 2006 20:47:37 GMT
     [ http://issues.apache.org/jira/browse/AXIS2-1338?page=all ]

Davanum Srinivas resolved AXIS2-1338.
-------------------------------------

    Resolution: Fixed

Marking as fixed.

thanks,
dims

> Code generation drops the element which holds an xsd:anyType element at both client and
server sides
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1338
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1338
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>         Environment: Axis2 1.1 RC-1
>            Reporter: Asankha C. Perera
>         Attachments: AbstractTestCase.java, ADBBeanTemplate.xsl-patch-111006.txt, ComplexEchoServiceSkeleton.java,
ComplexEchoServiceTest.java, echo-good.xml, echo.wsdl, echo.xsd
>
>
> The following is a fragment from the WSDL used (attached to the JIRA). The element "value"
is of type xsd:anyType
> 			<complexType name="NamedValue">
> 				<sequence>
> 					<element name="name" nillable="true" type="xsd:string"/>
> 					<element name="value" nillable="true" type="xsd:anyType"/>
> 				</sequence>
> 			</complexType>
> 			<complexType name="MyComplexType2">
> 				<sequence>
> 					<element name="username" type="xsd:string"/>
> 					<element name="password" type="xsd:string"/>
> 					<element name="options" type="tns1:NamedValue" maxOccurs="unbounded"/>
> 					<element name="userAttributes" type="tns1:AttributeRequest" maxOccurs="unbounded"/>
> 				</sequence>
> 			</complexType>
> Codegen using  -o <outputpath> -s -t -ss -sd -g -uri echo.wsdl and use attached
client and server skeleton implementations to test. 
> On TCPMon the SOAP request sent is as follows:
>             <ns1:options>
>                <ns1:name>Request NV1 name</ns1:name>
>                <foo:requestValue1 xmlns:foo="requestFoo" />
>             </ns1:options>
> When a correct request of the form shown below is sent to the server:
>             <ns1:options>
>                <ns1:name>Request NV1 name</ns1:name>
>                <ns1:value><foo:requestValue1 xmlns:foo="requestFoo" /></ns1:value>
>             </ns1:options>
> The server replies as:
> <ns1:MyElement2Response xmlns:ns1="http://types.echo.services" >
> <ns1:loginReturn>
> <ns1:name>Response NV1 name</ns1:name> 
> <bar:responseValue1 xmlns:bar="responseBar" /> 
> </ns1:loginReturn> 
> Again, thw WSDL defines the response as follows:
> 			<element name="MyElement2Response">
> 				<complexType>
> 					<sequence>
> 						<element name="loginReturn" type="tns1:NamedValue" maxOccurs="unbounded"/>
> 					</sequence>
> 				</complexType>
> 			</element>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message