camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Trenaman <TRENA...@progress.com>
Subject Re: Visibility between camel contexts
Date Tue, 27 Jul 2010 06:00:49 GMT
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

----- Original Message -----
From: Thiago Souza <tcostasouza@gmail.com>
To: users@camel.apache.org <users@camel.apache.org>
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
Sent from the Camel - Users mailing list archive at Nabble.com.
Mime
View raw message