You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by Mohanbabu Narayanasamy <mx...@bjc.org> on 2007/01/15 21:58:36 UTC

Axis 1.3 & .NET attachment issue

Hi,
 
I'm integrating axis 1.3 client to send JPEG files as DIME attachment
to a .NET webservice. I'm able to successfully set the attachment, set
the content-id, etc and send it to the .NET webservice.
 
But the .NET service is unable to read the JPEG attachment because the
content-id (GUID in .NET world) is of different format. That's what I
think is the problem. 
 
When I trace the SOAP messages in TcpMon, I see that the GUID for the
attachment is set as "F663CD71E7527568801FD45B3D2CF59D". 
But the .NET guys tell me that it has to be set in this format
"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" - example:
"f663cd71-e752-7568-801f-d45b3d2cf59d" 
(Ignore the case - it's case insensitive). 
 
is this correct? If so, how can I intercept the SOAP call and set the
content id with dashes?
 
Please correct me If I'm wrong. 
 
thanks in advance,
Babu