On 8/18/06, jlo_gestalt <[EMAIL PROTECTED]> wrote:

OK, that is good to know.

However, the jsr181 component does not work when another component, besides
the HTTP BC, sends it xml content which is described by the exposed wsdl.

I realize your point about the xml content not being a soap request, but it
is still xml/soap.

What do you mean ? It is soap or it is not ;)


In which case, is there anything else required by the jsr181 component to be
set?

No

Right now our compression component calls
NormalizedMesssage.setContent() and gives it a DOMSource. This DOMSource
contains the xml/soap. I would think this is all the jsr181 component would
require, but that doesn't appear to be the case.

This is the exception you post earlier, right ?
local part cannot be "null" when creating a QName

Not sure what is the exact reason, but i will take a look.
If you could reproduce that, please raise a JIRA and attach a test case,
it will speed things.

--
View this message in context: 
http://www.nabble.com/Problem-with-JSR181-Component-tf2128179.html#a5874168
Sent from the ServiceMix - User forum at Nabble.com.




--
Cheers,
Guillaume Nodet

Reply via email to