Could you send the 3.0 configuration file using the servicemix-eip component that cause a problem with stream. The servicemix-eip should be able to gracefully handle all streams, but this is not the case for all components.
Cheers, Guillaume Nodet On 5/31/06, TimT <[EMAIL PROTECTED]> wrote:
Guillaume, Thanks for the help, I now have routing working, deployed in Jboss using the EIP content-based-router. I did however initially run into the same problem as with servicemix 2, that is that the transformer that does the routing closed the input stream based StreamSource that is set as the NormalizedMessage content resulting in a "premature end of file". I fixed this by creating my own implementation of the HttpMarshaler, which I injected into the HttpConnector. In this implementation I have overwritten the toNMS(...) method so that it creates a DOMSource rather than a StreamSource. Is there some benefit to using StreamSource over DOMSource in the HttpMarshaler? It would be useful to make the choice between which sort of Source to use configurable. Regards, Tim Tennant -- View this message in context: http://www.nabble.com/XsltComponent+routing+problem-t1687094.html#a4644567 Sent from the ServiceMix - User forum at Nabble.com.
