Hello, I have a question about SOAP processing (specifically related to the SOAP header). I've been using ServiceMix lightly for over a year now and my experience has been that SOAP processing appears to occur exclusively at the binding components. That is to say, if a binding component (consumer) like servicemix-http or servicemix-jms receives a SOAP message it is responsible for processing all of the SOAP headers (WS-A, WS-Sec, etc), extracting the body, and passing it all along as a NormalizedMessage. The reverse seems to be true for provider binding components. Is that correct? Am I missing something?
I am trying to wrap my head around the message processing model used here. Theoretically, if I were going to develop a new binding component which used an entirely new transport protocol but still used SOAP message envelopes, what would I need to do to support the WS-* specifications? Would I have to embed all of that logic into the new binding component or is there some set of services on the bus that encapsulate that functionality? Thanks, Jeff
