I’ve done “reusable routes” two ways so far. I found the first one in the book "Apache Camel Developer’s Cookbook” - it talks about using Java RouteBuilders as templates for routes and then using Spring to configure the actual instances. I use Blueprint, but the same basic idea.
The second one is using camel-scr - after creating the component, you setup another PID and you have a new instance of the route. Neither of these solutions removes the route after is processes though - you’d have to work through that part. I still don’t quite understand what you’re after with “synchronous”. Basing a service call on the result of FTP download is pretty straightforward, and I’m not sure if the “retry option” you’re talking about is for the FTP polling or for the service call. When you say “synchronous”, do you only want one FTP download going on at a time? Or do you just need resulting actions to be based on the result of the file retrieval? > On Mar 17, 2016, at 3:05 PM, Premkumar <[email protected]> wrote: > > > There are common patterns in route. for example: Picking up from FTP > location, there will be n different ftp sites with different credentials and > pickup directory. How can we make it as reusable routes. > > The reason for going for synchronous route, reason is i need to make some > RESTful service call based on the outcome of the success/failure of route. > another reason handling retries if there are connectivity to FTP/SFTP sites. > Each client provides us different retry option (no of retries and retry > interval to connect to their sites. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Synchronous-One-time-Routing-for-files-tp5779150p5779252.html > Sent from the Camel - Users mailing list archive at Nabble.com.
