Hi, I have a web service receives attachment file from clients and sends attachment file to clients. Previously it assume AttachmentMap only contains attachment files and SOAP message is excluded. When I use XML Exchanger Lite as client to invoke the web service, the attachment is received by the server properly, and the acknowledgement file is returned to the client properly.
Now I use Axis2 client (OperationClient) to program the client. My observation shows that when I list AttachmentMap, the SOAP message is now the first attachment, and the actual attachment becomes the second attachment. The server is simply take the first attachment and do the processing. Effectively after I switching to Axis2 client, the server now is treating the SOAP message as the attachment which causes error. Why does SOAP message goes into the AttachmentMap? Is this a bug or a desirable change? Regards, Xinjun
