I find the idea of the Camel DSL pretty interesting. While I see typical enterprise scenario for using Camel, I am still wondering if it can be used for what I am doing. Therefore, I would be interested to receive your comments. I am mainly involved in scientific computing where we have to chain different applications. An application is (roughly) a piece of code that "eat" and "produce" files (nothing ambitious so far ;-) - files might be (very) large. Then we want to chain the applications, some output files going to some app, some others possibly to other apps.
So it looks quite different to the message model used by Camel. Should I consider that the different files generated by an application belong to the same "message" then multicast and filter the message so that the next applications only get what they need ? Are files (and moving files around) something "natural" in Camel ? Thanks for your feedback. Cheers Guillaume. PS: Any groovy example around ? -- View this message in context: http://www.nabble.com/Newbie-question-tp14593953s22882p14593953.html Sent from the Camel - Users mailing list archive at Nabble.com.
