You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Sneha (JIRA)" <ax...@ws.apache.org> on 2009/07/06 11:46:14 UTC

[jira] Created: (AXIS-2795) Axis 1.4 support for complex type in SOAP request

Axis 1.4 support for complex type in SOAP request
-------------------------------------------------

                 Key: AXIS-2795
                 URL: https://issues.apache.org/jira/browse/AXIS-2795
             Project: Axis
          Issue Type: Bug
          Components: Serialization/Deserialization
    Affects Versions: 1.4
         Environment: Eclipse Ganymede
            Reporter: Sneha


Hi,

I am using Axis 1.4.

Onlines to the example samples/client/DynamicInvoker.java, I am creating a SOAP request stub from a given WSDL url and populating it with the argument s and then giving a call to invoke the function.

I have observed that if my request has an element of complex type, code throws a run time exception while trying to populate the parameters for the request, at its unable to fill in the complex type.

e.g. if part of my wsdl looks as below:

<xsd:schema targetNamespace="http://www.example.org/NewWSDLFile/">
−
<xsd:element name="NewOperation">
−
<xsd:complexType>
−
<xsd:sequence>
<xsd:element name="in" type="xsd:string"/>
<xsd:element name="NewElement" type="xsd:int"/>
<xsd:element name="NewElement1" type="xsd:int"/>
<xsd:element name="NewElement2" type="xsd:boolean"/>
<xsd:any/>
<xsd:element name="NewElement3" type="xsd:string"/>
<xsd:element name="NewElement4" type="xsd:string"/>
<xsd:element name="NewElement5" type="xsd:string"/>
<xsd:element name="NewElement6" type="xsd:string"/>
<xsd:element name="NewElement7" type="xsd:string"/>
<xsd:element name="NewElement8" type="xsd:int"/>
<xsd:element name="NewElement9" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
−
<xsd:element name="NewOperationResponse">
−
<xsd:complexType>
−
<xsd:sequence>
<xsd:element name="out" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
−
<wsdl:message name="NewOperationRequest">
<wsdl:part element="tns:NewOperation" name="parameters"/>
</wsdl:message>
−
<wsdl:message name="NewOperationResponse">
<wsdl:part element="tns:NewOperationResponse" name="parameters"/>
</wsdl:message>


If you observe the highlighted portion, NewOperationRequest, it has element, parameters, of type NewOPeration, which is of complex type.

My code give s a run time exception when I try to execute my code using this WSDL file, as  java.lang.RuntimeException: not know how to convert 'abc' into org.apache.axis.client.Call@b45130

Please help me find a solution on this problem, as most of my WSDL files include complex types for the requests.

Thanks in advance.
-- 
Sneha 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AXIS-2795) Axis 1.4 support for complex type in SOAP request

Posted by "Sneha (JIRA)" <ax...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sneha updated AXIS-2795:
------------------------

    Priority: Blocker  (was: Major)

Hey all,

Please give me some response over this issue. I am blocked at it and cant move ahead without any additional knowledge about the same.

> Axis 1.4 support for complex type in SOAP request
> -------------------------------------------------
>
>                 Key: AXIS-2795
>                 URL: https://issues.apache.org/jira/browse/AXIS-2795
>             Project: Axis
>          Issue Type: Bug
>          Components: Serialization/Deserialization
>    Affects Versions: 1.4
>         Environment: Eclipse Ganymede
>            Reporter: Sneha
>            Priority: Blocker
>
> Hi,
> I am using Axis 1.4.
> Onlines to the example samples/client/DynamicInvoker.java, I am creating a SOAP request stub from a given WSDL url and populating it with the argument s and then giving a call to invoke the function.
> I have observed that if my request has an element of complex type, code throws a run time exception while trying to populate the parameters for the request, at its unable to fill in the complex type.
> e.g. if part of my wsdl looks as below:
> <xsd:schema targetNamespace="http://www.example.org/NewWSDLFile/">
> −
> <xsd:element name="NewOperation">
> −
> <xsd:complexType>
> −
> <xsd:sequence>
> <xsd:element name="in" type="xsd:string"/>
> <xsd:element name="NewElement" type="xsd:int"/>
> <xsd:element name="NewElement1" type="xsd:int"/>
> <xsd:element name="NewElement2" type="xsd:boolean"/>
> <xsd:any/>
> <xsd:element name="NewElement3" type="xsd:string"/>
> <xsd:element name="NewElement4" type="xsd:string"/>
> <xsd:element name="NewElement5" type="xsd:string"/>
> <xsd:element name="NewElement6" type="xsd:string"/>
> <xsd:element name="NewElement7" type="xsd:string"/>
> <xsd:element name="NewElement8" type="xsd:int"/>
> <xsd:element name="NewElement9" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> −
> <xsd:element name="NewOperationResponse">
> −
> <xsd:complexType>
> −
> <xsd:sequence>
> <xsd:element name="out" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
> </wsdl:types>
> −
> <wsdl:message name="NewOperationRequest">
> <wsdl:part element="tns:NewOperation" name="parameters"/>
> </wsdl:message>
> −
> <wsdl:message name="NewOperationResponse">
> <wsdl:part element="tns:NewOperationResponse" name="parameters"/>
> </wsdl:message>
> If you observe the highlighted portion, NewOperationRequest, it has element, parameters, of type NewOPeration, which is of complex type.
> My code give s a run time exception when I try to execute my code using this WSDL file, as  java.lang.RuntimeException: not know how to convert 'abc' into org.apache.axis.client.Call@b45130
> Please help me find a solution on this problem, as most of my WSDL files include complex types for the requests.
> Thanks in advance.
> -- 
> Sneha 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.