Hi, Can you please describe your use case before soliciting comment on this approach...
It would work just fine in an embedded scenario where Camel behaves more like a JCA connector to resources at the backend. The Camel Context performs lifecycle operations for entities under its control and own resources (aka threads, etc) to support underlying routes, components and entities under its direct control. As such the Camel Context is fairly benign and is only involved during lifecycle ops and stats gathering. In this regard, use case detail is directly proportional to response quality. Please provide further info. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com Blog: http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/Camel-context-tp5523994p5525119.html Sent from the Camel - Users mailing list archive at Nabble.com.
