I fix the problem by creating a document and importing the given element when the input source is a DOMSource, but the node is not a document. This is configurable, but enabled by default.
Cheers, Guillaume Nodet On 6/13/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
I have reproduced the problem. It seems that the problem comes from the xslt transformation / component. When the exchange come from the saab binding to the transformer component, the content of the message is a DOMSource, with a Node that represents the first child element of the soap:Body envelope. What happens is that the match="/" template is never executed, because the "/" seems to be mapped to the document itself, but not the current/root node. This leads to the fact that the result is not a valid xml, hence the exception you see. Replacing the "/" by "node()" seems to work. Still not sure if the problem comes from the xslt engine, the component or the stylesheet... I will try to find something Cheers, Guillaume Nodet On 6/13/06, markpittsnh <[EMAIL PROTECTED] > wrote: > > > 1.I am curious how to configure the XSLT component to an in-only MEP. > 2.I poked around the multiple web-sites (servicemix.org, > servicemix.codehaus.org, and http://goopen.org/confluence/display/SM) to > see > if I could find any examples which incorporate XSLT as a simple > transformation within a routing. The only examples I found used XSLT as > a > means to XPATH routing. > > Is there a better solution to content transformation other than XSLT? > > THanks and regards, > Mark > -- > View this message in context: > http://www.nabble.com/xslt-and-routing-t1775037.html#a4851597 > Sent from the ServiceMix - User forum at Nabble.com. > >
