Yadav,
I did a quick sanity check with Axis2 1.1.1 SwA attachments and I
wasn't able to recreate the issue you reported..

Please provide some more  information... Also what's the message
sniffer you are using..  Please try using tcpmon[1]..

~Thilina
[1] http://ws.apache.org/commons/tcpmon

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

-----Original Message-----
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 12:27 AM
To: [email protected]; [EMAIL PROTECTED]
Subject: Re: Attachments - incorrect *boundary* header

Yes.. Please log a Jira..

But it was working fine when I looked at it the last time (1 week
back).. What's the Axis2 version you are using.

Thanks,
Thilina

On 2/13/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> 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]
>
>


--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

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

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.

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




--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

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

Reply via email to