Hi Lukasz,
The JbiConstants.PROTOCOL_HEADERS store the protocol level headers (like
jms headers, http headers).
So your soap header won't be saved here. The soap header in your message
will be handled by the cxf bc in two cases
1) if the soap header is part of the parameters, it would be extracted
according to the service model (build from the wsdl)
2) if the soap header is used for ws-* (like ws-security, ws-addressing,
etc), it would be extract and processed by the related interceptors your
specified for the cxf bc endpoint.
Regards
Freeman
Lukasz L. wrote:
the SOAP header was exactly as I posted below ... that's why I wondered why
it's not fully logged (that was logged using Trace component) or if it's not
fully copied to property
Lukasz
Ashwin Karpe wrote:
Oops, yes indeed, It is JbiConstants.PROTOCOL_HEADERS...
The contents would depend on your SOAP Headers. If the Header section is
empty, I could expect to see the information you have specified...
Lukasz L. wrote:
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?
