Hi,
In this specific scenario (Timer service) I can't imagine why you
wouldn't want to use EJB Timers, long time supported by the Java EE spec
and EpenEJB/TomEE.
I also see many developers doing complex things using timers and
threads, where Java EE 5/6 async EJBs and JMS would provide for simpler
and more resilient solutions
Sometimes people just look at web and Java SE features and forget about
the entire Java EE stack. ;-)
[]s, Fernando Lozano
Hi,
will be included but not before it is 1) final, 2) we created the
branch for > JavaEE 6 (still dont know if we directly go to JavaEE 7
or we do an intermediate branch like we did before JavaEE 6)
That's said i think the WorkManager is already something interesting in JavaEE.
And about not managed resources...you should be able to use them (we
don't prevent it) but you have to manage it yourself...
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2012/12/7 Howard W. Smith, Jr. <smithh032...@gmail.com>:
I recognized the following blog this morning:
Concurrency Utilities for Java EE Early Draft (JSR 236) [1]
Will this be available at some point in TomEE (and OpenEJB) at some point?
Also, the following was mentioned in the blog:
Using Java SE concurrency utilities such as java.util.concurrent API,
java.lang.Thread andjava.util.Timer in a Java EE application component such
as EJB or Servlet are problematic since the container and server have no
knowledge of these resources.
Is the above statement true with TomEE? I am asking, because I am planning
to use the Timer service in my JSF web app. I did see the TomEE
schedule-expression and schedule-methods examples on the TomEE examples
page, so that tells me that I can use Timer service and 'rely' on it.
Please answer first question above (most of all). Thanks.
[1]
https://blogs.oracle.com/arungupta/entry/concurrency_utilities_for_java_ee
