Hi,
I guess you are using default JBI wrapper message inside servicemix, in
this case, the soap interceptor won't be invoked since the message
payload isn't soap message.
Try add useJBIWrapper="false" both for your CXF-SE su and CXF-BC su, the
soap payload will be used in this case and I believe the soap protocol
handler will be picked up.
Freeman
peppinolusuraio wrote:
I have a problem with CXF-SE and SOAPHandlers porting my application from CXF
to SMIX.
My App is made up of:
1)one CXF-SE su
1)one CXF-BC su
I have a lot of SOAPHanders doing some elaboration on my proprietary header
files.
Debugging I realized that while all the Handlers instances specified in the
handlers.xml are created, at execution time ONLY the LogicalHandlers are
invoked and process the incoming and outgoing message.
it seems the CXF SoapHandlerInterceptor does not intervene in the processing
execution.
does SMIX not use all the interceptors in all the "PHASE"s ??
Do i have to add myself this interceptor?
Is this a SMIX bug or is it correct?
How can I work around this big big porting problem?
thank you
