I've been using Java's executor service lately and it's very neat. http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html
It's just that I don't think it can guarantee a new thread for each request in case you are using per-thread scope services. On Wed, Jun 13, 2012 at 4:37 PM, Dmitry Gusev <dmitry.gu...@gmail.com>wrote: > You need Java EE if you want to use Java Message Service, or you can use > Apache TomEE which implements JMS (http://tomee.apache.org/tomcat-jms.html > ) > -- I haven't used TomEE though. > > Or you can implement your own queue (based on ArrayBlockingQueue, for > instance) with consumer thread(s) which you should start manually. > > Both approaches have their pros and cons, though. > > On Wed, Jun 13, 2012 at 6:04 PM, Angelo C. <angelochen...@gmail.com> > wrote: > > > no, i don't need the response from the method, MS/JMS is new to me, can > it > > be > > used even I 'm not using Java EE? > > > > > > Dmitry Gusev wrote > > > > > > Do you plan to consume method's response in the same request? > > > > > > If not, some sort of MQ/JMS may be an option--just put your message > there > > > and return. > > > The message itself will be processed in separate thread with MQ handler > > > (Message-Driven Bean in case of Java EE). > > > > > > Dmitry Gusev > > > > > > AnjLab Team > > > http://anjlab.com > > > > > > > > > -- > > View this message in context: > > > http://tapestry.1045711.n5.nabble.com/non-blocking-code-in-T5-tp5713836p5713841.html > > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > > -- > Dmitry Gusev > > AnjLab Team > http://anjlab.com > -- *Regards,* *Muhammad Gelbana Java Developer*
