I've tried that -- on the simple case just replacing endChoice() with end(). same issue there, and depending where I put it, it changes what it thinks it is from a ChoiceDefinition to a ProcessorDefinition.
I've also tried using .filter. However, that forces 'from' to expose yet a different object which is also incompatible with a RouteDefinition... HELP!! this seems very broken - is it not used much? we started with Spring routes, but ran into a number of restrictions - especially in OSGi that we could not live with, so we decided to go with Java DSL mainly because from everything I've read, it seemed to be what most are using. However, if you can't use choice or filter, it seems fairly useless, no? let me know what the plan is for this and if I should be looking into a different DSL to use ... thanks Claus, always appreciate your quick help! -- View this message in context: http://camel.465427.n5.nabble.com/RouteBuilder-from-exposing-as-a-ChoiceDefinition-rather-than-a-RouteDefinition-tp5743309p5743357.html Sent from the Camel - Users mailing list archive at Nabble.com.
