DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14065>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14065 Message.addAttachmentPart() != Call.addAttachmentPart() Summary: Message.addAttachmentPart() != Call.addAttachmentPart() Product: Axis Version: 1.0 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Basic Architecture AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm unable to send SOAP messages with attachments by adding the AttachmentPart using (Case A) org.apache.axis.Message.addAttachmentPart(AttachmentPart ap). However, adding the attachmentPart via (Case B) org.apache.axis.client.Call.addAttachmentPart(AttachmentPart ap) works. The only other differences between the two pieces of the code involve how the connection to the service is setup. In Case A, the connection is setup using the saaj classes and interfaces (SOAPConnection obtained via SOAPConnectionFactory) and then invoked as soapConnection.call(soapMessage, endPointURLString). The tcp Monitor shows the xml going out but not the attachment, even though inspecting the soapMessage before the .call() shows that an attachment exists. This leads me to believe that there may be a problem with the client side serialization of SOAPMessage (or one of its constituent parts). In Case B, the connection is setup and invoked similar to /samples/attachments/EchoAttachment. I believe that Case A should work based on the documentation/mailing list archives and source code I've looked at. I've also heard someone mention that the problem lies in the mapping between the saaj classes/interfaces and the org.apache.axis ones. If this is the case, it should be documented somewhere so others don't have difficulty getting this to work.
