Hello, I am currently working an application that does use JMS for async communication in one part of the application backend. We use ConcurrentHashMap and CopyOnWriteList to store and retrieve "common/shared data".
These "common data" are then queried by GWT-RPC Servlets. There is a "clean-up thread", that wakes up after 2 hrs to clean up the stale data from these common-data-holders. This has worked pretty well for us. Also, queing/threading has become a breeze with java.util.concurrent.* classes. With Executor/ExecutorServices etc you can very easily write async. multi threaded applications, without bothering about internal details. We are using http://jboss.org/hornetq/ Thanks, Subhro. On Wed, Nov 24, 2010 at 7:35 PM, Baloe <[email protected]> wrote: > Hi, > > Has anyone experience using JMS with GWT? We need something like that, > but the only thing I can find is some tests integrating Spring with > GWT. > > With or without JMS, we need to let some asynchronous processing take > place, preferrably taken after we put some work somewhere on a queue > and not worrying about threading or queueing. Any ideas? > > Thanks! > Niels > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
