We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SOAP server simulation with Citrus. Client sends request, server responds with an MTOM repsonse with attachment.
If the attachement is sent as inline attachment, it works
<testcase name="MtomSimulationXml"> <actions> <ws:receive endpoint="soapServerSimulation"> <message> <resource file="testfiles/mtom-request.xml"/> </message> </ws:receive> <ws:send endpoint="soapServerSimulation" mtom-enabled="true"> <message> <resource file="testfiles/mtom-response.xml"/> </message> <!-- this attachment is correctly delivered to the client --> <ws:attachment content-id="myAttachment" content-type="application/octet-stream" mtom-inline="true" encoding-type="base64Binary"> <ws:resource file="classpath:testfiles/attachment.pdf"/> </ws:attachment> </ws:send> </actions> </testcase>
Normal MTOM response (NOT inline) does not work. It is not even a multipart response.
<testcase name="MtomSimulationXml"> <actions> <ws:receive endpoint="soapServerSimulation"> <message> <resource file="testfiles/mtom-request.xml"/> </message> </ws:receive> <ws:send endpoint="soapServerSimulation" mtom-enabled="true"> <message> <resource file="testfiles/mtom-response.xml"/> </message> <!-- this attachment is NOT delivered to the client --> <ws:attachment content-id="myAttachment" content-type="application/octet-stream"> <ws:resource file="classpath:testfiles/attachment.pdf"/> </ws:attachment> </ws:send> </actions> </testcase>
If I add this header to the testcase above, the attachment is still NOT delivered to the client, but it is at least a multipart response.
<header> <element name="citrus_http_Content-Type" value="application/xop+xml; charset=utf-8"/> </header>
I have attached an example project (citrus-mtom.zip) that includes a SoapUI project that acts as a client.
XML testcase with inline attachment works
Java testcase with normal attachment does not work
citrus-mtom.zip
The text was updated successfully, but these errors were encountered:
f515791
Fixed #328 SOAP server response with MTOM attachment
6b6616d
No branches or pull requests
Use case
SOAP server simulation with Citrus. Client sends request, server responds with an MTOM repsonse with attachment.
Inline attachment works fine
If the attachement is sent as inline attachment, it works
Problem
Normal MTOM response (NOT inline) does not work. It is not even a multipart response.
Multipart response, but still no attachment
If I add this header to the testcase above, the attachment is still NOT delivered to the client, but it is at least a multipart response.
Example
I have attached an example project (citrus-mtom.zip) that includes a SoapUI project that acts as a client.
XML testcase with inline attachment works
Java testcase with normal attachment does not work
citrus-mtom.zip
The text was updated successfully, but these errors were encountered: