Re: EJBContainer

2015-05-29 Thread Andy Gumbrecht
Agree, a test needs something to test. Maybe we should change the message to add a hint? Andy. On 28 May 2015 at 14:25, Romain Manni-Bucau rmannibu...@gmail.com wrote: Well it is the way it is done. If nothing to deploy it fails. Forcing the MODULES it should work Le 28 mai 2015 01:58, Alex

Re: tomee jee 7

2015-05-29 Thread Jean-Louis Monteiro
+1 -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, May 28, 2015 at 11:29 PM, Alex Soto asot...@gmail.com wrote: Short answer, I think so in fact it is almost there because lot of TomEE API has already migrated. Real answer, any hand is more than

Re: BUG ON APACHE TOMCAT 8, 7, AND TOMEE 1.7

2015-05-29 Thread Romain Manni-Bucau
Hi THIS IS NOT A BUG (joke apart try to not write in uppercase;)) this is a bug in netbeans, just rename tomee-common-x.x.x.jar to tomee-common-1.6.0.jar and it should work. Anycase it should go on netbeans bugtracker. Romain Manni-Bucau @rmannibucau https://twitter.com/rmannibucau | Blog

Re: BUG ON APACHE TOMCAT 8, 7, AND TOMEE 1.7

2015-05-29 Thread Howard W. Smith, Jr.
2015-05-29 0:31 GMT-04:00 JESUS GEIDER GUERRA HERNANDEZ jgguer...@misena.edu.co: I create a Session Beans For Entity Classess, the message show up this: Cannot be generated for Java EE 6 sources without server with complete Java EE 6 Web Profile support (at least EJB Lite support). I see

BUG ON APACHE TOMCAT 8, 7, AND TOMEE 1.7

2015-05-29 Thread JESUS GEIDER GUERRA HERNANDEZ
Hi, I actually studyign programing, so, I have some excersices for creating JSF web and including connection to database, the bug appears when I create a Session Beans For Entity Classess, the message show up this: Cannot be generated for Java EE 6 sources without server with complete Java EE

Re: BUG ON APACHE TOMCAT 8, 7, AND TOMEE 1.7

2015-05-29 Thread Jean-Louis Monteiro
Do you have a sample to reproduce ? Le 29 mai 2015 12:23, JESUS GEIDER GUERRA HERNANDEZ jgguer...@misena.edu.co a écrit : Hi, I actually studyign programing, so, I have some excersices for creating JSF web and including connection to database, the bug appears when I create a Session Beans

Re: tomee jee 7

2015-05-29 Thread Alex Soto
I have some suggestions, I will send you an email privately. Alex. El dv., 29 maig 2015 a les 11:06, Jean-Louis Monteiro ( jlmonte...@tomitribe.com) va escriure: +1 -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, May 28, 2015 at 11:29 PM, Alex

Re: java.lang.instrument ASSERTION FAILED when running JNDI dump in ejb-example

2015-05-29 Thread Thusitha Thilina Dayaratne
Hi, yep, should be org.apache.openjpa:openjpa:2.4.0 + the openejb-javaagent should be in place, also assume you use -ea option. Thanks for the response. I've set the JAVA_OPTS as follows in my server startup script and put the javaagent jar in the mentioned position. But I'm still getting the

Re: Long running background tasks using Java EE 6

2015-05-29 Thread Lars-Fredrik Smedberg
@Romain If the long running task (started as an @Asynchronous EJB method) is periodacally sleeping for say 1 minute and then perform some tasks and goes to sleep again Would it then be okay to on the EJB class level have a: private volatile Therad asynchronousThread; variable... The

Re: Long running background tasks using Java EE 6

2015-05-29 Thread Romain Manni-Bucau
2015-05-29 14:55 GMT+02:00 Lars-Fredrik Smedberg itsme...@gmail.com: @Romain If the long running task (started as an @Asynchronous EJB method) is periodacally sleeping for say 1 minute and then perform some tasks and goes to sleep again Would it then be okay to on the EJB class level

Re: Long running background tasks using Java EE 6

2015-05-29 Thread Lars-Fredrik Smedberg
@Romain Thanks for the answer I use a boolean now... the problem (if any) is that using a boolean flag is that the shutdown will take atleast the time the wait interval is Did you then mean I need to in the @PreDestroy wait for the async thread to finish and exit? About the thread and

Re: Long running background tasks using Java EE 6

2015-05-29 Thread Lars-Fredrik Smedberg
@Romain Got it... so do i need in @PreDestroy method to wait for the async method to pick up the boolean variable change and exit before exiting @PreDestroy method or will application shutdown wait a certain amount of time for async method executions to finish? On May 29, 2015 3:40 PM, Romain

Re: Long running background tasks using Java EE 6

2015-05-29 Thread Romain Manni-Bucau
yep, a CountDownLatch is perfect for it Romain Manni-Bucau @rmannibucau https://twitter.com/rmannibucau | Blog http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau | LinkedIn https://www.linkedin.com/in/rmannibucau | Tomitriber http://www.tomitribe.com 2015-05-29 15:45

Re: Long running background tasks using Java EE 6

2015-05-29 Thread Lars-Fredrik Smedberg
 On May 29, 2015 3:48 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: yep, a CountDownLatch is perfect for it Romain Manni-Bucau @rmannibucau https://twitter.com/rmannibucau | Blog http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau | LinkedIn

TomEE comparision page; SSL errors

2015-05-29 Thread jieryn
https://tomee.apache.org/comparison.html This page references images off site and behind an ASF protected authentication. It seems it would just be easier to put an 'x' mark instead and avoid these SSL issues. Also, the firefox is complaining about this page's SSL certificate.

Re: Long running background tasks using Java EE 6

2015-05-29 Thread Romain Manni-Bucau
it depends also on your config but if you have another task finishing after (singleton) which starts an asynch task as well here you can force your pool to recreate thread. Then add a custom pool config and you are lost about what will happen ;) the point point is to handle the level you use (you

Re: Long running background tasks using Java EE 6

2015-05-29 Thread Lars-Fredrik Smedberg
@Romain Just tried it out in a testcase... boolean for stopping and countdownlatch for waiting in the predestroy method until the async method has ended is working good... Thanks for the hints... However I still little curious when you wrote: You dont have by default one thread by task but a