It would help to avoid these kind of errors if there was some mechanism in
place to refer to URIs by reference, somewhat in the way that Spring refs
work. If I have:
<!-- constants -->
<bean name="xslt" class="java.lang.String">
<constructor-arg value="./xslt/InputToOutput.xslt"/>
</bean>
then I can do:
<bean id="transformBrook" class="com.syys.camel.interceptor.Transformer"
init-method="init">
<property name="xslt" ref="xslt"/>
</bean>
<bean id="transformTini" class="com.syys.camel.interceptor.Transformer"
init-method="init">
<property name="xslt" ref="xslt"/>
</bean>
...
because I have more than one flow using transformers.
My suggestion is to extend this to the camel-spring.
James.Strachan wrote:
>
>
> You're using 2 different URIs...
>
> * direct:outgoing
> * direct:incoming
>
> shouldn't they be the same? :)
>
> (I've started to use direct:start everywhere as the first entry point
> to a test case to avoid myself getting confused :)
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
>
--
View this message in context:
http://www.nabble.com/-camel--using-camel-spring-container-tf3663875s2354.html#a10277041
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
