Hi there, My suggestion would be to host your camel application in a container such as Karaf/SMX and run it as a OS service. This will allow you to restart your container automatically on a failure etc.
It would be advisable to make use of Transactions in your routes and a persisted transport mechanism to ensure information is not lost on error. Finally; You can easily avoid the need for a 'dynamic endpoint' if you treat your application as a service, and take advantage of SOA - Service Orientated Architecture. As such, you will benefit from having a WS/RS which exposes the required operation for your use case, and you simply treat your 'file endpoints' as data for this operation. This enables you to become completely decoupled from Camel and any other architectural choices you may have chosen. Alan -- View this message in context: http://camel.465427.n5.nabble.com/Web-based-camel-route-automation-tp5738797p5738849.html Sent from the Camel - Users mailing list archive at Nabble.com.
