Hi,

I have been trying to get the following requirements in blueprint XML.

- An External client invokes the servicemix URL along with the SOAP Payload.

1. Inside the blueprint, I want to extract this SOAP Payload (Header, Body)
and get few informations like Username, CountryCode, SiteID, etc.

My SOAP message looks like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
   <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>
      <wsa:Action>http://dummyWS.com/system/Access/ServiceOne</wsa:Action>
      <wsa:ReplyTo>
        
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
      </wsa:ReplyTo>
      <wsse:Security>
            <wsse:Username>scheduling</wsse:Username>
            <wsse:Password
wsse:Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>Password</wsse:Password>
         </wsse:UsernameToken>
      </wsse:Security>
   </soapenv:Header>
   <soapenv:Body>
         <ns2:UserName>TEST1</ns2:UserName>
         <ns2:SiteId>0000</ns2:SiteId>
         <ns2:CountryCode>XX</ns2:CountryCode>
</soapenv:Body>
</soapenv:Envelope> 


- How I can extract this information from a Blueprint XML. (No java methods
can be used for our project). 

Are there any alternate way of extracting SOAP message without using java. ?


2.  Going fwd, Once after extracting the SOAP data, I need to construct a
SOAP message (along with the extracted data like username, siteID,
CountryCode, etc )and call another REST service and pass this SOAP message
using POST method. 

- How to invoke a REST service in Blueprint XML, without using CXFRS since
it uses Java.

Could anyone update me with an information about this ?

Regards,
Pradeep



--
View this message in context: 
http://servicemix.396122.n5.nabble.com/Extract-SOAP-Body-in-blueprint-XML-tp5714486.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to