ADBException: Any type element type has not been given
------------------------------------------------------
Key: AXIS2-4439
URL: https://issues.apache.org/jira/browse/AXIS2-4439
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: client-api
Affects Versions: 1.5
Environment: Windows XP Desktop computer
Reporter: Anthony Seniunas
Priority: Blocker
I've developed a web client using wsdl2java and I'm getting the following
exception when obtaining a response from a web service.
org.apache.axis2.databinding.ADBException: Any type element type has not been
given
The .wsdl fragment relating to this is:-
<xsd:complexType name="DocumentData">
<xsd:sequence>
<xsd:element name="Doc" type="schema:DocType"
form="unqualified" minOccurs="0"
maxOccurs="unbounded"/>
<xsd:element name="Result" type="xsd:string"
form="unqualified" minOccurs="0"/>
<xsd:element name="SessionId" type="xsd:string"
form="unqualified" minOccurs="0"/>
<xsd:element name="OriginalMessage" type="xsd:anyType"
form="unqualified" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
Note the originalMessage element type - anyType.
The following is a typical response SOAP message causing the exception:-
<?xml version = '1.0' encoding = 'UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soapenv:Body>
<call:LoginResponse
xmlns:call="http://www.testplc.com/ws/services/dms/interface/kirona/envhealth/";>
<call:DocumentData>
<Result>SUCCESS</Result>
<SessionId>D83D8A42672F08AA6EC9377CB32F6317</SessionId>
<OriginalMessage>
<ns1:Login
xmlns:ns1="http://www.testplc.com/ws/services/dms/interface/kirona/envhealth/";>
<ns1:Authorisation>Y29yb25hdXNlcjpjMHIwbjR1czNy</ns1:Authorisation>
</ns1:Login>
</OriginalMessage>
</call:DocumentData>
</call:LoginResponse>
</soapenv:Body>
</soapenv:Envelope>
Its unusual but the web service returns the original message hence the usage of
anyType.
I've come across many articles on problems with anyType and its possible this
problem has already been fixed so please can you advise?.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
