[ http://issues.apache.org/jira/browse/AXIS2-1338?page=all ]

Amila Chinthaka Suriarachchi updated AXIS2-1338:
------------------------------------------------

    Attachment: ADBBeanTemplate.xsl-patch-111006.txt

fixed the default element serialization and deserialization problems.

> 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.wsdl
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to