On 8/26/07, steven.marcus <[EMAIL PROTECTED]> wrote: > > Is there any chance that support for bean method invocations on the event > dispatch thread could be added? > > The URI might look something like: > > bean:foo?methodName=addBar&EDT=true > > Some way to tell @MessageDriven that it should dispatch on the EDT would be > really nice too...
Whats the event driven thread? Are you talking Swing/UI stuff? If so we could maybe have a component/endpoint to process messages in the EDT. e.g. like the SEDA component, but the messages would be processed in the EDT... http://activemq.apache.org/camel/seda.html Then the beans could be bound to URIs "edt:someName" then some route could go from whatever the input is to the EDT uri? Or maybe we just have an EDT component which invokes beans? So binding to edt:beanName?methodName=foo > I'm new to camel, but so far the refactoring of our project where we try out > using camel, spring, spring-javaconfig, and maven, is going very well. There > has been a large reduction and simplification of the code, and a new clarity > in the architecture... thanks! Great, thats good to know! -- James ------- http://macstrac.blogspot.com/
