On Wed, Oct 27, 2010 at 5:54 PM, James Strachan <[email protected]> wrote: > On 27 October 2010 11:48, Scott England-Sullivan <[email protected]> wrote: >> Hi all, >> >> Long time listener, first time caller... > > Welcome Scott! > > >> Currently I have a similar issue on a project I am working on. Taking some >> hints from this discussion I am wondering if it is possible, and makes >> sense, to extend a Camel Context to provide the IN, OUT and ERROR Endpoints. >> >> Then you could nest this context inside a top level context and use nested >> context ID as it's namespace reference. >> >> {bean definition} >> blackboxContext >> in >> out >> error >> >> routerContext >> from:seda >> to:blackboxContext >> >> from:blackboxContext >> to:mock >> >> This isolates the namespaces and would allow abstraction of the desired >> capabilities. > > Agreed! I think we're all on about the same page; there's just a few > devils in the details on exactly how this all works. > > * we want to wrap up a set of routes as either an Endpoint (kinda like > the route:foo examples from Kristof which have a natural in/out type > approach), or as a Component with internal named endpoints > > * we either use a "local:" component for local only endpoints inside > nested routes; or just nest an inner CamelContext inside them to get > the same kind of effect >
I would assume the "local:" thing would be the easiest. Having a nested CamelContext, we would maybe have to strip it down from some features to keep it lighter (loading type converters, JMX management, event notification, OSGi complexity, lifecycle etc.). > * there are a few options as to how we should export or declare the > 'public endpoints' for a Protocol (e.g. maybe component:in maps to > local:in inside the route - or is there some explicit mapping of a > public name "component:in" to some implementation endpoint URI? > > Maybe we just need to build a prototype of this feature and kick the > tyres a bit and see which approaches seem to work the best? > Yeah kick on the tires from Kristof :) > -- > James > ------- > FuseSource > Email: [email protected] > Web: http://fusesource.com > Twitter: jstrachan > Blog: http://macstrac.blogspot.com/ > > Open Source Integration > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
