That does not seem right. Can u please log a bug?

thanks,
dims

On 2/12/07, Yadav, Yogendra (IT) <[EMAIL PROTECTED]> wrote:



Hi,
While generating SOAP with attachments message using Operation Client API,
it generates one *boundary* header in Content-Type: multipart/related
whereas it generate all new header for SOAP Body section and attachment
section. See the relevant section from message below:
---------------------------------------------------------------------------------------------------
Content-Type: multipart/related;
boundary=MIMEBoundaryurn:uuid:F02ECC18873CFB73E211412748909307;
type="application/xop+xml";
start="<0.urn:uuid:[EMAIL PROTECTED]>";
start-info="text/xml"; charset=UTF-16

User-Agent: Axis2

Host: 127.0.0.1:8081

Proxy-Connection: Keep-Alive

Content-Length: 6956

---------------------------------------------------------------------------------------------------
--MIMEBoundaryurn_uuid_D57945993FC51941A31171314318273
<---------different than one defined above

content-type: text/xml; charset=UTF-8

content-transfer-encoding: 8bit

content-id:
<0.urn:uuid:[EMAIL PROTECTED]>

---------------------------------------------------------------------------------------------------
--MIMEBoundaryurn_uuid_D57945993FC51941A31171314318273
<---------different than one defined above

content-type: text/xml

content-transfer-encoding: binary

content-id: <urn:uuid:D57945993FC51941A31171314318022>

---------------------------------------------------------------------------------------------------

Appreciate if someone can suggest a solution for this.

thanx in advance
-yogen

 ________________________________


NOTICE: If received in error, please destroy and notify sender. Sender does
not intend to waive confidentiality or privilege. Use of this email is
prohibited when received in error.



--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to