Ashwin Karpe wrote:
> 
> Hi Lukasz,
> 
> The rules of the game are same for the Provider and Consumer. Only the
> directionality and role changes....
> The Provider will therefore look for a Raw XML message if SOAP="false" and
> not go looking for a SOAP Header in JBI properties.
> 
> As for your second question, the JBI property used to store the SOAP
> Header constent if SOAP="true" is JbiConstants.SOAP_HEADERS
> 
> 

Thank you for the response.
Didn't you mean JbiConstants.PROTOCOL_HEADERS ? 
I can't find SOAP_HEADERS and the name of the property I see in the log
match PROTOCOL_HEADERS

I also did a test and a message with the following header:
        <soapenv:Header>
                <eb:MessageHeader soapenv:mustUnderstand="0">
                        <eb:ConversationId>12345</eb:ConversationId>
                </eb:MessageHeader>
        </soapenv:Header>

and what is looged is:
properties: 
{javax.jbi.messaging.protocol.headers={{http://eb}MessageHeader=[eb:MessageHeader:
null]}}}

is that what should we expect?
-- 
View this message in context: 
http://www.nabble.com/SOAP-headers-and-CXF-Provider-tp20893998p20918123.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to