axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajith Harshana Ranabahu (JIRA)" <>
Subject [jira] Resolved: (AXIS2-845) WSDL2Java fails to detect nonexistent element referenced by wsdl:message
Date Tue, 18 Jul 2006 10:37:14 GMT
     [ ]

Ajith Harshana Ranabahu resolved AXIS2-845.

    Resolution: Fixed

The problem here was the behavior of the type mapper where it pumped out the default class
name in case of unknown QNames. The behavior is changed now to throw a UnmatchedQnameException
 if the given QName is not found. A test case is also added to test this behavior

> WSDL2Java fails to detect nonexistent element referenced by wsdl:message
> ------------------------------------------------------------------------
>                 Key: AXIS2-845
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Derek Foster
>         Assigned To: Ajith Harshana Ranabahu
> I recently noticed that the Axis2 WSDL2Java program, when generating XmlBeans, seems
to accept WSDL which contains references to nonexistent elements. For instance:
>    <types>
>       <xs:schema>
>          <xs:import namespace="http://www.dummy-im-address"
> schemaLocation="im.xsd"/>
>       </xs:schema>
>    </types>
>    <message name="IEEE1512Event">
>       <part name="iMWrapper" element="im:thisDoesNotExist"/>
>    </message>
> The element "thisDoesNotExist" is not defined anywhere in the im.xsd schema file, yet
WSDL2Java reports no warnings or errors when asked to generate code for a service using this
WSDL file. The server skeleton that is generated takes a parameter of type XmlObject where
the thisDoesNotExist element would be passed. Considering that this can easily happen due
to a simple typo in an element name, this seems like a very difficult problem to track down.
> It seems to me that an error, or at least a warning, should be reported for cases like

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:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message