camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Fw: How to process Multipart SOAP response
Date Tue, 05 Apr 2016 14:46:25 GMT
Hi Team,

Any response on this ?

in the documentation of camel-SOAP, the example for multipart request & response states
using serviceInterfaceStrategy. however the example is not clear.

ServiceInterfaceStrategy strat =  new ServiceInterfaceStrategy(com.example.customerservice.multipart.MultiPartCustomerService.class,
SoapJaxbDataFormat soapDataFormat = new SoapJaxbDataFormat("com.example.customerservice.multipart",

we are not able to find the definitio of this class- com.example.customerservice.multipart.MultiPartCustomerService.class

hence cant use this example to implement.

Please help



From: Wadhwani, Ekta V.
Sent: Wednesday, March 30, 2016 8:38 AM
Subject: How to process Multipart SOAP response

Hi Camel team,

Jboss Fuse Studio : Version: 8.1.0.GA

Jdk version: 1.8.0_73


No server involved. since i am yet trying to run camel context locally on dev studio

I am trying to connect send and receive a SOAP request&response message to a third party

I am succesfully able to send and receive. However i am not able to process the soap response
received since its a multipart messasge as follows:

SOAP response 1st : ------=_Part_4694_423702238.1459343682692
Content-Type: application/xop+xml;charset=UTF-8;type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <44e5cd34-e05d-41d2-8231-e3e23f2440a1>

<?xml version="1.0" encoding="UTF-8" ?>
<env:Envelope xmlns:env="" xmlns:wsa=""><env:Header><wsa:Action></wsa:Action><wsa:MessageID>urn:uuid:46417381-5e12-448d-968f-0e8e824a1828</wsa:MessageID></env:Header><env:Body><ns0:uploadFileToUcmResponse

[           default-workqueue-3] route7                         INFO  SOAP response 4th :
Content-Type: application/xop+xml;charset=UTF-8;type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID: <e0946c95-9d0d-40ba-8416-0528bfcb4aa9>

<?xml version="1.0" encoding="UTF-8" ?>
<env:Envelope xmlns:env="" xmlns:wsa=""><env:Header><wsa:Action></wsa:Action><wsa:MessageID>urn:uuid:82d7d264-ef7f-41da-8d51-79e940413b13</wsa:MessageID></env:Header><env:Body><ns0:downloadESSJobExecutionDetailsResponse
xmlns:ns1="" xmlns:ns0=""
xmlns:xsi="" xsi:type="ns0:DocumentDetails"><ns0:Content><xop:Include
xmlns:xop="" href="cid:51e0b71c-160b-4921-a8a7-8fe7f87ccc3b"/></ns0:Content><ns0:FileName
Content-Transfer-Encoding: binary
Content-ID: <51e0b71c-160b-4921-a8a7-8fe7f87ccc3b>

PK157463.log?XKS?8??W??????jTL?  .. blah blah some binary content

I am using below XML DSL code:

elementNameStrategyRef="elStrategy" id="soapFormat" />

<route streamCache="true">
<from ... />
<bean ref="erpintservice" method="prepareDocumentDetails" />
<marshal ref="soapFormat" />
<setHeader headerName="Authorization">
<constant>Basic ZzRzLmludGVncmF0aW9uLnVzZXI6RnVzaW9uQDEyMw==</constant>
<!-- <log message="SOAP Request : ${body}"/> -->
<to uri="cxf:bean:uploadFileToUcmEndpoint?defaultOperationName=uploadFileToUcm&amp;dataFormat=MESSAGE"

<log message="SOAP response 1st : ${body}" />
<bean id="elStrategy" class="">
<constructor-arg value=""/>
<constructor-arg value="true"/>

Marshalling works fine since i can see my webservice call has been invoked and response coming
back. unmarshalling would obviously not work directly since the message is not a pure soap
msg but A multipart message

I checked online for mime multipart data format however i do not see any example of xml DSL
+ i could not use it in my jboss dev studio since it does not have this dataformat at all
(dont know why)

My objectives:
1. to be able to process/ fetch out the soap envelope part from this multipart soap response
using XML DSL
2. to be able to process the binary content of multipart message since that is my attachment
using XML DSL.

Request you all to help. Badly stuck at this point


This message is for the designated recipient only and may contain privileged, proprietary,
or otherwise confidential information. If you have received it in error, please notify the
sender immediately and delete the original. Any other use of the e-mail by you is prohibited.
Where allowed by local law, electronic communications with Accenture and its affiliates, including
e-mail and instant messaging (including content), may be scanned by our systems for the purposes
of information security and assessment of internal compliance with Accenture policy.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message