Type: New Feature
Affects Version/s: None
Fix Version/s: 2.6.0
Given below is the discussion forum thread that spawned this thought.
Need a Camel component (called Backbox, maybe) that can nicely expose a ProtocolBuilder endpoint that does the following
a> Instantiate route definitions/route(s) configured in Spring or DSL at startup
b> Launch a Producer or Consumer with a well known protocol(s) so that a client can invoke it (could be direct or seda initially but could be any protocol... really) . Must support multiple consumer endpoints and routes using a URI scheme.
c> redirect received payloads (with marshalling into an exchange if necessary) to the inner route(s) since they are launched and started. If there are multiple inner routes with many consumers, we could expect the user to provide a clue using the payload and/or an exchange property as to how the payload should be routed.
d> Extend from a Default Consumer, Producer, Endpoint and Component.
e> Internally manage inner route lifecycles and operations.