Recently learn that using nested flow structure for BeanRef processor isn't
working compare to any other currently supported Processors(in FUSE FID) in
other words:
The following configuration where final <to> is inside bean not working,
message gets to the bean and never goes to final output
<root>
<from url="..."/>
<bean ...>
<to url../>
</bean>
</root>
However the following configuration, where final <to> is not a part of bean
element works OK
<root>
<from url="..."/>
<bean .../>
<to url = "..."/>
</root>
Unfortunely it completly break logic of currently implemented FUSE FID
designer export utility :-(
It would be nice to know from expert is this behaviour is a bug in Camel
Runtime: why bean case should be treated differently then any other
processors (according bean's elements schema first configuration is valid
case).
--
View this message in context:
http://www.nabble.com/What-will-be-a-correct-xml-router-configuration-for-bean-reference--tp19780202s22882p19780202.html
Sent from the Camel - Development mailing list archive at Nabble.com.
