Hi I'm seeing some strange behaviour that I suspect might come from the fact that I have two Camel-contexts in each it's own Camel Main competing over the same files in a directory. What will actually happen when you let two effectively seperate Camel applications loose at the same directory?
I get some nullpointer-exceptions because at some "random" point Camel reads an empty file and tries to perform transformations on it. I have this setup because I consume two types of files from a remote directory. Then I have two contexts take care of each type of type. If one context picks up an unknown type I throw an exception to roll back the file to the remote dir. This is probably not the greatest idea either, but the only one I could come up with. -- View this message in context: http://camel.465427.n5.nabble.com/Does-Camel-respect-another-context-s-readLock-tp3246756p3246756.html Sent from the Camel - Users mailing list archive at Nabble.com.
