[
https://issues.apache.org/jira/browse/CAMEL-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993426#comment-12993426
]
james strachan commented on CAMEL-3651:
---------------------------------------
Code complete and tested though we could do with some Spring based tests too....
> create a simple way to expose a CamelContext as a black box component that
> can be easily reused in other CamelContext instances
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3651
> URL: https://issues.apache.org/jira/browse/CAMEL-3651
> Project: Camel
> Issue Type: New Feature
> Reporter: james strachan
> Assignee: james strachan
> Fix For: 2.7.0
>
>
> see these discussions for background
> http://camel.465427.n5.nabble.com/implementing-Protocols-or-a-way-to-make-it-easier-to-black-box-routes-and-compose-them-with-other-ros-td3218777.html#a3218777
> http://camel.465427.n5.nabble.com/Abstracting-Routes-using-Components-td3234703.html
> but basically I'm hoping for a simpler alternative than RouteBox...
> http://camel.apache.org/routebox.html
> for a way to take a set of Routes; wrap them up as a CamelContext, register
> it into the Registry (Spring / JNDI / Guice / OSGi etc) and then refer to the
> endpoints inside the black box in a simple way.
> The idea is similar to: https://issues.apache.org/jira/browse/CAMEL-3563 -
> though a different motivation. This issue is about composition; taking a
> CamelContext making it a black box object in the Registry then having a
> simple naming convention to refer to its endpoints.
> To better describe this issue I'll post to the mailing list and document it
> in the wiki and post links to this issue...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
