axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sagara Gunathunga (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AXIS2-5384) org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement messages
Date Sat, 13 Jul 2013 07:51:52 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sagara Gunathunga  updated AXIS2-5384:
--------------------------------------

    Assignee: Kishanthan Thangarajah
    
> org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement
messages
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5384
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5384
>             Project: Axis2
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.4, 1.6.2
>         Environment: windows,unix
>            Reporter: Ranjani Kannappan
>            Assignee: Kishanthan Thangarajah
>            Priority: Critical
>
> "Messages" is a defined field in the Web services.This field is currently not used in
the request- and in the response object, because it contains no useful information for us.
On response side, however, this field is set automatically by the webservice. if data is entered
in this field (in the Web-Service-Response), the call works. But if this is empty we get an
error when calling this function.
> This behavior is surprising because this is an error in the data of the response object.
> Normally, errors occur when using  incorrect information in the request object. -->
in client side. 
> But the request is sent successfully and will be processed successfully by the webservice.
We think that there is some kind of parsing error of the response object although the call
was successful.
> 1. <messages>
>     <cmn:message type="String">rwe - cm - qg1 passed</cmn:message>
>   </messages>
> 	
> 2.  <messages />
> During first it succeeds and second run it fails due to empty value.
> And the wsdl looks like this for the above call
> - <xs:element name="CloseChangeResponse">
> - <xs:complexType>
> - <xs:sequence>
>   <xs:element name="model" type="ChangeModelType" /> 
>   <xs:element minOccurs="0" name="messages" type="cmn:MessagesType" /> 
>   </xs:sequence>
>   <xs:attribute name="status" type="cmn:StatusType" use="required" /> 
>   <xs:attribute name="message" type="xs:string" use="required" /> 
>   <xs:attribute name="schemaRevisionDate" type="xs:date" use="required" /> 
>   <xs:attribute name="schemaRevisionLevel" type="xs:int" use="required" /> 
>   <xs:attribute name="returnCode" type="xs:decimal" use="optional" /> 
>   <xs:attribute name="query" type="xs:string" use="optional" /> 
>   </xs:complexType>
>   </xs:element>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


Mime
View raw message