On Mon, Mar 22, 2010 at 11:06 AM, Drasil <pavel.dra...@gmail.com> wrote: > > So if I understand you correctly, there is currently no reasonable solution > to this issue (except from casting the end() method result or switching to > XML-based configuration) and chances are it will be fixed in the next Camel > release. Right? >
Yeah it should be possible to fix that for 2.3. But in the long run using Scala etc. for DSL will allow a much better foundation for that than what Java and its _somewhat poor_ generics can offer for DSL. I created ticket https://issues.apache.org/activemq/browse/CAMEL-2567 > > Claus Ibsen-2 wrote: >> >> I got it working here locally with some changes in the DSL. >> I will "play" with a bit more to see if it dont break to much. >> >> The problem is many of the EIP can be configured further using their >> own builder methods and as you said end() is reverting back to a too >> generic type. >> It gotta "remember" its current scope and return back the >> ChoiceDefinition. >> >> Btw Spring XML does not have this issue as you can stack the XML tags >> as you like. >> > > -- > View this message in context: > http://old.nabble.com/RecipientList-%2B-Choice-no-longer-work-together-in-Camel-2.2.0--tp27983922p27984287.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
