Alex, You can run Camel in a gazillion ways (see http://java.dzone.com/articles/apache-camel-deployment-modes). You can run it as a standalone java app. You can also embed it somewhere (even in an ActiveMQ server if I remember right).
If you go with option 1, you could use servicemix or fabric8. Servicemix comes as a nice complete bundle with Camel+AMQ+CXF+whatnot, that is tested to work together. Fabric8 should be the same. Don´t know if that is too much of overhead for your use case. And referencing a remote broker is fine. The less moving parts - the less maintenance (nightmare). Cheers, Thomas. Am 05.06.2014 um 16:05 schrieb alx <[email protected]>: > Thomas, > yes, you got my problem right. > So my first option, in case I need to send files as messages (files are > usually XML files, but could be graphics as well), would be to embed Camel > in a Java app running on server C with a local route to read from the queue > and write to a local file, referencing the ActiveMQ on server A. Tried that: > it works. > Second option would be create a share on server C, open the related port, > and copy files from remote. > > As far as option 1 I was stuck with running an activemq instance within > camel, but this is not required at all, and referencing a remote broker is > just as easy. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/distributed-file-copy-tp5751920p5751929.html > Sent from the Camel - Users mailing list archive at Nabble.com.
signature.asc
Description: Message signed with OpenPGP using GPGMail
