On 2/11/11 5:50 PM, James Strachan wrote:
On 10 February 2011 20:13, Ashwin Karpe<aka...@fusesource.com> wrote:
Hi James,
I like the approach. It certainly replaces the need to have a Strategy and
eliminates the need to inject a context into a component.
Thanks!
Am sure there's uses for the RouteBox approach when folks want to do
different things; though my gut feel was just to use regular Camel
endpoints as the 'API' to the black boxed components; then you can use
the regular Camel routing engine as the 'strategy' for consuming from
those endpoints and doing Content Based Routing or whatever.
If everyone agrees, I will be happy to develop this capability along these
lines and open it up for review and comment.
Great stuff thanks! BTW before I sent the previous email I'd checked
in an implementation and a number of test cases to check it worked;
using concise or verbose URIs using the Java DSL. Though we need more
testing of using this concept more with Spring; we might have a few
gremlins when working with multiple contexts and using some of the
injection& annotation features; which up to now have tended to assume
only a single CamelContext etc.
I read about the test, and have a question for it.
Do we real need to call the camelContext.start() in the
RouteBuilder.Configure method?
Maybe we should let the CamelContext component check the camel context
stats when it is stared.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
