In the first component, I set the messageExchange with the message and do a getDeliveryChannel().send(messageExchange). This method will get called again once the next chunk of data is ready.
I get the following exception when the getDeliveryChannel().send(messageExchange) is called for second time. java.lang.IllegalStateException: component is not owner gnodet wrote: > > I think you need to write a lightweight component > that would suite your needs. There's no problem > to do what you want: you just need to parse the incoming > xml, and each time a chunk of data is ready, create an > exchange, populate it and sent it asynchronously. > > On 2/27/07, Ujval wrote: >> >> Hi Juergen, >> >> Thanks for your reply. But, EIP doesnt solve my problem here. The size of >> the XML the first component receives is almost of 2GB with 1 million >> records. So, I use the streaming API to first get the data in chunks or >> single records. Once the second component starts creating the chunks of >> data, it needs to be passed to the next component for processing. >> Simultaneously, as the first component is still creating data records to >> be >> passed to the next component, the second component will be processing the >> records which are already passed to it. >> >> Regards, >> Ujval >> >> >> >> >> Juergen Mayrbaeurl wrote: >> > >> > Simply use the >> http://incubator.apache.org/servicemix/servicemix-eip.html >> > EIP XPath Splitter . >> > >> > Greetings >> > Juergen >> > >> > >> > Ujval wrote: >> >> >> >> Hi, >> >> >> >> I have a scenario where I get huge amount of data in one of the JBI >> >> components. I need to parse this message, create smaller chunks of >> data >> >> and pass it to the next component in the flow. Is it possible to send >> >> data multiple times on to the delivery channel and get back the >> control >> >> to the first component? >> >> >> >> One solution to this could be, I can simply drop the message into a >> >> queue, and use a JMSInBinding component which will trigger the next >> >> component. But this adds to the complexity, which I do not want to >> >> handle. >> >> >> >> Any help in this regard would be very useful. >> >> >> >> Thanks in advance, >> >> Ujval >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Sending-message-to-the-same-recipient-multiple-times-tf3296818s12049.html#a9182855 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Architect, LogicBlaze (http://www.logicblaze.com/) > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Sending-message-to-the-same-recipient-multiple-times-tf3296818s12049.html#a9193608 Sent from the ServiceMix - User mailing list archive at Nabble.com.
