camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Visibility between camel contexts
Date Tue, 27 Jul 2010 12:43:42 GMT
On Tue, Jul 27, 2010 at 2:41 PM, Thiago Souza <tcostasouza@gmail.com> wrote:
>
> Hi,
>
>    My current understanding is that components should be  considered as
> isolated from each other. And Camel context is just the way to organize and
> configure routes.
>
>    The problem is that camel context modularization support is not good
> enough. For example, in this case, by separating endpoints and routes in xml
> files I could use a different endpoint configuration set for test and
> production environment and still keeping the same routing xml.
>

See chapter 6 in the Camel in Action book which covers how to do this.
6.1.6 Unit testing in multiple environments



>    For this specific situation I guess I could use RouteContextRef or even
> Java DSL but that's not what I want. What I am really looking for is a way
> to make dynamic xml configuration contributions to existing camel context
> instances.
>
> Regards,
> Thiago Souza
>
> On Jul 27, 2010 3:02 AM, "Adrian Trenaman-2 [via Camel]" <
> ml-node+2255475-1717021524-15243@n5.nabble.com<ml-node%2B2255475-1717021524-15243@n5.nabble.com>>
> wrote:
> In general, Camel contexts should be considered as isolated from each other
> (this is by design!). To communicate between Camel contexts, consider using
> the VM or JMS transports.
>
> Right now, what you're trying to do by separating the endpoints from the
> routes won't work - as you have found out! Is there a reason why you're
> separating the two?
>
> Cheers,
> Ade
>
> http://fusesource.com <http://fusesource.com?by-user=t>
>
> ----- Original Message -----
> From: Thiago Souza <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=2255475&i=0>>
>
> To: [hidden email]
> <http://user/SendEmail.jtp?type=node&node=2255475&i=1> <[hidden
> email] <http://user/SendEmail.jtp?type=node&node=2255475&i=2>>
> Sent: Mon Jul 26 23:58:05 2010
> Subject: Visibility between camel contexts
>
>
> Hi,
>
>      In a standalone spring application context the following is perfectly
> fine:
>
>
>  <c:camelContext id="endpoints">
>                <c:endpoint id="source" uri="file://source" />
>                <c:endpoint id="target" uri="file://target" />
>        </c:camelContext>
>
>  <c:camelContext id="routes">
>                <c:route>
>                        <c:from ref="source" />
>                        <c:to ref="target" />
>                </c:route>
>        </c:camelContext>
>
>
>       That is, the configured camelContexts can see each other. Is it
> possible to achieve this in Karaf?  (i.e. "endpoints" goes in a xml and
> "routes" goes in another one)
>
>        I've tried with no success, the xml containing "routes" can not see
> the endpoints defined in "endpoints" (in another xml)
>
> Regards,
> Thiago Souza
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Visibility-between-camel-contexts-tp2255423p2255423.html<http://camel.465427.n5.nabble.com/Visibility-between-camel-contexts-tp2255423p2255423.html?by-user=t>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
> ------------------------------
>  View message @
> http://camel.465427.n5.nabble.com/Visibility-between-camel-contexts-tp2255423p2255475.html
> To unsubscribe from Visibility between camel contexts, click
> here< (link removed) =>.
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Visibility-between-camel-contexts-tp2255423p2255766.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Mime
View raw message