I was thinking about referring the other direction. In particular, I was looking for a way to avoid repeating complicated URIs within the camelContext. But if you allow references to endpoints within the camelContext, that would probabably be good enough.
James.Strachan wrote: > > On 5/2/07, dr.jeff <[EMAIL PROTECTED]> wrote: >> >> Good stuff. >> It might be useful to be able to refer from the camelContext out into the >> wider Spring beans context (I would find it useful): >> >> <!-- define a URI here --> >> <bean name="foo" class="java.net.URI"> >> <constructor-arg value="jms:queue:cheese.bar"/> >> </bean> >> >> <!-- refer to it here --> >> <bean name=... class=...> >> <property name="foo" ref="foo"/> >> </bean> >> ... >> <!-- also refer to it inside here --> >> <camelContext> >> <endpoint id="foo" ref="foo"/> > > Great idea! > > I've just implemented it as follows... > https://svn.apache.org/repos/asf/activemq/camel/trunk/camel-spring/src/test/resources/org/apache/camel/spring/endpointReference.xml > > where we inject Endpoint instances into a POJO. i.e. you can define > them within a <camelContext> then use them by reference anywhere in > the spring.xml > -- > James > ------- > http://macstrac.blogspot.com/ > > -- View this message in context: http://www.nabble.com/-camel--using-camel-spring-container-tf3663875s2354.html#a10291520 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
