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 ax...@ws.apache.org on 2004/10/11 15:39:51 UTC

[jira] Updated: (AXIS-1417) Special characters in enum value

The following issue has been updated:

    Updater: Ashutosh Shahi (mailto:ashutosh.shahi@gmail.com)
       Date: Mon, 11 Oct 2004 6:38 AM
    Comment:
Patch(diff) for the issue. Ran all-tests and everthing seems fine.
Ashutosh
    Changes:
             Attachment changed to diff_1417.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXIS-1417?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1417

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1417
    Summary: Special characters in enum value
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis
 Components: 
             Serialization/Deserialization

   Assignee: 
   Reporter: Nicolai Grødum

    Created: Sun, 27 Jun 2004 2:53 PM
    Updated: Mon, 11 Oct 2004 6:38 AM
Environment: Java

Description:

I have a .NET Web service where I serialize the values of my enum into things like "Telephone -> 22222222" using custom xml serialization attributes on my enum.

This generates a WSDL that has entries like the one above, which produces a valid client stub when I use .NET (the value is automatically encoded as > in the request), but fails with Axis.

I have to modify my enum values like this in my java Axis stub every time I recreate it from the WSDL:

from
public static final java.lang.String _value9 = "Telephone -> 22222222";

to
public static final java.lang.String _value9 = "Telephone -> 22222222";

Not a killer bug, but probably easy to fix.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira