Hi James & Hadrian,

I like what you both have said. I was actually thinking of the URI more
along the lines of a URN (camel-lucene) rather than a URL Scheme
(camel-netty), but a ProtocolBuilder the way Hadrian has suggested will work
well too (route:blackboxroute1://out || route:blackboxroute1:out). 

The key is (as you correctly pointed out) James to be able to wrap a route
with multiple inputs/outputs and transparently move payloads arriving at
(route:blackboxroute1://out) to the right set of consumers and collect the
final exchange from the inner route and push it to the next coarse grainer
route (route:blackboxroute2:in).

Even more interesting is the situation that endpoint
(route:blackboxroute1://out) has to handle In-Out scenarios when an exchange
from the endpoint (route:blackboxroute2:in) is received on the outbound to
be directed back to the original client.

I still have to work out how an distributed client will know about the
protocol semantics of the hidden sub-route consumer (easy/no change when
involving an in-JVM client). Maybe query params??? Any thoughts...

I was thinking of taking advantage of using a ProtocolBuilderContext
(similar to RouteContext) to facilitate route declaration and encapsulation
of the inner route with the endpoint name (blackboxroute1) that can then be
wired by the component (route:) along the way.   

Any thoughts/ideas on this approach.... Getting a generic second level of
indirection in Camel using a coarse grained ProtocolBuilder component is
sweet !!! I love it...

Cheers,

Ashwin...



-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com http://fusesource.com 

Blog: http://opensourceknowledge.blogspot.com
http://opensourceknowledge.blogspot.com 
---------------------------------------------------------
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Abstracting-Routes-using-Components-tp3234703p3237867.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to