Incoming SOAP messages with attachments are parsed correctly, but outgoing messages with attachments are missing attachment parts and all part boundaries, even though the overall HTTP content-type is "multipart/related" with a boundary value specified.
Given this message sending scenario:
I get an HTTP message like this:
Correct overall content-type and boundary value, but no attachment parts and no boundaries.
The problem may be in CommonsHttpConnection.onSendAfterWrite() where a ByteArrayRequestEntity is always used instead of the MultipartRequestEntity that the Commons HttpClient API says should be used for requests with attachments
It would seem to me that onSendAfterWrite() should be checking the WebServiceMessage to see if there are any attachments, and if there are, creating the necessary xml message and attachment Parts and passing them to a MultipartRequestEntity instead of sending the entire request to a ByteArrayRequestEntity.
|Field||Original Value||New Value|
|Fix Version/s||1.5.3 [ 10982 ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Summary||outgoing SOAP messages with attachments created incorrectly||Axiom does not support SwA attachments|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|