Follow up: Re: Receive the error "Attachment tag 'item' .. second request - Pls help

[email protected]
Newsgroups gmane.text.xml.soap.devel
Message-ID <[email protected]>
Scott, 
I think I know what is causing the problem.  The Windows NetBios (AKA 
ComputerName) of the computer that has the aforemention problem has 
characters that are not ASCII.  Instead, they are Korean characters.


When the SOAP client is creating an attachment, it calls 
MimeUtils.getUniqueValue();

This in turn calls 
InetAddress.getLocalHost().getHostName();

which seems to return the ComputerName;

In the SOAP ENV:Body section, the href to the attachment is

<item href 
="cid:4875224.1055357926265.apache-soap.TRAINING%F6%AB%FB%AD%B8%F4"/>


However, in the Part 2 section, Content ID is

Content-ID: <4875224.1055357926265.apache-soap.TRAININGi¡Æ> 

(where the funny characters are the Korean characters - machine I am 
sending mail from does not display them well)

and I am guessing this is what is causing the problem.




Here is the the most relevant lines from the Network Monitor: (I have left 
out the rest of the Part 2 section, Please let me know if you need it also 
- Thx)

Is this a SOAP Bug?

Thanks

Komal



POST /soap/servlet/rpcrouter HTTP/1.0

Host: localhost

Content-Type: text/xml; charset=utf-8

Content-Length: 532

SOAPAction: ""



<?xml version='1.0' encoding='UTF-8'?>

<SOAP-ENV:Envelope 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/1999/XMLSchema">

<SOAP-ENV:Body>

<ns1:SIVerify xmlns:ns1="urn:issfilexfer" 
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<test xmlns:ns2="http://xml.apache.org/xml-soap" xsi:type="ns2:Vector">

<item xsi:type="xsd:string">-MODE=BCA</item>

</test>

</ns1:SIVerify>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

POST /soap/servlet/rpcrouter HTTP/1.0

Host: localhost

Content-Type: multipart/related; 
boundary="----=_Part_2_26204548.1055357926250"; type="text/xml"; 
start="13783459.1055357926281.apache-soap.TRAINING???"

Content-Length: 28545

SOAPAction: ""



------=_Part_2_26204548.1055357926250

Content-Type: text/xml; charset=utf-8

Content-Transfer-Encoding: 8bit

Content-ID: <13783459.1055357926281.apache-soap.TRAININGi¡Æ>

Content-Length: 1480



<?xml version='1.0' encoding='UTF-8'?>

<SOAP-ENV:Envelope 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/1999/XMLSchema">

<SOAP-ENV:Body>

<ns1:SIService xmlns:ns1="urn:issfilexfer" 
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<test xmlns:ns2="http://xml.apache.org/xml-soap" xsi:type="ns2:Vector">

<item xsi:type="xsd:int">1</item>

<item xsi:type="xsd:string">LooseFiles_105108.zip</item>

<item xmlns:ns3="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns3:base64">KqwXPO7KDgVWa3HWqygmSQ==</item>

<item href 
="cid:4875224.1055357926265.apache-soap.TRAINING%F6%AB%FB%AD%B8%F4"/>

<item xsi:type="xsd:string">-MODE=BCA</item>

<item xsi:type="xsd:string">CL_DICT=INSYNC30</item>

<item xsi:type="xsd:string">CL_DATA=KAISTEP</item>

<item xsi:type="xsd:string">CL_USER</item>

<item xsi:type="xsd:string">=</item>

<item xsi:type="xsd:string">321`1143*79321777&gt;111f57000</item>

<item xsi:type="xsd:string">CL_PSWD</item>

<item xsi:type="xsd:string">=</item>

<item xsi:type="xsd:string">321`1143*79321777&gt;111f57000</item>

<item xsi:type="xsd:string">CL_SGRP</item>

<item xsi:type="xsd:string">=</item>

<item xsi:type="xsd:string">*}b145501*63117901&lt;;17778000</item>

<item xsi:type="xsd:string">CL_OS_USER=brianp</item>

<item xsi:type="xsd:string">SV_LOG_COPY=</item>

</test>

</ns1:SIService>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>



------=_Part_2_26204548.1055357926250

Content-Type: application/octet-stream

Content-Transfer-Encoding: 8bit

Content-ID: <4875224.1055357926265.apache-soap.TRAININGi¡Æ>

Content-Length: 26625
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.