Thanks James for the quick answer,
>A message can be a File. >http://activemq.apache.org/camel/file.html > >e.g. when routing files from some directory to some processes... > >from("file://some/dir").beanRef("myBean"); > >the body is actually a File object that the bean can process as an >InputStream, Reader, ByteBuffer, byte[], String, DOM or whatever. Two more (stupid) questions on this side: 1- Can we have from("file://some/dir", "file://some/other/file").beanRef("myBean") 2- Is there something like a remote bean execution (on an other machine) ? >> 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 ? >Does an application generate multiple files that you want to group >together? Or just send each file as a separate message to some >processor? Both schemes are valid, I suspect the first case is an optimisation of sending two files in two messages. I will have a look to the pointers. Thanks Guillaume -- View this message in context: http://www.nabble.com/Newbie-question-tp14593953s22882p14597515.html Sent from the Camel - Users mailing list archive at Nabble.com.
