The jsr181 component can be configured with a given instance of the class that will be used to process all the incoming exchanges. You just need to make sure your code is designed to be used that way: a single instance will receive all calls concurrently, as in the servlets world. The servicemix-bean behaves the same way.
Another way would be to implement your own aggregation strategy using servicemix-eip or camel. Servicemix-eip already provides some aggregation and can be extended (but does not use any jaxb marshaling, so it depends if you need it or not). Camel is really flexible and powerful and it may be worth to take a look at it. On Wed, Feb 20, 2008 at 6:37 AM, sachin2008 <[EMAIL PROTECTED]> wrote: > > Hi, > > I am having a scenario: > > HTTP(BC)-------> JSR----------->Aggregator---------------->HTTP(BC) > > My requirement is: > > In JSR, we need incorporate the multi threading logic for getting the data > from different data sources and by using the aggregator pattern we need to > aggregate the xml data coming from different datasources and send the > response back to the HTTP(BC). > > Can anyone please tell me how to use the aggregator pattern in this regard. > > -- > View this message in context: > http://www.nabble.com/Reg%3AAggregator-Pattern-tp15582806s12049p15582806.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
