axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay Metchev (JIRA)" <>
Subject [jira] Created: (AXIS-2332) exceptions which are wrapped arrays should not get unwrapped
Date Thu, 08 Dec 2005 16:21:08 GMT
exceptions which are wrapped arrays should not get unwrapped

         Key: AXIS-2332
     Project: Apache Axis
        Type: Bug
  Components: WSDL processing  
    Versions: 1.3    
    Reporter: Nikolay Metchev

If you define your exception to be something of the sort:

<xs:complexType name="WebServiceException">
<xs:element maxOccurs="unbounded" type="tns:AdminError" name="error"/>
<message name="WebServiceException">
<part type="tns:WebServiceException" name="WebServiceException"/>
<operation name="Login">
<input message="tns:LoginRequest"/>
<output message="tns:Success"/>
<fault message="tns:WebServiceException" name="WebServiceException"/>

Then wsdl2java will generate java code which doesn't compile. It will try and "unwrap" the
WebServiceException type and declare a port type with the following signature:

public boolean login(com.teamphone.enterprise.admin.service.LoginRequest loginRequest) throws
java.rmi.RemoteException, com.teamphone.enterprise.admin.service.AdminError[];

The work around is to use the -w option of wsdl2java.

The correct functionality is not to unwrap exception of this type.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message