I also added the test into Camel 1.x branch, the test result looks good. We may fix this issue in camel 1.6 :)
Willem Willem Jiang wrote: > Yes, these two walk around are turning the input stream which set by the > http client to a re-readable object. > > I just added a simple integration test[1] in Camel 2.0 trunk, the test > shows you don't need any walk around in Camel 2.0 :) > [1] http://svn.apache.org/viewvc?rev=767403&view=rev > > Willem > > Claus Ibsen wrote: >> Hi >> >> You can also use .convertBodyTo(String.class) instead of the JMS queue. >> It will convert the payload from stream based into a String that >> safely can be read multiple times. >> You can also use byte[].class if you want to keep it as byte based. >> >> >> On Wed, Apr 22, 2009 at 10:15 AM, G.J. van de Streek <[email protected]> wrote: >>> I noticed, that if I insert a queue in the route and go from there, that it >>> works: >>> >>> public void configure() { >>> >>> from("timer://foo?fixedRate=true&delay=0&period=60000") >>> .to("http://avisi.nl/integration/agents";) >>> .to("activemq:example.B"); >>> >>> from("activemq:example.B") >>> .multicast() >>> .to("direct:splitAgentsFile", "direct:saveAgentsFile") >>> ; >>> >>> from("direct:saveAgentsFile") >>> .setHeader(FileComponent.HEADER_FILE_NAME, "agents.xml") >>> >>> .to("file:///Users/streekgj/Desktop/filestore/?append=false") >>> ; >>> >>> from("direct:splitAgentsFile") >>> .splitter(new XPathExpression("/agents/agent")) >>> .to("activemq:example.A") >>> ; >>> -- >>> View this message in context: >>> http://www.nabble.com/usage-of-multicast-tp23163812p23171791.html >>> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. >>> >>> >> >> > >
