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 bu...@apache.org on 2003/05/23 23:25:26 UTC

DO NOT REPLY [Bug 17484] - WSDL2JAVA generates wrong getSerializer / getDeserializer Methods

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17484>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17484

WSDL2JAVA generates wrong getSerializer / getDeserializer Methods

jleming@tgw.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |
            Version|1.1RC1                      |1.1rc2



------- Additional Comments From jleming@tgw.com  2003-05-23 21:25 -------
When we use WSDL2Java, for the enumerated objects, it generates classes without 
any typedesc or getSerializer/getDeserializer functions such that when we run 
them, the error message is:

No serializer found for class ....

an example of the enumeration is where the xsd does something like this:
<xsd:element name="Type">
    <xsd:simpleType>
        <xsd:restriction base="xsd:string">
            <xsd:enumeration value="Commission"/>
        </xsd:restriction>
    </xsd:simpleType>
</xsd:element>