You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by ji...@apache.org on 2004/04/09 15:28:43 UTC

[jira] Assigned: (SOAP-158) SAX parsing error

Message:

   The following issue has been re-assigned.

   Assignee: Scott Nichol (mailto:snicholnews@scottnichol.com)
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/SOAP-158

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: SOAP-158
    Summary: SAX parsing error
       Type: Bug

     Status: Open

    Project: Apache SOAP
 Components: 
             All
   Versions:
             2.3

   Assignee: Scott Nichol
   Reporter: amit

    Created: Mon, 17 Nov 2003 2:07 PM
    Updated: Fri, 9 Apr 2004 6:27 AM
Environment: Operating System: Windows NT/2K
Platform: All

Description:
the following RPC generate the following fault:
Fault code = SOAP-ENV:Client
Fault string = parsing error: org.xml.sax.SAXParseException: The prefix "ns6" 
for attribute "ns6:arrayType" is not bound


it looks like the soap client message generated from calling the following 
remote procedure gets screwed in the marshalling process due to the user 
defined array type.
the service name is: "urn:service".
the method name is "attach".
the method signature is:
public void attach(String[] strings1, int[] ints1, int[] ints2, String[] 
strings2, Complex[] complex1, Complex[] complex2, int[] ints3);

all of the arrays get parsed fine until the first complex array type gets 
marshalled. the first complex array is marshalle correctly but
after that the next complex array and the int array after that generate bad xml 
code. they both get stuck with the same name space of the first complex array.


here is the relevent part of the soap message, notice that after binding the 
user defined complex arry type using ns6, the next bindings get stuck on ns6 
which causes the xml parsing error.

<ns1:attach xmlns:ns1="urn:service" 
  SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">   
    <strings1 xmlns:ns2="http://schemas.xmlsoap.org/soap/encoding/" 
      xsi:type="ns2:Array" ns2:arrayType="xsd:string[1]">        
	<item xsi:type="xsd:string">aaa</item>    
    </strings1>    
    <ints1 xmlns:ns3="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns3:Array" 
      ns3:arrayType="xsd:int[1]">        
	<item xsi:type="xsd:int">0</item>    
    </ints1>    
    <ints2 xmlns:ns4="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns4:Array" 
      ns4:arrayType="xsd:int[1]">        
	<item xsi:type="xsd:int">0</item>    
    </ints2>    
    <strings2 xmlns:ns5="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns5:Array" 
      ns5:arrayType="xsd:string[1]">        
	<item xsi:type="xsd:string">aaa</item>    
    </strings2>    
    <complex1 xmlns:ns6="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns6:Array" 
      ns6:arrayType="ns1:amit.soap.Complex[1]">   	
	<item xsi:type="ns1:amit.soap.Complex">
	    <complexType 
              xsi:type="ns1:amit.soap.ComplexType"> 		
		<value xsi:type="xsd:int">0</value>            
	    </complexType>            
	    <name xsi:type="xsd:string">amit</name>            
	    <IPAdress 
xsi:type="xsd:string">111.111.111.111</IPAdress>            	    	

    	    <ZNumber xsi:type="xsd:string">10</ZNumber>        
	</item>    
    </complex1>    
    <complex2 xsi:type="ns6:Array" 
      ns6:arrayType="ns1:amit.soap.Complex[1]">   		
	<item xsi:type="ns1:amit.soap.Complex"> 
	    <complexType xsi:type="ns1:amit.soap.ComplexType">	
	  	<value xsi:type="xsd:int">0</value>            
	    </complexType>            
	    <name xsi:type="xsd:string">amit</name>            
	    <IPAdress 
xsi:type="xsd:string">111.111.111.111</IPAdress>            
	    <ZNumber xsi:type="xsd:string">10</ZNumber>        
	</item>    
    </complex2>    
    <ints3 xsi:type="ns6:Array" ns6:arrayType="xsd:int[1]">        
	<item xsi:type="xsd:int">0</item>    
    </ints3>
</ns1:attach>


---------------------------------------------------------------------
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