- This is always a good practice to increase readability of the camel DSL or its reusability by using the "direct" component for sync exchanges - Exposing your rules/conditions using the Camel DSL (like choice().when()) offers the advantage that the logic is visible and not encapsulated with java beans/pojo. So this is good practice too to define as much as possible the business logic as you did
On Mon, Sep 22, 2014 at 9:05 AM, imranrazakhan <imranrazak...@gmail.com> wrote: > Hi, > > Thanks, > > 1- I want to improve syntax. > 2- As i am using multiple choices so any better way to handle it. > 3- Can we break one big route into multiple for more good readability. > 4- Any other suggestion to improve syntax design as i am getting data in > table(no other trigger available) so polling from one table and run > business > logic and save result in other table. > > Regards, > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Route-Design-Suggetion-tp5756825p5756831.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
