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 2002/10/25 16:40:43 UTC

DO NOT REPLY [Bug 13974] New: - Faulty XML response gnerated by AXIS.

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

Faulty XML response gnerated  by AXIS.

           Summary: Faulty XML response gnerated  by AXIS.
           Product: Axis
           Version: 1.0
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: arvindbc@hotmail.com


The webservice I am  invoking has EJB as the provider and AXIS-10 is the SOAP 
server.

I trapped the SOAP packets using TCPMon.I notice that in SOAP response  
generated by AXIS that there is unwanted value - It  is number "2000"  embedded 
in between the items of an array as in

-----------------------------------------
    <item xsi:nil="true"/>
    <item xsi:nil="true"/>
   

2000

 <item xsi:nil="true"/>
    <item xsi:nil="true"/>
------------------------------------------

Yet in some cases it is worse as this number is embdded within the item tag as 
in

=========================================
    <item xsi:nil="true"/>
    <item xsi:nil="t

2000

rue"/>
    <item xsi:nil="true"/>
    <item xsi:nil="true"/>

=========================================

I guess this causing the deserializer error on the client side(.NET).What is 
this number 2000?.It is definitely not from my application.Is it a kind of 
UNICODE character?.Becuase of all of this , I think it may be a bug in response 
generated by  AXIS.

Thanks,


Arvind