On Sat, Sep 24, 2011 at 9:14 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > * cleanup the api an architecture to allow one to use camel as an > integration framework *without* the routing part. For instance one should be > able to use just a producer template and the components of choice with a > lean runtime (without the dsl, some processors maybe, support for routing, > etc)
+1 on this one...let Camel be a protocol repository. Possibly also allowing an endpoint to act as a simple readable BlockingQueue. Though this wouldn't necessarily be a compatibility problem, would it? Could it not be done as a new layer under the routing, leaving the existing API intact? Don
