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/03/01 02:08:15 UTC

DO NOT REPLY [Bug 17554] New: - Integer[] -> int[]

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=17554>.
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=17554

Integer[] -> int[]

           Summary: Integer[] -> int[]
           Product: Axis
           Version: 1.1RC1
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: john@agari.com


Using Apache AXIS 1.1-rc1, I have a client perform a web service invocation on 
a method with a signature similar to:

  execute(String, Map);

Inside of the Map, my client puts an Integer[].  In the web service class 
called by the AxisServlet, the object in the Map is an instance of int[] (the 
primitive int array when it should be the object Integer array).

This is odd because Integer is sent across as Integer just fine.  The problem 
appears to be only when sending arrays.  Have not tested with other 
primitives, but would guess similar behavior.