James.Strachan wrote: > > 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 >
Yes, EDT=event dispatch thread, used by AWT and Swing and defines a "thread compartment" for all gui objects. As you say, implementing an edt component, like seda, makes more sense. I'll look at the seda component and cobble together an edt component. Note that there are two ways to dispatch, synchronously and asynchronously: SwingUtilities.invokeAndWait SwingUtilities.invokeLater If there is a need to participate in transactions invokeAndWait needs to be supported too... Can seda processors participate in transactions? thanks again! Steven Marcus ps. there is an SWT thread which is analogous but incompatible with the EDT, so SWT users may ask for an SWT component... -- View this message in context: http://www.nabble.com/bean-method-invocations-on-EDT-tf4329507s22882.html#a12339298 Sent from the Camel - Users mailing list archive at Nabble.com.
