[
https://issues.apache.org/jira/browse/CXF-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Granseuer updated CXF-4106:
--------------------------------
Attachment: swa-client.zip
Sample project that exhibits the issue.
The client will send a request on "mvn integration-test". Note that the project
uses WebSphere as JMS broker.
> Attachments get lost when WSDL claims HTTP transport but config uses JMS
> ------------------------------------------------------------------------
>
> Key: CXF-4106
> URL: https://issues.apache.org/jira/browse/CXF-4106
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.5.2
> Reporter: Jens Granseuer
> Attachments: swa-client.zip
>
>
> I'm trying to call a service that claims SOAP with Attachments via an HTTP
> transport. In reality, however, the service is connected via JMS, so I'm
> overwriting the transportId in the Spring config. In the request that is sent
> out from the client the attachment is missing. Instead, it is included as a
> second XML element in the SOAP body.
> According to Dan, this is because the change in transport resets a couple of
> things to defaults, see
> http://cxf.547215.n5.nabble.com/SOAP-w-Attachments-still-supported-td5454220.htm
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
