The jsr181 component should be able to accept any xml source in the exchange, but it does expect it not to be a soap request. SOAP is handled by BC. The purpose of the soap="true" attribute on the BC is to unmarshall the soap envelope, process any ws-addressing, ws-security headers and send the content of the request to the target component.
So the jsr181 component acts as a good citizen in the jbi bus: it accepts an xml content which is described by the exposed wsdl. But this is not a soap request. On 8/18/06, jlo_gestalt <[EMAIL PROTECTED]> wrote:
I could, but I don't think that is the cause of my problem. I think the fundamental question is, shouldn't the JSR181 component be able to accept just SOAP through the content method and it should work no matter who is sending the SOAP, whether it be the HTTP BC or another component such as our Compression Component? I guess I was assuming that was how the JSR181 component was built and how any JBI component should be built. Is this correct? -- View this message in context: http://www.nabble.com/Problem-with-JSR181-Component-tf2128179.html#a5873437 Sent from the ServiceMix - User forum at Nabble.com.
-- Cheers, Guillaume Nodet
