Re: AW: AW: CalendarTimers created with TimerService and persistent=true are not persisted over tomee restart

2013-03-05 Thread Romain Manni-Bucau
so jobs are removed at shutdown, so it works *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau*

AW: AW: AW: CalendarTimers created with TimerService and persistent=true are not persisted over tomee restart

2013-03-05 Thread dmitry.volkov
But cron timers with persistent=true should be persisted over JVM restarts. What is the purpose of persistent=true otherwise? http://docs.oracle.com/javaee/6/api/javax/ejb/TimerConfig.html The persistent property determines whether the corresponding timer has a lifetime that spans the JVM in

Re: AW: AW: CalendarTimers created with TimerService and persistent=true are not persisted over tomee restart

2013-03-05 Thread Howard W. Smith, Jr.
You gotta love this Romain guy, a fix for this, a fix for that...even/especially when you (have to) throw the Java EE (6) bible/tutorial (reference implementation) at him! :) By the way, I love that document...Java EE 6 tutorial; that helped me get started almost 2 years ago. On Tue, Mar 5, 2013

NullPointerException in ReloadableEntityManagerFactory.createEntityManager() - 1.5.2.SNAPSHOT

2013-03-05 Thread ymaraner
Testing my application against recent snapshots of 1.5.2 results in a NullPointerException: I have an EAR containing several EJB jars and one WAR file. There are a number of jar files needed by most of the EJB jars that are in the lib directory. One of those jars in the lib directory contains a

How do I deploy?

2013-03-05 Thread Jason Zwolak
I know this is such a basic question and I should be able to just read the docs and follow the instructions... I've read some instructions (see notes below) and tried to follow them but I really have no idea where to begin to deploy my application. Are there instructions somewhere? I cannot

Re: How do I deploy?

2013-03-05 Thread Jason Zwolak
Okay... guess the documentation is correct... just copy the jar to the webapps directory :-) What wasn't clear to me is the URL that I can access my app at after copying the jar. And the maven plugin for Tomee isn't working for me. The URL is

Re: How do I deploy?

2013-03-05 Thread Romain Manni-Bucau
Hi, try mvn tomee:run after having added to the pom: plugin groupIdorg.apache.openejb.maven/groupId artifactIdtomee-maven-plugin/artifactId version1.6.0-SNAPSHOT/version configuration tomeeClassifierjaxrs/tomeeClassifier /configuration

Re: Jax-RS ApplicationPath ignored

2013-03-05 Thread James Green
I got it to break. https://github.com/jmkgreen/jaxrs-twoapp deploy that and watch the root paths disappear. It's just because I added a second JAX-RS Application. I don't see anything in the spec to prevent that. James On 4 March 2013 17:14, Romain Manni-Bucau rmannibu...@gmail.com wrote:

Re: Packaging advice

2013-03-05 Thread Romain Manni-Bucau
Hi It works, ensure you have a beans.xml in each jar + about annotations check your need but @applicationscoped is tempting. Finally sharing your exception can help too Le 5 mars 2013 21:39, James Green james.mk.gr...@gmail.com a écrit : I've spent the past year developing a Java EE 6

Re: Jax-RS ApplicationPath ignored

2013-03-05 Thread John D. Ament
Most other app servers (GF, WebSphere) support it. There's actually a bug in RESTEasy right now blocking it. On Tue, Mar 5, 2013 at 3:42 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Nothing allows it too ;). Defining it through web.xml would work. Through auto discovering...that's not

Re: Packaging advice

2013-03-05 Thread James Green
I only added @Stateless to my @WebService classes because of deployment errors in TomEE. They worked fine in Glassfish. Figured perhaps CDI wasn't as mature in TomEE? Didn't realise beans.xml had to go into each jar. Will add. If I'm reading this right, POJOs @Injected into a SLSB will share the

Re: Packaging advice

2013-03-05 Thread Romain Manni-Bucau
Yes a jar without a beans.xml is not a cdi one. About webservices maybe you hit the fact a pojo one (not ejb) should be defined in web.xml. finally you are right about pooling (but a lot of mongo stuff is thread safe. Producers with scopes (reauest?) can be another answer Le 5 mars 2013 22:13,

Re: Packaging advice

2013-03-05 Thread Romain Manni-Bucau
Jaxrs and jaxws are for sure but for jaxws you need to map them in web.xml Le 5 mars 2013 22:56, James Green james.mk.gr...@gmail.com a écrit : The only producers I have our POJO Factories for my Mongo DAOs. They all @Inject an @ApplicationScoped datasource which itself holds the Mongo client

Re: ActiveMQ in TomEE

2013-03-05 Thread Howard W. Smith, Jr.
Lesson learned! :) Thanks Romain! On Wed, Mar 6, 2013 at 1:53 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Injecting a stateful without scope doesnt make sense since the caller handle the lifecycle of a stateful in such a case (@remove) Le 6 mars 2013 07:35, Howard W. Smith, Jr.

Re: Packaging advice

2013-03-05 Thread James Green
Yeah I think this is where I am coming unstuck with portability. See http://stackoverflow.com/questions/15156171/glassfish-web-xml-servlet-mapping-to-webservice-gets-classcastexceptionfor the problem I was having declaring jaxws services in web.xml portably. Without shipping a jaxws

Re: Packaging advice

2013-03-05 Thread Romain Manni-Bucau
just remove the listener and it works *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/3/6