Re: 2.0.0-SNAPSHOT @provider and @inject
Hi Is the provider is scanned it is injected. Do you have a sample showing it? Le jeudi 6 novembre 2014, hwaastad he...@waastad.org a écrit : Hi, @inject/@ejb in a @provider resolves to null. is this WIP? br hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/2-0-0-SNAPSHOT-provider-and-inject-tp4672772.html Sent from the TomEE Users mailing list archive at Nabble.com. -- Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau
Re: TomEE plans for Java EE 7
Hi Will not be enough cause of descriptor part but this one is easier to dev now Le jeudi 6 novembre 2014, John D. Ament john.d.am...@gmail.com a écrit : Hey all, First, cudos to Roberto for taking on the TomEE support! It came to my mind after speaking w/ David @ JavaOne about EE7 status. So quick question. If we put in hibernate in the TomEE profile, that should deploy fine right? I'm not saying for you guys to put it in, but for the sake of the EE sample tests that might help with the JPA 2.1 tests. John On Wed, Nov 5, 2014 at 12:06 PM, Roberto Cortez radcor...@yahoo.com.invalid wrote: Great! Thanks, I'll add it in the next run :) From: Romain Manni-Bucau rmannibu...@gmail.com To: Roberto Cortez radcor...@yahoo.com Cc: users@tomee.apache.org users@tomee.apache.org; David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 5:01 PM Subject: Re: TomEE plans for Java EE 7 seems tomee embedded profile misses at least (tomee-embedded doesn't provide it by default, tomee-plus should if you want to use tomee-remote with plus classifier configured): dependency groupIdorg.apache.batchee/groupId artifactIdbatchee-jbatch/artifactId version0.2-incubating/version /dependency dependency groupIdorg.apache.johnzon/groupId artifactIdjohnzon-core/artifactId version0.1-incubating/version /dependency Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:55 GMT+00:00 Romain Manni-Bucau rmannibu...@gmail.com: great, thks Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:51 GMT+00:00 Roberto Cortez radcor...@yahoo.com: Ok, Jenkins archiving was killing the machine disk space. I had to delete and create a new job. It's running now and should be accessible on the same url: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ From: Roberto Cortez radcor...@yahoo.com.INVALID To: Romain Manni-Bucau rmannibu...@gmail.com; users@tomee.apache.org users@tomee.apache.org Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:42 PM Subject: Re: TomEE plans for Java EE 7 Yeah give me a sec, the job was taking too much space From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:38 PM Subject: Re: TomEE plans for Java EE 7 Hello Roberto, is it broken again? I get 404 Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 11:44 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid : Hi, We got our account back, so the tests are now running in CI with the latest TomEE 2.0 SNAPSHOT: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ Cheers, Roberto From: Roberto Cortez radcor...@yahoo.com To: David Blevins david.blev...@gmail.com; users@tomee.apache.org users@tomee.apache.org Sent: Monday, November 3, 2014 9:19 AM Subject: Re: TomEE plans for Java EE 7 Hi David, Thanks for a warm welcome :) The samples are setup with TomEE 2.0-SNAPSHOT already. We were using the Cloudbees - Jenkins FOSS, but for some reason it's unavailable. They are looking into it. Cheers,Roberto From: David Blevins david.blev...@gmail.com To: users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Sent: Monday, November 3, 2014 8:24 AM Subject: Re: TomEE plans for Java EE 7 First -- welcome, Roberto! Great to see you on the list :) We should definitely try with TomEE 2.0-SNAPSHOT. Would be great to track these. What CI are you using? We could set something up on the Apache side if needed. -David On Sun, Nov 2, 2014 at 1:35 PM, Roberto Cortez radcor...@yahoo.com.invalid wrote: Hi guys, I just subscribed to the list, so this is my first email here. I'm currently contributing to a Java EE 7 samples project here: https://github.com/javaee-samples/javaee7-samples, and I just added profiles to run the samples in TomEE and TomEE Embedded. Running the samples / tests we got the following results: batch - No Implementation Providedcdi - Failing a few tests. Most are related with the absence of a beans.xmlconcurrency - Failing a few tests. DefaultManagedExecutorService not binded to JNDI comp/DefaultManagedExecutorServiceejb - Failure in TimerServiceel - Missing Lambda
Re: TomEE plans for Java EE 7
Hi, Thank you John! I just added the dependencies for batch as well in https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/, so that took care of a few missing tests. Now it seems that a lot of tests are failing because there is no beans.xml, since on Java EE 7 the description it's optional. Cheers,Roberto From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org Sent: Thursday, November 6, 2014 8:37 AM Subject: Re: TomEE plans for Java EE 7 Hi Will not be enough cause of descriptor part but this one is easier to dev now Le jeudi 6 novembre 2014, John D. Ament john.d.am...@gmail.com a écrit : Hey all, First, cudos to Roberto for taking on the TomEE support! It came to my mind after speaking w/ David @ JavaOne about EE7 status. So quick question. If we put in hibernate in the TomEE profile, that should deploy fine right? I'm not saying for you guys to put it in, but for the sake of the EE sample tests that might help with the JPA 2.1 tests. John On Wed, Nov 5, 2014 at 12:06 PM, Roberto Cortez radcor...@yahoo.com.invalid wrote: Great! Thanks, I'll add it in the next run :) From: Romain Manni-Bucau rmannibu...@gmail.com To: Roberto Cortez radcor...@yahoo.com Cc: users@tomee.apache.org users@tomee.apache.org; David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 5:01 PM Subject: Re: TomEE plans for Java EE 7 seems tomee embedded profile misses at least (tomee-embedded doesn't provide it by default, tomee-plus should if you want to use tomee-remote with plus classifier configured): dependency groupIdorg.apache.batchee/groupId artifactIdbatchee-jbatch/artifactId version0.2-incubating/version /dependency dependency groupIdorg.apache.johnzon/groupId artifactIdjohnzon-core/artifactId version0.1-incubating/version /dependency Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:55 GMT+00:00 Romain Manni-Bucau rmannibu...@gmail.com: great, thks Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:51 GMT+00:00 Roberto Cortez radcor...@yahoo.com: Ok, Jenkins archiving was killing the machine disk space. I had to delete and create a new job. It's running now and should be accessible on the same url: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ From: Roberto Cortez radcor...@yahoo.com.INVALID To: Romain Manni-Bucau rmannibu...@gmail.com; users@tomee.apache.org users@tomee.apache.org Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:42 PM Subject: Re: TomEE plans for Java EE 7 Yeah give me a sec, the job was taking too much space From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:38 PM Subject: Re: TomEE plans for Java EE 7 Hello Roberto, is it broken again? I get 404 Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 11:44 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid : Hi, We got our account back, so the tests are now running in CI with the latest TomEE 2.0 SNAPSHOT: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ Cheers, Roberto From: Roberto Cortez radcor...@yahoo.com To: David Blevins david.blev...@gmail.com; users@tomee.apache.org users@tomee.apache.org Sent: Monday, November 3, 2014 9:19 AM Subject: Re: TomEE plans for Java EE 7 Hi David, Thanks for a warm welcome :) The samples are setup with TomEE 2.0-SNAPSHOT already. We were using the Cloudbees - Jenkins FOSS, but for some reason it's unavailable. They are looking into it. Cheers,Roberto From: David Blevins david.blev...@gmail.com To: users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Sent: Monday, November 3, 2014 8:24 AM Subject: Re: TomEE plans for Java EE 7 First -- welcome, Roberto! Great to see you on the list :) We should definitely try with TomEE 2.0-SNAPSHOT. Would be great to track these. What CI are you using? We could set something up on the Apache side if needed. -David On Sun, Nov 2, 2014 at 1:35 PM, Roberto Cortez radcor...@yahoo.com.invalid wrote: Hi guys, I just subscribed to the list, so this is my first email here. I'm currently contributing to a
Re: TomEE plans for Java EE 7
pushed few things about it this morning, not sure it will help these particular tests but hopefully it will Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 9:52 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid: Hi, Thank you John! I just added the dependencies for batch as well in https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/, so that took care of a few missing tests. Now it seems that a lot of tests are failing because there is no beans.xml, since on Java EE 7 the description it's optional. Cheers,Roberto From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org Sent: Thursday, November 6, 2014 8:37 AM Subject: Re: TomEE plans for Java EE 7 Hi Will not be enough cause of descriptor part but this one is easier to dev now Le jeudi 6 novembre 2014, John D. Ament john.d.am...@gmail.com a écrit : Hey all, First, cudos to Roberto for taking on the TomEE support! It came to my mind after speaking w/ David @ JavaOne about EE7 status. So quick question. If we put in hibernate in the TomEE profile, that should deploy fine right? I'm not saying for you guys to put it in, but for the sake of the EE sample tests that might help with the JPA 2.1 tests. John On Wed, Nov 5, 2014 at 12:06 PM, Roberto Cortez radcor...@yahoo.com.invalid wrote: Great! Thanks, I'll add it in the next run :) From: Romain Manni-Bucau rmannibu...@gmail.com To: Roberto Cortez radcor...@yahoo.com Cc: users@tomee.apache.org users@tomee.apache.org; David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 5:01 PM Subject: Re: TomEE plans for Java EE 7 seems tomee embedded profile misses at least (tomee-embedded doesn't provide it by default, tomee-plus should if you want to use tomee-remote with plus classifier configured): dependency groupIdorg.apache.batchee/groupId artifactIdbatchee-jbatch/artifactId version0.2-incubating/version /dependency dependency groupIdorg.apache.johnzon/groupId artifactIdjohnzon-core/artifactId version0.1-incubating/version /dependency Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:55 GMT+00:00 Romain Manni-Bucau rmannibu...@gmail.com: great, thks Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:51 GMT+00:00 Roberto Cortez radcor...@yahoo.com: Ok, Jenkins archiving was killing the machine disk space. I had to delete and create a new job. It's running now and should be accessible on the same url: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ From: Roberto Cortez radcor...@yahoo.com.INVALID To: Romain Manni-Bucau rmannibu...@gmail.com; users@tomee.apache.org users@tomee.apache.org Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:42 PM Subject: Re: TomEE plans for Java EE 7 Yeah give me a sec, the job was taking too much space From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:38 PM Subject: Re: TomEE plans for Java EE 7 Hello Roberto, is it broken again? I get 404 Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 11:44 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid : Hi, We got our account back, so the tests are now running in CI with the latest TomEE 2.0 SNAPSHOT: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ Cheers, Roberto From: Roberto Cortez radcor...@yahoo.com To: David Blevins david.blev...@gmail.com; users@tomee.apache.org users@tomee.apache.org Sent: Monday, November 3, 2014 9:19 AM Subject: Re: TomEE plans for Java EE 7 Hi David, Thanks for a warm welcome :) The samples are setup with TomEE 2.0-SNAPSHOT already. We were using the Cloudbees - Jenkins FOSS, but for some reason it's unavailable. They are looking into it. Cheers,Roberto From: David Blevins david.blev...@gmail.com To: users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Sent: Monday, November 3, 2014 8:24 AM Subject: Re: TomEE plans for Java EE 7 First -- welcome, Roberto! Great to see you on the list :) We should definitely try with TomEE 2.0-SNAPSHOT. Would be great to
Re: TomEE plans for Java EE 7
Great! Kicking out new builds. Anyway, I'm very interested in contributing with this effort. Maybe you can help / guide me on something? Cheers,Roberto From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Sent: Thursday, November 6, 2014 10:32 AM Subject: Re: TomEE plans for Java EE 7 pushed few things about it this morning, not sure it will help these particular tests but hopefully it will Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 9:52 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid: Hi, Thank you John! I just added the dependencies for batch as well in https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/, so that took care of a few missing tests. Now it seems that a lot of tests are failing because there is no beans.xml, since on Java EE 7 the description it's optional. Cheers,Roberto From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org Sent: Thursday, November 6, 2014 8:37 AM Subject: Re: TomEE plans for Java EE 7 Hi Will not be enough cause of descriptor part but this one is easier to dev now Le jeudi 6 novembre 2014, John D. Ament john.d.am...@gmail.com a écrit : Hey all, First, cudos to Roberto for taking on the TomEE support! It came to my mind after speaking w/ David @ JavaOne about EE7 status. So quick question. If we put in hibernate in the TomEE profile, that should deploy fine right? I'm not saying for you guys to put it in, but for the sake of the EE sample tests that might help with the JPA 2.1 tests. John On Wed, Nov 5, 2014 at 12:06 PM, Roberto Cortez radcor...@yahoo.com.invalid wrote: Great! Thanks, I'll add it in the next run :) From: Romain Manni-Bucau rmannibu...@gmail.com To: Roberto Cortez radcor...@yahoo.com Cc: users@tomee.apache.org users@tomee.apache.org; David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 5:01 PM Subject: Re: TomEE plans for Java EE 7 seems tomee embedded profile misses at least (tomee-embedded doesn't provide it by default, tomee-plus should if you want to use tomee-remote with plus classifier configured): dependency groupIdorg.apache.batchee/groupId artifactIdbatchee-jbatch/artifactId version0.2-incubating/version /dependency dependency groupIdorg.apache.johnzon/groupId artifactIdjohnzon-core/artifactId version0.1-incubating/version /dependency Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:55 GMT+00:00 Romain Manni-Bucau rmannibu...@gmail.com: great, thks Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:51 GMT+00:00 Roberto Cortez radcor...@yahoo.com: Ok, Jenkins archiving was killing the machine disk space. I had to delete and create a new job. It's running now and should be accessible on the same url: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ From: Roberto Cortez radcor...@yahoo.com.INVALID To: Romain Manni-Bucau rmannibu...@gmail.com; users@tomee.apache.org users@tomee.apache.org Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:42 PM Subject: Re: TomEE plans for Java EE 7 Yeah give me a sec, the job was taking too much space From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:38 PM Subject: Re: TomEE plans for Java EE 7 Hello Roberto, is it broken again? I get 404 Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 11:44 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid : Hi, We got our account back, so the tests are now running in CI with the latest TomEE 2.0 SNAPSHOT: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ Cheers, Roberto From: Roberto Cortez radcor...@yahoo.com To: David Blevins david.blev...@gmail.com; users@tomee.apache.org users@tomee.apache.org Sent: Monday, November 3, 2014 9:19 AM Subject: Re: TomEE plans for Java EE 7 Hi David, Thanks for a warm welcome :) The samples are setup with TomEE 2.0-SNAPSHOT already. We were using the Cloudbees - Jenkins FOSS, but for some reason it's
Re: TomEE plans for Java EE 7
On CDI entry points are: 1) AnnotationDeployer#getBeanClasses 2) CdiScanner Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-11-06 10:40 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid: Great! Kicking out new builds. Anyway, I'm very interested in contributing with this effort. Maybe you can help / guide me on something? Cheers,Roberto From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Sent: Thursday, November 6, 2014 10:32 AM Subject: Re: TomEE plans for Java EE 7 pushed few things about it this morning, not sure it will help these particular tests but hopefully it will Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 9:52 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid: Hi, Thank you John! I just added the dependencies for batch as well in https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/, so that took care of a few missing tests. Now it seems that a lot of tests are failing because there is no beans.xml, since on Java EE 7 the description it's optional. Cheers,Roberto From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org Sent: Thursday, November 6, 2014 8:37 AM Subject: Re: TomEE plans for Java EE 7 Hi Will not be enough cause of descriptor part but this one is easier to dev now Le jeudi 6 novembre 2014, John D. Ament john.d.am...@gmail.com a écrit : Hey all, First, cudos to Roberto for taking on the TomEE support! It came to my mind after speaking w/ David @ JavaOne about EE7 status. So quick question. If we put in hibernate in the TomEE profile, that should deploy fine right? I'm not saying for you guys to put it in, but for the sake of the EE sample tests that might help with the JPA 2.1 tests. John On Wed, Nov 5, 2014 at 12:06 PM, Roberto Cortez radcor...@yahoo.com.invalid wrote: Great! Thanks, I'll add it in the next run :) From: Romain Manni-Bucau rmannibu...@gmail.com To: Roberto Cortez radcor...@yahoo.com Cc: users@tomee.apache.org users@tomee.apache.org; David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 5:01 PM Subject: Re: TomEE plans for Java EE 7 seems tomee embedded profile misses at least (tomee-embedded doesn't provide it by default, tomee-plus should if you want to use tomee-remote with plus classifier configured): dependency groupIdorg.apache.batchee/groupId artifactIdbatchee-jbatch/artifactId version0.2-incubating/version /dependency dependency groupIdorg.apache.johnzon/groupId artifactIdjohnzon-core/artifactId version0.1-incubating/version /dependency Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:55 GMT+00:00 Romain Manni-Bucau rmannibu...@gmail.com: great, thks Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:51 GMT+00:00 Roberto Cortez radcor...@yahoo.com: Ok, Jenkins archiving was killing the machine disk space. I had to delete and create a new job. It's running now and should be accessible on the same url: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ From: Roberto Cortez radcor...@yahoo.com.INVALID To: Romain Manni-Bucau rmannibu...@gmail.com; users@tomee.apache.org users@tomee.apache.org Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:42 PM Subject: Re: TomEE plans for Java EE 7 Yeah give me a sec, the job was taking too much space From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:38 PM Subject: Re: TomEE plans for Java EE 7 Hello Roberto, is it broken again? I get 404 Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 11:44 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid : Hi, We got our account back, so the tests are now running in CI with the latest TomEE 2.0 SNAPSHOT: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ Cheers, Roberto From: Roberto Cortez radcor...@yahoo.com To: David Blevins
Re: TomEE plans for Java EE 7
Thanks! I'll have a look. From: Romain Manni-Bucau rmannibu...@tomitribe.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Sent: Thursday, November 6, 2014 11:10 AM Subject: Re: TomEE plans for Java EE 7 On CDI entry points are: 1) AnnotationDeployer#getBeanClasses 2) CdiScanner Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-11-06 10:40 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid: Great! Kicking out new builds. Anyway, I'm very interested in contributing with this effort. Maybe you can help / guide me on something? Cheers,Roberto From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Sent: Thursday, November 6, 2014 10:32 AM Subject: Re: TomEE plans for Java EE 7 pushed few things about it this morning, not sure it will help these particular tests but hopefully it will Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 9:52 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid: Hi, Thank you John! I just added the dependencies for batch as well in https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/, so that took care of a few missing tests. Now it seems that a lot of tests are failing because there is no beans.xml, since on Java EE 7 the description it's optional. Cheers,Roberto From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org Sent: Thursday, November 6, 2014 8:37 AM Subject: Re: TomEE plans for Java EE 7 Hi Will not be enough cause of descriptor part but this one is easier to dev now Le jeudi 6 novembre 2014, John D. Ament john.d.am...@gmail.com a écrit : Hey all, First, cudos to Roberto for taking on the TomEE support! It came to my mind after speaking w/ David @ JavaOne about EE7 status. So quick question. If we put in hibernate in the TomEE profile, that should deploy fine right? I'm not saying for you guys to put it in, but for the sake of the EE sample tests that might help with the JPA 2.1 tests. John On Wed, Nov 5, 2014 at 12:06 PM, Roberto Cortez radcor...@yahoo.com.invalid wrote: Great! Thanks, I'll add it in the next run :) From: Romain Manni-Bucau rmannibu...@gmail.com To: Roberto Cortez radcor...@yahoo.com Cc: users@tomee.apache.org users@tomee.apache.org; David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 5:01 PM Subject: Re: TomEE plans for Java EE 7 seems tomee embedded profile misses at least (tomee-embedded doesn't provide it by default, tomee-plus should if you want to use tomee-remote with plus classifier configured): dependency groupIdorg.apache.batchee/groupId artifactIdbatchee-jbatch/artifactId version0.2-incubating/version /dependency dependency groupIdorg.apache.johnzon/groupId artifactIdjohnzon-core/artifactId version0.1-incubating/version /dependency Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:55 GMT+00:00 Romain Manni-Bucau rmannibu...@gmail.com: great, thks Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 16:51 GMT+00:00 Roberto Cortez radcor...@yahoo.com: Ok, Jenkins archiving was killing the machine disk space. I had to delete and create a new job. It's running now and should be accessible on the same url: https://javaee-support.ci.cloudbees.com/job/javaee7-samples-tomee-2.0/ From: Roberto Cortez radcor...@yahoo.com.INVALID To: Romain Manni-Bucau rmannibu...@gmail.com; users@tomee.apache.org users@tomee.apache.org Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:42 PM Subject: Re: TomEE plans for Java EE 7 Yeah give me a sec, the job was taking too much space From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org; Roberto Cortez radcor...@yahoo.com Cc: David Blevins david.blev...@gmail.com Sent: Wednesday, November 5, 2014 4:38 PM Subject: Re: TomEE plans for Java EE 7 Hello Roberto, is it broken again? I get 404 Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-05 11:44 GMT+00:00 Roberto Cortez radcor...@yahoo.com.invalid : Hi, We got our account back, so the
Question regarding EJB Timers
Hi I've been looking for some details on EJB Timers and retries... maybe someone can help me out on the below? - WebSphere has default an unlimited number of retries with a 300 sec (5 min) interval. - Assume we have a timer that triggers every half hour and that it at some point fails (lets assume 1 clock for the example below) - Only thing I can find the EJB JSR318 EJB 3.1 is: - If the container-managed transaction is rolled back, the container retries the timeout. and - The container must retry the timeout after the transaction rollback. and - If the transaction fails or is rolled back, the container must retry the timeout at least once. Questions - Are all details around retries implementation specific? How does OpenEJB handle it? - Assume that the timer tasks all fail before say 1:30, will I then see the following scenario?? - 1:00 - Timer due to @Schedule expression = Fails - 1:05 - 1:25 (every 5 minutes) - Timer due to retry = Fails - 1:30 - Timer due to @Schedule expression = Succeed - 2:00 - Timer due to @Schedule expression = Succeed - ... and so on... - Or might the Timer trigger twice (or twice within a short timeinterval around) 2:00 ? - Will the retry of the Timer stop as soon as the Timer not fails regardless of wether it was triggered as a result of a retry or a normal @Scheduler? -- Med vänlig hälsning / Best regards Lars-Fredrik Smedberg STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the address(es) and may contain confidential or privileged information. If you are not the intended recipient, please notify Lars-Fredrik Smedberg immediately at itsme...@gmail.com, and destroy all copies of this message and any attachments.
Re: Question regarding EJB Timers
Hi isn't it more or less the same as http://tomee-openejb.979440.n4.nabble.com/More-information-on-EJB-Timer-their-Exception-handling-etc-td4672037.html ? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 13:22 GMT+00:00 Lars-Fredrik Smedberg itsme...@gmail.com: Hi I've been looking for some details on EJB Timers and retries... maybe someone can help me out on the below? - WebSphere has default an unlimited number of retries with a 300 sec (5 min) interval. - Assume we have a timer that triggers every half hour and that it at some point fails (lets assume 1 clock for the example below) - Only thing I can find the EJB JSR318 EJB 3.1 is: - If the container-managed transaction is rolled back, the container retries the timeout. and - The container must retry the timeout after the transaction rollback. and - If the transaction fails or is rolled back, the container must retry the timeout at least once. Questions - Are all details around retries implementation specific? How does OpenEJB handle it? - Assume that the timer tasks all fail before say 1:30, will I then see the following scenario?? - 1:00 - Timer due to @Schedule expression = Fails - 1:05 - 1:25 (every 5 minutes) - Timer due to retry = Fails - 1:30 - Timer due to @Schedule expression = Succeed - 2:00 - Timer due to @Schedule expression = Succeed - ... and so on... - Or might the Timer trigger twice (or twice within a short timeinterval around) 2:00 ? - Will the retry of the Timer stop as soon as the Timer not fails regardless of wether it was triggered as a result of a retry or a normal @Scheduler? -- Med vänlig hälsning / Best regards Lars-Fredrik Smedberg STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the address(es) and may contain confidential or privileged information. If you are not the intended recipient, please notify Lars-Fredrik Smedberg immediately at itsme...@gmail.com, and destroy all copies of this message and any attachments.
Re: Question regarding EJB Timers
Hi again Yes some of it (the vendor specific part and configuration of number of retries / interval etc). Had forgotten about that :) What about the questions regarding the example? (that is if it will trigger it twice at (almost) the same time and if the failure attempts will stop at any successfull timer execution) Hope I not asked about that also before :) On Thu, Nov 6, 2014 at 3:08 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi isn't it more or less the same as http://tomee-openejb.979440.n4.nabble.com/More-information-on-EJB-Timer-their-Exception-handling-etc-td4672037.html ? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 13:22 GMT+00:00 Lars-Fredrik Smedberg itsme...@gmail.com: Hi I've been looking for some details on EJB Timers and retries... maybe someone can help me out on the below? - WebSphere has default an unlimited number of retries with a 300 sec (5 min) interval. - Assume we have a timer that triggers every half hour and that it at some point fails (lets assume 1 clock for the example below) - Only thing I can find the EJB JSR318 EJB 3.1 is: - If the container-managed transaction is rolled back, the container retries the timeout. and - The container must retry the timeout after the transaction rollback. and - If the transaction fails or is rolled back, the container must retry the timeout at least once. Questions - Are all details around retries implementation specific? How does OpenEJB handle it? - Assume that the timer tasks all fail before say 1:30, will I then see the following scenario?? - 1:00 - Timer due to @Schedule expression = Fails - 1:05 - 1:25 (every 5 minutes) - Timer due to retry = Fails - 1:30 - Timer due to @Schedule expression = Succeed - 2:00 - Timer due to @Schedule expression = Succeed - ... and so on... - Or might the Timer trigger twice (or twice within a short timeinterval around) 2:00 ? - Will the retry of the Timer stop as soon as the Timer not fails regardless of wether it was triggered as a result of a retry or a normal @Scheduler? -- Med vänlig hälsning / Best regards Lars-Fredrik Smedberg STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the address(es) and may contain confidential or privileged information. If you are not the intended recipient, please notify Lars-Fredrik Smedberg immediately at itsme...@gmail.com, and destroy all copies of this message and any attachments. -- Med vänlig hälsning / Best regards Lars-Fredrik Smedberg STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the address(es) and may contain confidential or privileged information. If you are not the intended recipient, please notify Lars-Fredrik Smedberg immediately at itsme...@gmail.com, and destroy all copies of this message and any attachments.
Question about tomEE http remote ejb port
how can i change port from 8080 to, for example, 2345?? from p.put(java.naming.provider.url, http://localhost:8080/tomee/ejb;); to, for example p.put(java.naming.provider.url, http://localhost:2345/tomee/ejb;); what file in conf/ directory must compile?!? tank... -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Question-about-tomEE-http-remote-ejb-port-tp4672785.html Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Question about tomEE http remote ejb port
Hi, This is picked up from the server.xml file in the conf/ directory: Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443/ Simply changing this port will move anything that was exposed on port 8080 to the new port that you want to use, so you may wish to add another connector if that's not quite what you're after. Hope that helps. Jon On Thu, Nov 6, 2014 at 8:26 AM, vidaniello vidanie...@gmail.com wrote: how can i change port from 8080 to, for example, 2345?? from p.put(java.naming.provider.url, http://localhost:8080/tomee/ejb;); to, for example p.put(java.naming.provider.url, http://localhost:2345/tomee/ejb;); what file in conf/ directory must compile?!? tank... -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Question-about-tomEE-http-remote-ejb-port-tp4672785.html Sent from the TomEE Users mailing list archive at Nabble.com.
java:comp/ORB
Hi, I tried to look up the ORB from within a jsp, javax.naming.Context ctx = new javax.naming.InitialContext(); Object o = ctx.lookup(java:comp/ORB); This fails with javax.naming.NameNotFoundException: No ORB registered with the OpenEJB system Do you have to configure something to get the ORB? This should be Yoko, isn't it ? (https://issues.apache.org/jira/browse/OPENEJB-266) Thanks, Juergen
Re: Question about tomEE http remote ejb port
Ok... Therefore for lookup a remote EJB using HTTP, is necessary using the same port of http web?!? Can't dissociate the two port?! For this purpose is best to use openejb remote (ejbd://localhost:4201)?? -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Question-about-tomEE-http-remote-ejb-port-tp4672785p4672788.html Sent from the TomEE Users mailing list archive at Nabble.com.
Re: Question about tomEE http remote ejb port
Hi - is it best to dissociate both? depend 100% of your app - you can do it defining another connector and another host and associating this new host with a webapp containing only EJbServlet. Alternative is to use ejbd:// directly but then you swicth completely tomcat (can be nicer since faster but drawback is it is not that standard for prod in general) Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 17:15 GMT+00:00 vidaniello vidanie...@gmail.com: Ok... Therefore for lookup a remote EJB using HTTP, is necessary using the same port of http web?!? Can't dissociate the two port?! For this purpose is best to use openejb remote (ejbd://localhost:4201)?? -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Question-about-tomEE-http-remote-ejb-port-tp4672785p4672788.html Sent from the TomEE Users mailing list archive at Nabble.com.
Re: java:comp/ORB
Hi IIRC you need to put it in openejb component. In conf/system.properties: org.omg.CORBA.ORB=org.superbiz.MyORBImpl Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 17:00 GMT+00:00 Jürgen Weber juer...@jwi.de: Hi, I tried to look up the ORB from within a jsp, javax.naming.Context ctx = new javax.naming.InitialContext(); Object o = ctx.lookup(java:comp/ORB); This fails with javax.naming.NameNotFoundException: No ORB registered with the OpenEJB system Do you have to configure something to get the ORB? This should be Yoko, isn't it ? (https://issues.apache.org/jira/browse/OPENEJB-266) Thanks, Juergen
Re: Question regarding EJB Timers
If I got it right the anser will be: retry is by execution and it stops when it passes. Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 14:39 GMT+00:00 Lars-Fredrik Smedberg itsme...@gmail.com: Hi again Yes some of it (the vendor specific part and configuration of number of retries / interval etc). Had forgotten about that :) What about the questions regarding the example? (that is if it will trigger it twice at (almost) the same time and if the failure attempts will stop at any successfull timer execution) Hope I not asked about that also before :) On Thu, Nov 6, 2014 at 3:08 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi isn't it more or less the same as http://tomee-openejb.979440.n4.nabble.com/More-information-on-EJB-Timer-their-Exception-handling-etc-td4672037.html ? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 13:22 GMT+00:00 Lars-Fredrik Smedberg itsme...@gmail.com: Hi I've been looking for some details on EJB Timers and retries... maybe someone can help me out on the below? - WebSphere has default an unlimited number of retries with a 300 sec (5 min) interval. - Assume we have a timer that triggers every half hour and that it at some point fails (lets assume 1 clock for the example below) - Only thing I can find the EJB JSR318 EJB 3.1 is: - If the container-managed transaction is rolled back, the container retries the timeout. and - The container must retry the timeout after the transaction rollback. and - If the transaction fails or is rolled back, the container must retry the timeout at least once. Questions - Are all details around retries implementation specific? How does OpenEJB handle it? - Assume that the timer tasks all fail before say 1:30, will I then see the following scenario?? - 1:00 - Timer due to @Schedule expression = Fails - 1:05 - 1:25 (every 5 minutes) - Timer due to retry = Fails - 1:30 - Timer due to @Schedule expression = Succeed - 2:00 - Timer due to @Schedule expression = Succeed - ... and so on... - Or might the Timer trigger twice (or twice within a short timeinterval around) 2:00 ? - Will the retry of the Timer stop as soon as the Timer not fails regardless of wether it was triggered as a result of a retry or a normal @Scheduler? -- Med vänlig hälsning / Best regards Lars-Fredrik Smedberg STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the address(es) and may contain confidential or privileged information. If you are not the intended recipient, please notify Lars-Fredrik Smedberg immediately at itsme...@gmail.com, and destroy all copies of this message and any attachments. -- Med vänlig hälsning / Best regards Lars-Fredrik Smedberg STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the address(es) and may contain confidential or privileged information. If you are not the intended recipient, please notify Lars-Fredrik Smedberg immediately at itsme...@gmail.com, and destroy all copies of this message and any attachments.
Re: Question regarding EJB Timers
Thanks Romain and sorry for missing out that i already asked half of my questions in the last mail :-) On Nov 6, 2014 7:22 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: If I got it right the anser will be: retry is by execution and it stops when it passes. Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 14:39 GMT+00:00 Lars-Fredrik Smedberg itsme...@gmail.com: Hi again Yes some of it (the vendor specific part and configuration of number of retries / interval etc). Had forgotten about that :) What about the questions regarding the example? (that is if it will trigger it twice at (almost) the same time and if the failure attempts will stop at any successfull timer execution) Hope I not asked about that also before :) On Thu, Nov 6, 2014 at 3:08 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi isn't it more or less the same as http://tomee-openejb.979440.n4.nabble.com/More-information-on-EJB-Timer-their-Exception-handling-etc-td4672037.html ? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 13:22 GMT+00:00 Lars-Fredrik Smedberg itsme...@gmail.com: Hi I've been looking for some details on EJB Timers and retries... maybe someone can help me out on the below? - WebSphere has default an unlimited number of retries with a 300 sec (5 min) interval. - Assume we have a timer that triggers every half hour and that it at some point fails (lets assume 1 clock for the example below) - Only thing I can find the EJB JSR318 EJB 3.1 is: - If the container-managed transaction is rolled back, the container retries the timeout. and - The container must retry the timeout after the transaction rollback. and - If the transaction fails or is rolled back, the container must retry the timeout at least once. Questions - Are all details around retries implementation specific? How does OpenEJB handle it? - Assume that the timer tasks all fail before say 1:30, will I then see the following scenario?? - 1:00 - Timer due to @Schedule expression = Fails - 1:05 - 1:25 (every 5 minutes) - Timer due to retry = Fails - 1:30 - Timer due to @Schedule expression = Succeed - 2:00 - Timer due to @Schedule expression = Succeed - ... and so on... - Or might the Timer trigger twice (or twice within a short timeinterval around) 2:00 ? - Will the retry of the Timer stop as soon as the Timer not fails regardless of wether it was triggered as a result of a retry or a normal @Scheduler? -- Med vänlig hälsning / Best regards Lars-Fredrik Smedberg STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the address(es) and may contain confidential or privileged information. If you are not the intended recipient, please notify Lars-Fredrik Smedberg immediately at itsme...@gmail.com, and destroy all copies of this message and any attachments. -- Med vänlig hälsning / Best regards Lars-Fredrik Smedberg STATEMENT OF CONFIDENTIALITY: The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the address(es) and may contain confidential or privileged information. If you are not the intended recipient, please notify Lars-Fredrik Smedberg immediately at itsme...@gmail.com, and destroy all copies of this message and any attachments.
Re: 2.0.0-SNAPSHOT @provider and @inject
Hi, https://github.com/hwaastad/TomEEAngular.git Not made any tests yet since this is a project testing out different technologies. however mvn tomee:run and localhost:8080 and click Customers the injected EJB in filter resolves to null. br hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/2-0-0-SNAPSHOT-provider-and-inject-tp4672772p4672795.html Sent from the TomEE Users mailing list archive at Nabble.com.
Re: 2.0.0-SNAPSHOT @provider and @inject
Hi fixed on trunk, @Context ResourceInfo was not supported - fixed - Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 18:54 GMT+00:00 hwaastad he...@waastad.org: Hi, https://github.com/hwaastad/TomEEAngular.git Not made any tests yet since this is a project testing out different technologies. however mvn tomee:run and localhost:8080 and click Customers the injected EJB in filter resolves to null. br hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/2-0-0-SNAPSHOT-provider-and-inject-tp4672772p4672795.html Sent from the TomEE Users mailing list archive at Nabble.com.
Re: 2.0.0-SNAPSHOT @provider and @inject
Marvellous :-) I'll give it a try tomorrow. br hw -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/2-0-0-SNAPSHOT-provider-and-inject-tp4672772p4672797.html Sent from the TomEE Users mailing list archive at Nabble.com.
apache tomee 1.7.0 -- rest application duplicate deploy
https://github.com/jieryn/javaee-example mvn install ; mvn -pl :war tomee:run Notice two deployments: INFO: REST Application: http://localhost:8080/ - org.apache.openejb.server.rest.InternalApplication INFO: REST Application: http://localhost:8080/api - com.acme.javaee.api.Application Tomee is not respecting my API application and is doubley deploying my resources. This is more than just annoying because it is taking over the root context default handler, instead of Tomcat.
Re: apache tomee 1.7.0 -- rest application duplicate deploy
Sorry, it's TomEE 1.7.1. On Thu, Nov 6, 2014 at 5:16 PM, jieryn jie...@gmail.com wrote: https://github.com/jieryn/javaee-example mvn install ; mvn -pl :war tomee:run Notice two deployments: INFO: REST Application: http://localhost:8080/ - org.apache.openejb.server.rest.InternalApplication INFO: REST Application: http://localhost:8080/api - com.acme.javaee.api.Application Tomee is not respecting my API application and is doubley deploying my resources. This is more than just annoying because it is taking over the root context default handler, instead of Tomcat.
Re: apache tomee 1.7.0 -- rest application duplicate deploy
that's cause of wink: $ cat conf/exclusions.list default-list wink- Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-06 22:17 GMT+00:00 jieryn jie...@gmail.com: Sorry, it's TomEE 1.7.1. On Thu, Nov 6, 2014 at 5:16 PM, jieryn jie...@gmail.com wrote: https://github.com/jieryn/javaee-example mvn install ; mvn -pl :war tomee:run Notice two deployments: INFO: REST Application: http://localhost:8080/ - org.apache.openejb.server.rest.InternalApplication INFO: REST Application: http://localhost:8080/api - com.acme.javaee.api.Application Tomee is not respecting my API application and is doubley deploying my resources. This is more than just annoying because it is taking over the root context default handler, instead of Tomcat.
