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"/>
...
James.Strachan wrote:
>
> Yeah, we could definitely have some kinda mechanism like that. Maybe
>
> <camelContext>
> <endpoint id="foo" uri="jms:queue:cheese.bar"/>
> <endpoint id="bar" uri="jms:queue:cheese.bar"/>
>
> ....
>
> <from ref="foo"/>
> <to ref="bar"/>
>
> etc
>
> Another option is to allow URIs themselves to be references. e.g. we
> could have some kinda way of making an alias to a URI (using some
> kinda syntax as above), then we could use a uri of the form
>
> ref:referenceName to refer to it?
>
> <camelContext>
> <endpoint id="foo" uri="jms:queue:cheese.bar"/>
> <endpoint id="bar" uri="jms:queue:cheese.bar"/>
>
> ....
>
> <from uri="ref:foo"
> <to uri="ref:bar"/>
>
>
>
--
View this message in context:
http://www.nabble.com/-camel--using-camel-spring-container-tf3663875s2354.html#a10289533
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
