Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Hello, I still don't see from which page of tomee.apache.org this new page is linked, if it is: http://openejb.staging.apache.org/tomee-version-policies.html I know for sure that it isn't directly linked from TomEE documentation page: http://openejb.staging.apache.org/documentation.html Don't we have a missing link ? (joke on TomEE evolution ;) Alex On Mon, Jan 7, 2013 at 1:28 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Done. Thanks Alex. Jean-Louis 2013/1/6 Alex The Rocker alex.m3...@gmail.com Hello, Can this http://openejb.staging.apache.org/tomee-version-policies.htmlpage be linked from official from TomEE documentation links page, if you all agree about its content? Alex On Thu, Jan 3, 2013 at 7:03 PM, Alex The Rocker alex.m3...@gmail.com wrote: @Jean-Louis; How about this page: http://openejb.staging.apache.org/tomee-version-policies.html Is it okay for you guys? can it be linked to official TomEE documentation ? Alex. On Wed, Jan 2, 2013 at 6:30 PM, David Blevins david.blev...@gmail.com wrote: On Dec 30, 2012, at 1:42 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Id like to break rest default config so 1.6 is better imo Why don't we have a discussion about breaking the default config. Can you post a proposal on it? -David Le 30 déc. 2012 21:34, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis -- Jean-Louis -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Hi, i see it here http://tomee.apache.org/tomee-version-policies.html btw i wonder if it should be under the documentation page because currently documentation is more practise doc we either need to split doc page in subitems IMO or put it elsewhere (maybe support tab?) wdyt? *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/1/13 Alex The Rocker alex.m3...@gmail.com Hello, I still don't see from which page of tomee.apache.org this new page is linked, if it is: http://openejb.staging.apache.org/tomee-version-policies.html I know for sure that it isn't directly linked from TomEE documentation page: http://openejb.staging.apache.org/documentation.html Don't we have a missing link ? (joke on TomEE evolution ;) Alex On Mon, Jan 7, 2013 at 1:28 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Done. Thanks Alex. Jean-Louis 2013/1/6 Alex The Rocker alex.m3...@gmail.com Hello, Can this http://openejb.staging.apache.org/tomee-version-policies.htmlpage be linked from official from TomEE documentation links page, if you all agree about its content? Alex On Thu, Jan 3, 2013 at 7:03 PM, Alex The Rocker alex.m3...@gmail.com wrote: @Jean-Louis; How about this page: http://openejb.staging.apache.org/tomee-version-policies.html Is it okay for you guys? can it be linked to official TomEE documentation ? Alex. On Wed, Jan 2, 2013 at 6:30 PM, David Blevins david.blev...@gmail.com wrote: On Dec 30, 2012, at 1:42 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Id like to break rest default config so 1.6 is better imo Why don't we have a discussion about breaking the default config. Can you post a proposal on it? -David Le 30 déc. 2012 21:34, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Done. Thanks Alex. Jean-Louis 2013/1/6 Alex The Rocker alex.m3...@gmail.com Hello, Can this http://openejb.staging.apache.org/tomee-version-policies.htmlpage be linked from official from TomEE documentation links page, if you all agree about its content? Alex On Thu, Jan 3, 2013 at 7:03 PM, Alex The Rocker alex.m3...@gmail.com wrote: @Jean-Louis; How about this page: http://openejb.staging.apache.org/tomee-version-policies.html Is it okay for you guys? can it be linked to official TomEE documentation ? Alex. On Wed, Jan 2, 2013 at 6:30 PM, David Blevins david.blev...@gmail.com wrote: On Dec 30, 2012, at 1:42 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Id like to break rest default config so 1.6 is better imo Why don't we have a discussion about breaking the default config. Can you post a proposal on it? -David Le 30 déc. 2012 21:34, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis -- Jean-Louis -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Hello, Can this http://openejb.staging.apache.org/tomee-version-policies.html page be linked from official from TomEE documentation links page, if you all agree about its content? Alex On Thu, Jan 3, 2013 at 7:03 PM, Alex The Rocker alex.m3...@gmail.comwrote: @Jean-Louis; How about this page: http://openejb.staging.apache.org/tomee-version-policies.html Is it okay for you guys? can it be linked to official TomEE documentation ? Alex. On Wed, Jan 2, 2013 at 6:30 PM, David Blevins david.blev...@gmail.comwrote: On Dec 30, 2012, at 1:42 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Id like to break rest default config so 1.6 is better imo Why don't we have a discussion about breaking the default config. Can you post a proposal on it? -David Le 30 déc. 2012 21:34, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
@Jean-Louis; How about this page: http://openejb.staging.apache.org/tomee-version-policies.html Is it okay for you guys? can it be linked to official TomEE documentation ? Alex. On Wed, Jan 2, 2013 at 6:30 PM, David Blevins david.blev...@gmail.comwrote: On Dec 30, 2012, at 1:42 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Id like to break rest default config so 1.6 is better imo Why don't we have a discussion about breaking the default config. Can you post a proposal on it? -David Le 30 déc. 2012 21:34, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis -- Jean-Louis
Fwd: svn commit: r1427716 - in /openejb/trunk/openejb/tck: bval-embedded/pom.xml bval-tomee/pom.xml cdi-embedded/pom.xml cdi-tomee-embedded/pom.xml cdi-tomee/pom.xml pom.xml tck-common/pom.xml
We cant use surefire 2.12.4 (dont run tests), 2.13 is fine
-- Message transféré --
De : andygumbre...@apache.org
Date : 2 janv. 2013 10:09
Objet : svn commit: r1427716 - in /openejb/trunk/openejb/tck:
bval-embedded/pom.xml bval-tomee/pom.xml cdi-embedded/pom.xml
cdi-tomee-embedded/pom.xml cdi-tomee/pom.xml pom.xml tck-common/pom.xml
À : comm...@openejb.apache.org
Author: andygumbrecht
Date: Wed Jan 2 09:08:33 2013
New Revision: 1427716
URL: http://svn.apache.org/viewvc?rev=1427716view=rev
Log:
Use newer maven plugin versions and try to avoid creating files that win
platforms cannot cope with.
Modified:
openejb/trunk/openejb/tck/bval-embedded/pom.xml
openejb/trunk/openejb/tck/bval-tomee/pom.xml
openejb/trunk/openejb/tck/cdi-embedded/pom.xml
openejb/trunk/openejb/tck/cdi-tomee-embedded/pom.xml
openejb/trunk/openejb/tck/cdi-tomee/pom.xml
openejb/trunk/openejb/tck/pom.xml
openejb/trunk/openejb/tck/tck-common/pom.xml
Modified: openejb/trunk/openejb/tck/bval-embedded/pom.xml
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/tck/bval-embedded/pom.xml?rev=1427716r1=1427715r2=1427716view=diff
==
--- openejb/trunk/openejb/tck/bval-embedded/pom.xml (original)
+++ openejb/trunk/openejb/tck/bval-embedded/pom.xml Wed Jan 2 09:08:33 2013
@@ -86,7 +86,7 @@
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
-version2.12/version
+version2.12.4/version
configuration
suiteXmlFiles
suiteXmlFilesrc/test/resources/jsr303-tck-suite.xml/suiteXmlFile
@@ -102,7 +102,7 @@
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-report-plugin/artifactId
-version2.12/version
+version2.12.4/version
executions
execution
idgenerate-test-report/id
Modified: openejb/trunk/openejb/tck/bval-tomee/pom.xml
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/tck/bval-tomee/pom.xml?rev=1427716r1=1427715r2=1427716view=diff
==
--- openejb/trunk/openejb/tck/bval-tomee/pom.xml (original)
+++ openejb/trunk/openejb/tck/bval-tomee/pom.xml Wed Jan 2 09:08:33 2013
@@ -124,7 +124,7 @@
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
-version2.3/version
+version2.6/version
executions
execution
idunpack/id
@@ -174,7 +174,7 @@
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
-version2.12/version
+version2.12.4/version
configuration
skiptrue/skip
/configuration
@@ -183,7 +183,7 @@
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-failsafe-plugin/artifactId
-version2.9/version
+version2.12.4/version
configuration
suiteXmlFiles
suiteXmlFilesrc/test/resources/jsr303-tck-suite.xml/suiteXmlFile
@@ -205,7 +205,7 @@
connect.tries90/connect.tries
server.http.port${tomee.http.port}/server.http.port
server.shutdown.port${tomee.shutdown.port}/server.shutdown.port
-java.opts-Xmx512m -Xms256m -XX:PermSize=64m
-XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=64m/java.opts
+java.opts-Xmx512m -Xss2048k -XX:PermSize=64m
-XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=64m/java.opts
openejb.home${openejb.home}/openejb.home
/systemPropertyVariables
/configuration
@@ -229,7 +229,7 @@
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
-version1.5/version
+version1.7/version
executions
execution
idremove-apps/id
Modified: openejb/trunk/openejb/tck/cdi-embedded/pom.xml
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/tck/cdi-embedded/pom.xml?rev=1427716r1=1427715r2=1427716view=diff
==
--- openejb/trunk/openejb/tck/cdi-embedded/pom.xml (original)
+++ openejb/trunk/openejb/tck/cdi-embedded/pom.xml Wed Jan 2 09:08:33 2013
@@ -15,8 +15,7 @@
See the License for the specific language governing permissions and
limitations under the License.
--
-project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
- xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
+project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;
parent
artifactIdtck/artifactId
Re: Fwd: svn commit: r1427716 - in /openejb/trunk/openejb/tck: bval-embedded/pom.xml bval-tomee/pom.xml cdi-embedded/pom.xml cdi-tomee-embedded/pom.xml cdi-tomee/pom.xml pom.xml tck-common/pom.xml
Do we know why, is it a bug in surefire or our configuration? -- View this message in context: http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1427716-in-openejb-trunk-openejb-tck-bval-embedded-pom-xml-bval-tomee-pom-xml-cdi-eml-tp4660010p4660011.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Fwd: svn commit: r1427716 - in /openejb/trunk/openejb/tck: bval-embedded/pom.xml bval-tomee/pom.xml cdi-embedded/pom.xml cdi-tomee-embedded/pom.xml cdi-tomee/pom.xml pom.xml tck-common/pom.xml
Surefire, fixed in 2.13 Le 2 janv. 2013 11:43, AndyG andy.gumbre...@orprovision.com a écrit : Do we know why, is it a bug in surefire or our configuration? -- View this message in context: http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1427716-in-openejb-trunk-openejb-tck-bval-embedded-pom-xml-bval-tomee-pom-xml-cdi-eml-tp4660010p4660011.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
On Dec 30, 2012, at 1:42 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Id like to break rest default config so 1.6 is better imo Why don't we have a discussion about breaking the default config. Can you post a proposal on it? -David Le 30 déc. 2012 21:34, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis -- Jean-Louis
It's official.. we're TomEE
Heard back from the ASF Board. Our TLP name is now officially Apache TomEE :) Will follow up with Infra to see if it's at all possible to get us...@tomee.apache.org etc. -David
CMS diff: TomEE and Arquillian
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/arquillian-available-adapters.mdtext rudy vissers Index: trunk/content/arquillian-available-adapters.mdtext === --- trunk/content/arquillian-available-adapters.mdtext (revision 1427260) +++ trunk/content/arquillian-available-adapters.mdtext (working copy) @@ -2,7 +2,7 @@ Check out the [Getting started](arquillian-getting-started.html) page if you are not familiar with Arquillian. -All the Aqruillian Adapters for TomEE support the following configuration options in the arquillian.xml: +All the Arquillian Adapters for TomEE support the following configuration options in the arquillian.xml: container qualifier=tomee default=true configuration
Re: CMS diff: TomEE and Arquillian
Not committed as I don't see any difference. JLouis 2013/1/1 rudy vissers anonym...@apache.org Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/arquillian-available-adapters.mdtext rudy vissers Index: trunk/content/arquillian-available-adapters.mdtext === --- trunk/content/arquillian-available-adapters.mdtext (revision 1427260) +++ trunk/content/arquillian-available-adapters.mdtext (working copy) @@ -2,7 +2,7 @@ Check out the [Getting started](arquillian-getting-started.html) page if you are not familiar with Arquillian. -All the Aqruillian Adapters for TomEE support the following configuration options in the arquillian.xml: +All the Arquillian Adapters for TomEE support the following configuration options in the arquillian.xml: container qualifier=tomee default=true configuration -- Jean-Louis
Re: CMS diff: TomEE and Arquillian
A typo in arquillian name This year you need glasses ;) Le 1 janv. 2013 14:16, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Not committed as I don't see any difference. JLouis 2013/1/1 rudy vissers anonym...@apache.org Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/arquillian-available-adapters.mdtext rudy vissers Index: trunk/content/arquillian-available-adapters.mdtext === --- trunk/content/arquillian-available-adapters.mdtext (revision 1427260) +++ trunk/content/arquillian-available-adapters.mdtext (working copy) @@ -2,7 +2,7 @@ Check out the [Getting started](arquillian-getting-started.html) page if you are not familiar with Arquillian. -All the Aqruillian Adapters for TomEE support the following configuration options in the arquillian.xml: +All the Arquillian Adapters for TomEE support the following configuration options in the arquillian.xml: container qualifier=tomee default=true configuration -- Jean-Louis
Re: CMS diff: TomEE and Arquillian
Oups, probably :) 2013/1/1 Romain Manni-Bucau rmannibu...@gmail.com A typo in arquillian name This year you need glasses ;) Le 1 janv. 2013 14:16, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Not committed as I don't see any difference. JLouis 2013/1/1 rudy vissers anonym...@apache.org Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/arquillian-available-adapters.mdtext rudy vissers Index: trunk/content/arquillian-available-adapters.mdtext === --- trunk/content/arquillian-available-adapters.mdtext (revision 1427260) +++ trunk/content/arquillian-available-adapters.mdtext (working copy) @@ -2,7 +2,7 @@ Check out the [Getting started](arquillian-getting-started.html) page if you are not familiar with Arquillian. -All the Aqruillian Adapters for TomEE support the following configuration options in the arquillian.xml: +All the Arquillian Adapters for TomEE support the following configuration options in the arquillian.xml: container qualifier=tomee default=true configuration -- Jean-Louis -- Jean-Louis
Re: CMS diff: TomEE and Arquillian
Done! 2013/1/1 Jean-Louis MONTEIRO jeano...@gmail.com Oups, probably :) 2013/1/1 Romain Manni-Bucau rmannibu...@gmail.com A typo in arquillian name This year you need glasses ;) Le 1 janv. 2013 14:16, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Not committed as I don't see any difference. JLouis 2013/1/1 rudy vissers anonym...@apache.org Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/arquillian-available-adapters.mdtext rudy vissers Index: trunk/content/arquillian-available-adapters.mdtext === --- trunk/content/arquillian-available-adapters.mdtext (revision 1427260) +++ trunk/content/arquillian-available-adapters.mdtext (working copy) @@ -2,7 +2,7 @@ Check out the [Getting started](arquillian-getting-started.html) page if you are not familiar with Arquillian. -All the Aqruillian Adapters for TomEE support the following configuration options in the arquillian.xml: +All the Arquillian Adapters for TomEE support the following configuration options in the arquillian.xml: container qualifier=tomee default=true configuration -- Jean-Louis -- Jean-Louis -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Alex, You are right, dunno why it does not work. I don't have a lot of time today to dig into. The first thing you can to do is to create a bookmark titled 'ASF CMS edit' with the following content: javascript:void(location.href='https://cms .apache.org/redirect?uri='+escape(location.href)) Then, you can navigate again to http://tomee.apache.org/tomee-version-policies.html Or any page you wanna update. Finally, just click on the 'ASF CMS Edit' bookmark created in the first step and that should work. The top right blue pen is supposed to do the same. There was a synchronization issue between the online cms editor and our svn repo. It's working now for me. Crossing fingers now. Happy new year JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com When I click 'No', I'm redirected to this location: https://cms.apache.org/openejb/wc/browse/anonymous-sFLdJE/trunk/ and I don't see where I could edit the page about TomEE versions :( Am I missing something? On Sun, Dec 30, 2012 at 11:17 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: No stupid question, only stupid answers. Apache ID = apache committer ID You can just say No and enter in an anonymous mode. As soon as you validate it, we receive a patch to commit for you. @Romain, no need to follow Tomcat, was just to clarify things in my opinion and check their versioning to inspire ourself. But we are all free to do whatever we want. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Okay, now time for a stupid question : I'm asked to enter an Apache ID, how can I register one? (the ID which I use for JIRA doesn't work here) On Sun, Dec 30, 2012 at 11:01 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: That sounds pretty similar to Tomcat. If we can adapt a bit to make things even clearer I'm all for it. Whatever the next version will be, yes we can create a page and push our versioning thoughts and Java EE mapping. Would you like to start pushing your understanding as you proposed previously and how you would get them proposed? Just created a new page and committed it. http://openejb.staging.apache.org/tomee-version-policies.html You can edit it and push a patch directly on the website using the top right blue pen. You don't need to be a committer. Thanks in advance JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: I wasn't very clear, sorry for that, but I think you got the idea :) If I understand well your proposal of TomEE versioning, it would be x.y.z, with x=1 for Java EE 6 ; and y moving when there are new features and z moving for fixes. Why not, but this is a little bit different from Tomcat's x.y.z : - it seems that Tomcat x version is correlated to a Java Servlet JSP specification, so TomEE's x meaning a given Java EE version, with x=1 = Java EE 6 is consistent. - For the middle version number y, I have been so much used to Tomcat 6.0.x that I wasn't considering features (other than Java EE version) changes - For the last version number z, your proposal for TomEE (fixes) seems to be consistent with Tomcat's So it seems that I need to ask our certification team to adapt a little bit our TomEE support policy, with a statement looking like this: our product is supported with Apache TomEE+ 1.5.x, x=1 or with TomEE+ 1.6.z, y=6. Now I have a request for you Jean-Louis: could your proposal for version be written somewhere in TomEE's internet side, including the major version mapping to Java EE release, like this: TomEE 1.x.y = Java EE 6 TomEE 2.x.y = Java EE 7 and the meaning of x y (features fixes) ? If you need a JIRA for this, then I can open it. Thanks, Alex On Sun, Dec 30, 2012 at 10:34 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Done. Would you please review it and let know if it's acceptable by the dev community before it's made public ? On Mon, Dec 31, 2012 at 3:13 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Alex, You are right, dunno why it does not work. I don't have a lot of time today to dig into. The first thing you can to do is to create a bookmark titled 'ASF CMS edit' with the following content: javascript:void(location.href='https://cms .apache.org/redirect?uri='+escape(location.href)) Then, you can navigate again to http://tomee.apache.org/tomee-version-policies.html Or any page you wanna update. Finally, just click on the 'ASF CMS Edit' bookmark created in the first step and that should work. The top right blue pen is supposed to do the same. There was a synchronization issue between the online cms editor and our svn repo. It's working now for me. Crossing fingers now. Happy new year JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com When I click 'No', I'm redirected to this location: https://cms.apache.org/openejb/wc/browse/anonymous-sFLdJE/trunk/ and I don't see where I could edit the page about TomEE versions :( Am I missing something? On Sun, Dec 30, 2012 at 11:17 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: No stupid question, only stupid answers. Apache ID = apache committer ID You can just say No and enter in an anonymous mode. As soon as you validate it, we receive a patch to commit for you. @Romain, no need to follow Tomcat, was just to clarify things in my opinion and check their versioning to inspire ourself. But we are all free to do whatever we want. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Okay, now time for a stupid question : I'm asked to enter an Apache ID, how can I register one? (the ID which I use for JIRA doesn't work here) On Sun, Dec 30, 2012 at 11:01 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: That sounds pretty similar to Tomcat. If we can adapt a bit to make things even clearer I'm all for it. Whatever the next version will be, yes we can create a page and push our versioning thoughts and Java EE mapping. Would you like to start pushing your understanding as you proposed previously and how you would get them proposed? Just created a new page and committed it. http://openejb.staging.apache.org/tomee-version-policies.html You can edit it and push a patch directly on the website using the top right blue pen. You don't need to be a committer. Thanks in advance JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: I wasn't very clear, sorry for that, but I think you got the idea :) If I understand well your proposal of TomEE versioning, it would be x.y.z, with x=1 for Java EE 6 ; and y moving when there are new features and z moving for fixes. Why not, but this is a little bit different from Tomcat's x.y.z : - it seems that Tomcat x version is correlated to a Java Servlet JSP specification, so TomEE's x meaning a given Java EE version, with x=1 = Java EE 6 is consistent. - For the middle version number y, I have been so much used to Tomcat 6.0.x that I wasn't considering features (other than Java EE version) changes - For the last version number z, your proposal for TomEE (fixes) seems to be consistent with Tomcat's So it seems that I need to ask our certification team to adapt a little bit our TomEE support policy, with a statement looking like this: our product is supported with Apache TomEE+ 1.5.x, x=1 or with TomEE+ 1.6.z, y=6. Now I have a request for you Jean-Louis: could your proposal for version be written somewhere in TomEE's internet side, including the major version mapping to Java EE release, like this: TomEE 1.x.y = Java EE 6 TomEE 2.x.y = Java EE 7 and the meaning of x y (features fixes) ? If you need a JIRA for this, then I can open it. Thanks, Alex On Sun, Dec 30, 2012 at 10:34 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Hi, I need at least 3 fixes (todo) pretty quickly Hope to get it mid january so end of january would be fine Would be a 1.6 IMO Will try to explain more next year ;) Le 29 déc. 2012 23:44, Alex The Rocker alex.m3...@gmail.com a écrit : Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Id like to break rest default config so 1.6 is better imo Le 30 déc. 2012 21:34, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Jean-Louis: I wasn't very clear, sorry for that, but I think you got the idea :) If I understand well your proposal of TomEE versioning, it would be x.y.z, with x=1 for Java EE 6 ; and y moving when there are new features and z moving for fixes. Why not, but this is a little bit different from Tomcat's x.y.z : - it seems that Tomcat x version is correlated to a Java Servlet JSP specification, so TomEE's x meaning a given Java EE version, with x=1 = Java EE 6 is consistent. - For the middle version number y, I have been so much used to Tomcat 6.0.x that I wasn't considering features (other than Java EE version) changes - For the last version number z, your proposal for TomEE (fixes) seems to be consistent with Tomcat's So it seems that I need to ask our certification team to adapt a little bit our TomEE support policy, with a statement looking like this: our product is supported with Apache TomEE+ 1.5.x, x=1 or with TomEE+ 1.6.z, y=6. Now I have a request for you Jean-Louis: could your proposal for version be written somewhere in TomEE's internet side, including the major version mapping to Java EE release, like this: TomEE 1.x.y = Java EE 6 TomEE 2.x.y = Java EE 7 and the meaning of x y (features fixes) ? If you need a JIRA for this, then I can open it. Thanks, Alex On Sun, Dec 30, 2012 at 10:34 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
That sounds pretty similar to Tomcat. If we can adapt a bit to make things even clearer I'm all for it. Whatever the next version will be, yes we can create a page and push our versioning thoughts and Java EE mapping. Would you like to start pushing your understanding as you proposed previously and how you would get them proposed? Just created a new page and committed it. http://openejb.staging.apache.org/tomee-version-policies.html You can edit it and push a patch directly on the website using the top right blue pen. You don't need to be a committer. Thanks in advance JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: I wasn't very clear, sorry for that, but I think you got the idea :) If I understand well your proposal of TomEE versioning, it would be x.y.z, with x=1 for Java EE 6 ; and y moving when there are new features and z moving for fixes. Why not, but this is a little bit different from Tomcat's x.y.z : - it seems that Tomcat x version is correlated to a Java Servlet JSP specification, so TomEE's x meaning a given Java EE version, with x=1 = Java EE 6 is consistent. - For the middle version number y, I have been so much used to Tomcat 6.0.x that I wasn't considering features (other than Java EE version) changes - For the last version number z, your proposal for TomEE (fixes) seems to be consistent with Tomcat's So it seems that I need to ask our certification team to adapt a little bit our TomEE support policy, with a statement looking like this: our product is supported with Apache TomEE+ 1.5.x, x=1 or with TomEE+ 1.6.z, y=6. Now I have a request for you Jean-Louis: could your proposal for version be written somewhere in TomEE's internet side, including the major version mapping to Java EE release, like this: TomEE 1.x.y = Java EE 6 TomEE 2.x.y = Java EE 7 and the meaning of x y (features fixes) ? If you need a JIRA for this, then I can open it. Thanks, Alex On Sun, Dec 30, 2012 at 10:34 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Note: why should we follow tomcat? Tomcat is pretty simple and doesnt depend of anything else compared to us so it is natural if our versioning is a bit less straight fwd even if we try to keep it as simple as possible Moreover we are tied to openejb too which doesnt depend on tomcat Le 30 déc. 2012 22:02, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : That sounds pretty similar to Tomcat. If we can adapt a bit to make things even clearer I'm all for it. Whatever the next version will be, yes we can create a page and push our versioning thoughts and Java EE mapping. Would you like to start pushing your understanding as you proposed previously and how you would get them proposed? Just created a new page and committed it. http://openejb.staging.apache.org/tomee-version-policies.html You can edit it and push a patch directly on the website using the top right blue pen. You don't need to be a committer. Thanks in advance JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: I wasn't very clear, sorry for that, but I think you got the idea :) If I understand well your proposal of TomEE versioning, it would be x.y.z, with x=1 for Java EE 6 ; and y moving when there are new features and z moving for fixes. Why not, but this is a little bit different from Tomcat's x.y.z : - it seems that Tomcat x version is correlated to a Java Servlet JSP specification, so TomEE's x meaning a given Java EE version, with x=1 = Java EE 6 is consistent. - For the middle version number y, I have been so much used to Tomcat 6.0.x that I wasn't considering features (other than Java EE version) changes - For the last version number z, your proposal for TomEE (fixes) seems to be consistent with Tomcat's So it seems that I need to ask our certification team to adapt a little bit our TomEE support policy, with a statement looking like this: our product is supported with Apache TomEE+ 1.5.x, x=1 or with TomEE+ 1.6.z, y=6. Now I have a request for you Jean-Louis: could your proposal for version be written somewhere in TomEE's internet side, including the major version mapping to Java EE release, like this: TomEE 1.x.y = Java EE 6 TomEE 2.x.y = Java EE 7 and the meaning of x y (features fixes) ? If you need a JIRA for this, then I can open it. Thanks, Alex On Sun, Dec 30, 2012 at 10:34 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Okay, now time for a stupid question : I'm asked to enter an Apache ID, how can I register one? (the ID which I use for JIRA doesn't work here) On Sun, Dec 30, 2012 at 11:01 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: That sounds pretty similar to Tomcat. If we can adapt a bit to make things even clearer I'm all for it. Whatever the next version will be, yes we can create a page and push our versioning thoughts and Java EE mapping. Would you like to start pushing your understanding as you proposed previously and how you would get them proposed? Just created a new page and committed it. http://openejb.staging.apache.org/tomee-version-policies.html You can edit it and push a patch directly on the website using the top right blue pen. You don't need to be a committer. Thanks in advance JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: I wasn't very clear, sorry for that, but I think you got the idea :) If I understand well your proposal of TomEE versioning, it would be x.y.z, with x=1 for Java EE 6 ; and y moving when there are new features and z moving for fixes. Why not, but this is a little bit different from Tomcat's x.y.z : - it seems that Tomcat x version is correlated to a Java Servlet JSP specification, so TomEE's x meaning a given Java EE version, with x=1 = Java EE 6 is consistent. - For the middle version number y, I have been so much used to Tomcat 6.0.x that I wasn't considering features (other than Java EE version) changes - For the last version number z, your proposal for TomEE (fixes) seems to be consistent with Tomcat's So it seems that I need to ask our certification team to adapt a little bit our TomEE support policy, with a statement looking like this: our product is supported with Apache TomEE+ 1.5.x, x=1 or with TomEE+ 1.6.z, y=6. Now I have a request for you Jean-Louis: could your proposal for version be written somewhere in TomEE's internet side, including the major version mapping to Java EE release, like this: TomEE 1.x.y = Java EE 6 TomEE 2.x.y = Java EE 7 and the meaning of x y (features fixes) ? If you need a JIRA for this, then I can open it. Thanks, Alex On Sun, Dec 30, 2012 at 10:34 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
No stupid question, only stupid answers. Apache ID = apache committer ID You can just say No and enter in an anonymous mode. As soon as you validate it, we receive a patch to commit for you. @Romain, no need to follow Tomcat, was just to clarify things in my opinion and check their versioning to inspire ourself. But we are all free to do whatever we want. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Okay, now time for a stupid question : I'm asked to enter an Apache ID, how can I register one? (the ID which I use for JIRA doesn't work here) On Sun, Dec 30, 2012 at 11:01 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: That sounds pretty similar to Tomcat. If we can adapt a bit to make things even clearer I'm all for it. Whatever the next version will be, yes we can create a page and push our versioning thoughts and Java EE mapping. Would you like to start pushing your understanding as you proposed previously and how you would get them proposed? Just created a new page and committed it. http://openejb.staging.apache.org/tomee-version-policies.html You can edit it and push a patch directly on the website using the top right blue pen. You don't need to be a committer. Thanks in advance JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: I wasn't very clear, sorry for that, but I think you got the idea :) If I understand well your proposal of TomEE versioning, it would be x.y.z, with x=1 for Java EE 6 ; and y moving when there are new features and z moving for fixes. Why not, but this is a little bit different from Tomcat's x.y.z : - it seems that Tomcat x version is correlated to a Java Servlet JSP specification, so TomEE's x meaning a given Java EE version, with x=1 = Java EE 6 is consistent. - For the middle version number y, I have been so much used to Tomcat 6.0.x that I wasn't considering features (other than Java EE version) changes - For the last version number z, your proposal for TomEE (fixes) seems to be consistent with Tomcat's So it seems that I need to ask our certification team to adapt a little bit our TomEE support policy, with a statement looking like this: our product is supported with Apache TomEE+ 1.5.x, x=1 or with TomEE+ 1.6.z, y=6. Now I have a request for you Jean-Louis: could your proposal for version be written somewhere in TomEE's internet side, including the major version mapping to Java EE release, like this: TomEE 1.x.y = Java EE 6 TomEE 2.x.y = Java EE 7 and the meaning of x y (features fixes) ? If you need a JIRA for this, then I can open it. Thanks, Alex On Sun, Dec 30, 2012 at 10:34 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
When I click 'No', I'm redirected to this location: https://cms.apache.org/openejb/wc/browse/anonymous-sFLdJE/trunk/ and I don't see where I could edit the page about TomEE versions :( Am I missing something? On Sun, Dec 30, 2012 at 11:17 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: No stupid question, only stupid answers. Apache ID = apache committer ID You can just say No and enter in an anonymous mode. As soon as you validate it, we receive a patch to commit for you. @Romain, no need to follow Tomcat, was just to clarify things in my opinion and check their versioning to inspire ourself. But we are all free to do whatever we want. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Okay, now time for a stupid question : I'm asked to enter an Apache ID, how can I register one? (the ID which I use for JIRA doesn't work here) On Sun, Dec 30, 2012 at 11:01 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: That sounds pretty similar to Tomcat. If we can adapt a bit to make things even clearer I'm all for it. Whatever the next version will be, yes we can create a page and push our versioning thoughts and Java EE mapping. Would you like to start pushing your understanding as you proposed previously and how you would get them proposed? Just created a new page and committed it. http://openejb.staging.apache.org/tomee-version-policies.html You can edit it and push a patch directly on the website using the top right blue pen. You don't need to be a committer. Thanks in advance JLouis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: I wasn't very clear, sorry for that, but I think you got the idea :) If I understand well your proposal of TomEE versioning, it would be x.y.z, with x=1 for Java EE 6 ; and y moving when there are new features and z moving for fixes. Why not, but this is a little bit different from Tomcat's x.y.z : - it seems that Tomcat x version is correlated to a Java Servlet JSP specification, so TomEE's x meaning a given Java EE version, with x=1 = Java EE 6 is consistent. - For the middle version number y, I have been so much used to Tomcat 6.0.x that I wasn't considering features (other than Java EE version) changes - For the last version number z, your proposal for TomEE (fixes) seems to be consistent with Tomcat's So it seems that I need to ask our certification team to adapt a little bit our TomEE support policy, with a statement looking like this: our product is supported with Apache TomEE+ 1.5.x, x=1 or with TomEE+ 1.6.z, y=6. Now I have a request for you Jean-Louis: could your proposal for version be written somewhere in TomEE's internet side, including the major version mapping to Java EE release, like this: TomEE 1.x.y = Java EE 6 TomEE 2.x.y = Java EE 7 and the meaning of x y (features fixes) ? If you need a JIRA for this, then I can open it. Thanks, Alex On Sun, Dec 30, 2012 at 10:34 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi Alex, You are all welcome to share your needs and what you expect (and also to help if you can ;-)). IMO, TomEE 1.x.y is only Java EE 6 dedicated. The work on Java EE 7 will start Q2 2013 I guess or a bit after and it should produce the 2.x.y of TomEE. Java EE 8, dunno for the moment, maybe a TomEE 3.x.y Back to 1.x.y, the third digit is usually for maintenance (bugfix and improvements). The second one is for new features and significant changes. Between 1.0.x and 1.5.0, we had a discussion all together and agreed that there were lot of new feature and improvements (see release notes where all should be clearer). We wanted to emphasis that huge work and decided to jump in the version. I'm not proposing to jump again, I just wanted to know what community and users have in mind and like to see in next release to decide what numbers are better. If 1.5.2 is a new maintenance release and does not contain any big new feature, I'm all ok to use that numbers. I'm not aware of Tomcat producing a new version since our last release, but the 1.5.2 could embedded the new release if available as well as other dependency upgrades. I have in mind at least CXF and maybe OpenJPA. Is it clearer? If I badly interpreted your thoughts, apologize and lemme know. Jean-Louis 2012/12/30 Alex The Rocker alex.m3...@gmail.com Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1
Re: CMS diff: TomEE Maven Plugin
Committed. On Dec 28, 2012, at 7:19 AM, Anonymous CMS User anonym...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/tomee-mp-getting-started.mdtext Index: trunk/content/tomee-mp-getting-started.mdtext === --- trunk/content/tomee-mp-getting-started.mdtext (revision 1426368) +++ trunk/content/tomee-mp-getting-started.mdtext (working copy) @@ -1,11 +1,12 @@ Title: TomEE Maven Plugin + # Generating a TomEE-Project with Maven TomEE provides a maven-archetype for generating a maven based project. This template-project is preconfigured with `javaee-api` (scope provided) and with the `tomee-maven-plugin` for starting the application with TomEE. The current version of the archetype is '1.0.1'. So the needed command to generate an application is: -mvn archetype:generate -DarchetypeGroupId=org.apache.openejb.maven -DarchetypeArtifactId=tomee-wapp-archetype -DarchetypeVersion=1.0.1 +mvn archetype:generate -DarchetypeGroupId=org.apache.openejb.maven -DarchetypeArtifactId=tomee-webapp-archetype -DarchetypeVersion=1.0.1 The first time you run this command maven downloads the archetype and some parts related to it. Afterwards you see a prompt which allows you to specify the groupId, artifactId, version and package of your application. If you are using 'tomee' as groupId, 'tomee-demo' as artifactId, '1.0' as version and 'myapp' as package, your console should show something like:
[DISCUSS] TomEE 1.5.2 release and 1.6.0
Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis
Re: [DISCUSS] TomEE 1.5.2 release and 1.6.0
Jean-Louis: This is a very serious topic for my company: we're releasing a product which we document that it is supported with Apache TomEE+ 1.5.x, x=1. The rationale for allowing our customers to use an higher fix version is to benefit from Apache Tomcat security fixes. When our product was based on Apache Tomcat instead of TomEE we had the same type of support policy : for example we wrote that we supported Apache Tomcat 7.0x, x=23. I am very concerned by a TomEE 1.6.0 version which could put an end to the 1.5.x series. Would it be possible for Apache TomEE team to stick to Apache Tomcat version conventions (too late for the middle number which could have stayed to '0', so we should be at version 1.0.3 instead of 1.5.1) ? Otherwise, if a 1.6.0 version is actually planned (for Java EE 8 alpha support, why not), then please keep 1.5.x series actives for a (long). Thanks, Alex. On Sat, Dec 29, 2012 at 11:44 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Hi guys, That are some painful bugs in 1.5.1. They are fixed in the trunk. So the question here is: what are the plans for next releases? We have basically 2 options: 1. try to push a new 1.5.2 by February or so 2. push a 1.6.0 We don't have so much new features for now, so I'm quite sure, we will get a 1.5.2 out. Thoughts are welcome. Another question is what to put in? As said previously, there are number of bugs fixed in trunk. Anything else you wanna get in? Any work (improvement, bugfixes, dependency updates, etc)? -- Jean-Louis
Re: CMS diff: TomEE Maven Plugin
Yes, I tried to do it when I realized Romain already did it.
JLouis
2012/12/28 David Blevins david.blev...@gmail.com
Applied! Thank you so much, Gerhard!
I think I had a stale version of that page, so the CMS merged and warned
me that it merged then committed. Let me know if the page is missing
something.
Thank you!
-David
On Dec 26, 2012, at 6:11 AM, Gerhard Petracek gpetra...@apache.org
wrote:
Clone URL (Committers only):
https://cms.apache.org/redirect?new=gpetracek;action=diff;uri=http://openejb.apache.org/tomee-mp-getting-started.mdtext
Index: trunk/content/tomee-mp-getting-started.mdtext
===
--- trunk/content/tomee-mp-getting-started.mdtext (revision 1425910)
+++ trunk/content/tomee-mp-getting-started.mdtext (working copy)
@@ -1 +1,49 @@
-Title: TomEE Maven Plugin
\ No newline at end of file
+Title: TomEE Maven Plugin
+# Generating a TomEE-Project with Maven
+
+TomEE provides a maven-archetype for generating a maven based project.
This template-project is preconfigured with `javaee-api` (scope provided)
and with the `tomee-maven-plugin` for starting the application with TomEE.
+
+The current version of the archetype is '1.0.1'. So the needed command
to generate an application is:
+
+mvn archetype:generate -DarchetypeGroupId=org.apache.openejb.maven
-DarchetypeArtifactId=tomee-wapp-archetype -DarchetypeVersion=1.0.1
+
+The first time you run this command maven downloads the archetype and
some parts related to it. Afterwards you see a prompt which allows you to
specify the groupId, artifactId, version and package of your application.
+If you are using 'tomee' as groupId, 'tomee-demo' as artifactId, '1.0'
as version and 'myapp' as package, your console should show something like:
+
+Define value for property 'groupId': : tomee
+Define value for property 'artifactId': : tomee-demo
+Define value for property 'version': 1.0-SNAPSHOT: : 1.0
+Define value for property 'package': tomee: : myapp
+Confirm properties configuration:
+groupId: tomee
+artifactId: tomee-demo
+version: 1.0
+package: myapp
+...
+[INFO] BUILD SUCCESS
+...
+
+Afterwards you see a new folder with the name you used for the
artifactId (in the previous example 'tomee-demo').
+For starting the application you have to change the current directory
to the directory of the generated application:
+
+cd tomee-demo
+
+# Starting a TomEE-Project with Maven
+
+With using the archetype everything you need is in place already. So
you just have to start TomEE with:
+
+mvn package tomee:run
+
+The first time you run this command takes a bit longer, because maven
has to download e.g. TomEE.
+Once those parts are downloaded, starting maven, deploying and starting
the generated application takes less than 10s (depending on your computer).
+
+# Accessing a started application
+
+The application gets deployed to `target/apache-tomee/webapps`. If
everything worked correctly, you should see two directories ('tomee' and
'tomee-demo-1.0') as well as a web-archive ('tomee-demo-1.0.war').
+The mentioned directories are also the context-paths you can access. In
our example the generated application contains a servlet mapped to
'/index'. So you can access it via:
+
+http://localhost:8080/[artifactId]-[version]/index
+
+e.g.:
+
+http://localhost:8080/tomee-demo-1.0/index
--
Jean-Louis
CMS diff: TomEE Maven Plugin
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/tomee-mp-getting-started.mdtext Index: trunk/content/tomee-mp-getting-started.mdtext === --- trunk/content/tomee-mp-getting-started.mdtext (revision 1426368) +++ trunk/content/tomee-mp-getting-started.mdtext (working copy) @@ -1,11 +1,12 @@ Title: TomEE Maven Plugin + # Generating a TomEE-Project with Maven TomEE provides a maven-archetype for generating a maven based project. This template-project is preconfigured with `javaee-api` (scope provided) and with the `tomee-maven-plugin` for starting the application with TomEE. The current version of the archetype is '1.0.1'. So the needed command to generate an application is: -mvn archetype:generate -DarchetypeGroupId=org.apache.openejb.maven -DarchetypeArtifactId=tomee-wapp-archetype -DarchetypeVersion=1.0.1 +mvn archetype:generate -DarchetypeGroupId=org.apache.openejb.maven -DarchetypeArtifactId=tomee-webapp-archetype -DarchetypeVersion=1.0.1 The first time you run this command maven downloads the archetype and some parts related to it. Afterwards you see a prompt which allows you to specify the groupId, artifactId, version and package of your application. If you are using 'tomee' as groupId, 'tomee-demo' as artifactId, '1.0' as version and 'myapp' as package, your console should show something like:
Re: CMS diff: TomEE Maven Plugin
Applied! Thank you so much, Gerhard!
I think I had a stale version of that page, so the CMS merged and warned me
that it merged then committed. Let me know if the page is missing something.
Thank you!
-David
On Dec 26, 2012, at 6:11 AM, Gerhard Petracek gpetra...@apache.org wrote:
Clone URL (Committers only):
https://cms.apache.org/redirect?new=gpetracek;action=diff;uri=http://openejb.apache.org/tomee-mp-getting-started.mdtext
Index: trunk/content/tomee-mp-getting-started.mdtext
===
--- trunk/content/tomee-mp-getting-started.mdtext (revision 1425910)
+++ trunk/content/tomee-mp-getting-started.mdtext (working copy)
@@ -1 +1,49 @@
-Title: TomEE Maven Plugin
\ No newline at end of file
+Title: TomEE Maven Plugin
+# Generating a TomEE-Project with Maven
+
+TomEE provides a maven-archetype for generating a maven based project. This
template-project is preconfigured with `javaee-api` (scope provided) and with
the `tomee-maven-plugin` for starting the application with TomEE.
+
+The current version of the archetype is '1.0.1'. So the needed command to
generate an application is:
+
+mvn archetype:generate -DarchetypeGroupId=org.apache.openejb.maven
-DarchetypeArtifactId=tomee-wapp-archetype -DarchetypeVersion=1.0.1
+
+The first time you run this command maven downloads the archetype and some
parts related to it. Afterwards you see a prompt which allows you to specify
the groupId, artifactId, version and package of your application.
+If you are using 'tomee' as groupId, 'tomee-demo' as artifactId, '1.0' as
version and 'myapp' as package, your console should show something like:
+
+Define value for property 'groupId': : tomee
+Define value for property 'artifactId': : tomee-demo
+Define value for property 'version': 1.0-SNAPSHOT: : 1.0
+Define value for property 'package': tomee: : myapp
+Confirm properties configuration:
+groupId: tomee
+artifactId: tomee-demo
+version: 1.0
+package: myapp
+...
+[INFO] BUILD SUCCESS
+...
+
+Afterwards you see a new folder with the name you used for the artifactId
(in the previous example 'tomee-demo').
+For starting the application you have to change the current directory to the
directory of the generated application:
+
+cd tomee-demo
+
+# Starting a TomEE-Project with Maven
+
+With using the archetype everything you need is in place already. So you
just have to start TomEE with:
+
+mvn package tomee:run
+
+The first time you run this command takes a bit longer, because maven has to
download e.g. TomEE.
+Once those parts are downloaded, starting maven, deploying and starting the
generated application takes less than 10s (depending on your computer).
+
+# Accessing a started application
+
+The application gets deployed to `target/apache-tomee/webapps`. If
everything worked correctly, you should see two directories ('tomee' and
'tomee-demo-1.0') as well as a web-archive ('tomee-demo-1.0.war').
+The mentioned directories are also the context-paths you can access. In our
example the generated application contains a servlet mapped to '/index'. So
you can access it via:
+
+http://localhost:8080/[artifactId]-[version]/index
+
+e.g.:
+
+http://localhost:8080/tomee-demo-1.0/index
CMS diff: TomEE Maven Plugin
Clone URL (Committers only):
https://cms.apache.org/redirect?new=gpetracek;action=diff;uri=http://openejb.apache.org/tomee-mp-getting-started.mdtext
Index: trunk/content/tomee-mp-getting-started.mdtext
===
--- trunk/content/tomee-mp-getting-started.mdtext (revision 1425910)
+++ trunk/content/tomee-mp-getting-started.mdtext (working copy)
@@ -1 +1,49 @@
-Title: TomEE Maven Plugin
\ No newline at end of file
+Title: TomEE Maven Plugin
+# Generating a TomEE-Project with Maven
+
+TomEE provides a maven-archetype for generating a maven based project. This
template-project is preconfigured with `javaee-api` (scope provided) and with
the `tomee-maven-plugin` for starting the application with TomEE.
+
+The current version of the archetype is '1.0.1'. So the needed command to
generate an application is:
+
+mvn archetype:generate -DarchetypeGroupId=org.apache.openejb.maven
-DarchetypeArtifactId=tomee-wapp-archetype -DarchetypeVersion=1.0.1
+
+The first time you run this command maven downloads the archetype and some
parts related to it. Afterwards you see a prompt which allows you to specify
the groupId, artifactId, version and package of your application.
+If you are using 'tomee' as groupId, 'tomee-demo' as artifactId, '1.0' as
version and 'myapp' as package, your console should show something like:
+
+Define value for property 'groupId': : tomee
+Define value for property 'artifactId': : tomee-demo
+Define value for property 'version': 1.0-SNAPSHOT: : 1.0
+Define value for property 'package': tomee: : myapp
+Confirm properties configuration:
+groupId: tomee
+artifactId: tomee-demo
+version: 1.0
+package: myapp
+...
+[INFO] BUILD SUCCESS
+...
+
+Afterwards you see a new folder with the name you used for the artifactId (in
the previous example 'tomee-demo').
+For starting the application you have to change the current directory to the
directory of the generated application:
+
+cd tomee-demo
+
+# Starting a TomEE-Project with Maven
+
+With using the archetype everything you need is in place already. So you just
have to start TomEE with:
+
+mvn package tomee:run
+
+The first time you run this command takes a bit longer, because maven has to
download e.g. TomEE.
+Once those parts are downloaded, starting maven, deploying and starting the
generated application takes less than 10s (depending on your computer).
+
+# Accessing a started application
+
+The application gets deployed to `target/apache-tomee/webapps`. If everything
worked correctly, you should see two directories ('tomee' and 'tomee-demo-1.0')
as well as a web-archive ('tomee-demo-1.0.war').
+The mentioned directories are also the context-paths you can access. In our
example the generated application contains a servlet mapped to '/index'. So you
can access it via:
+
+http://localhost:8080/[artifactId]-[version]/index
+
+e.g.:
+
+http://localhost:8080/tomee-demo-1.0/index
Re: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-web
I wonder about some basic arquillian tests but dont know if it should be embedded/remote/both Le 26 déc. 2012 18:59, stratwine tovishwan...@gmail.com a écrit : Hi, Had pushed such a crud application.. a book catalog application with a jsf front end. (cdi bean + ejb + openjpa-maven-plugin ) r1425328 Test yet to be added. Does this look fine ? Any other ideas / any new archetype could be useful ? -Vishwa -- View this message in context: http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1417653-in-openejb-trunk-openejb-maven-tomee-webapp-archetype-tomee-webapp-archetype-tp4659123p4659894.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Fwd: svn commit: r1423006 - in /openejb/trunk/openejb: arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/ arquillian/arquill
Sure, in general. But 1. This is in trunk, and 2. org.jboss.arquillian.spock is an Alpha. So really only trying to get this to build and test on the bots for groovy 2.x for now. Which I think it now does. I think I even removed a snapshot already. Which snapshot are you not liking? -- View this message in context: http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1423006-in-openejb-trunk-openejb-arquillian-arquillian-tomee-tests-arquillian-tomee--tp4659765p4659789.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Fwd: svn commit: r1423006 - in /openejb/trunk/openejb: arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/ arquillian/arquill
you removed it this morning, right? well now that's fine for me my point is we don't need to be up to up to date on these parts so releases are better than snapshots IMO so all is fine now, thks :) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/18 AndyG andy.gumbre...@orprovision.com: Sure, in general. But 1. This is in trunk, and 2. org.jboss.arquillian.spock is an Alpha. So really only trying to get this to build and test on the bots for groovy 2.x for now. Which I think it now does. I think I even removed a snapshot already. Which snapshot are you not liking? -- View this message in context: http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1423006-in-openejb-trunk-openejb-arquillian-arquillian-tomee-tests-arquillian-tomee--tp4659765p4659789.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Fwd: svn commit: r1423544 - /openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Hi Thiago,
if i understand here jndi = ejbs?
it doesn't really match, there is not the resources and all the user
could have bound.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
-- Forwarded message --
From: tveron...@apache.org
Date: 2012/12/18
Subject: svn commit: r1423544 -
/openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
To: comm...@openejb.apache.org
Author: tveronezi
Date: Tue Dec 18 17:32:42 2012
New Revision: 1423544
URL: http://svn.apache.org/viewvc?rev=1423544view=rev
Log:
Better way to list the JNDI values.
Modified:
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Modified:
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java?rev=1423544r1=1423543r2=1423544view=diff
==
---
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
(original)
+++
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Tue Dec 18 17:32:42 2012
@@ -17,14 +17,12 @@
package org.apache.tomee.webapp.command.impl;
-import org.apache.tomee.webapp.Application;
+import org.apache.openejb.BeanContext;
+import org.apache.openejb.loader.SystemInstance;
+import org.apache.openejb.spi.ContainerSystem;
import org.apache.tomee.webapp.command.Command;
import org.apache.tomee.webapp.command.IsProtected;
-import javax.naming.Context;
-import javax.naming.NameClassPair;
-import javax.naming.NamingEnumeration;
-import javax.naming.NamingException;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
@@ -36,32 +34,18 @@ public class GetJndi implements Command
@Override
public Object execute(final MapString, Object params) throws Exception {
final String sessionId = (String) params.get(sessionId);
-final Application.Session session =
Application.getInstance().getSession(sessionId);
final ListString jndi = new ArrayListString();
-list(session.getContext(), jndi, );
+ContainerSystem container =
SystemInstance.get().getComponent(ContainerSystem.class);
+BeanContext[] deployments = container.deployments();
+if (deployments != null) {
+for (BeanContext beanContext : deployments) {
+jndi.add(String.valueOf(beanContext.getDeploymentID()));
+}
+}
+
final MapString, Object json = new HashMapString, Object();
json.put(jndi, jndi);
-
return json;
}
-
-private void list(final Context context, final ListString jndi,
String path) throws NamingException {
-final NamingEnumerationNameClassPair namingEnum = context.list();
-while (namingEnum.hasMore()) {
-final NameClassPair pair = namingEnum.next();
-
-String namePath = (path + / + pair.getName()).trim();
-if (namePath.startsWith(/)) {
-namePath = namePath.substring(1);
-}
-jndi.add(namePath);
-
-final Object obj = context.lookup(pair.getName());
-if (Context.class.isInstance(obj)) {
-list((Context) obj, jndi, namePath);
-}
-}
-}
-
}
Re: svn commit: r1423544 - /openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Hi Romain,
It is still wrong... working on that.
btw, do you know a good way to get the JNDI names? I just want to list
the same jndi strings shown in the log file.
[]s,
Thiago.
On Tue, Dec 18, 2012 at 12:54 PM, Romain Manni-Bucau
rmannibu...@gmail.com wrote:
Hi Thiago,
if i understand here jndi = ejbs?
it doesn't really match, there is not the resources and all the user
could have bound.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
-- Forwarded message --
From: tveron...@apache.org
Date: 2012/12/18
Subject: svn commit: r1423544 -
/openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
To: comm...@openejb.apache.org
Author: tveronezi
Date: Tue Dec 18 17:32:42 2012
New Revision: 1423544
URL: http://svn.apache.org/viewvc?rev=1423544view=rev
Log:
Better way to list the JNDI values.
Modified:
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Modified:
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java?rev=1423544r1=1423543r2=1423544view=diff
==
---
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
(original)
+++
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Tue Dec 18 17:32:42 2012
@@ -17,14 +17,12 @@
package org.apache.tomee.webapp.command.impl;
-import org.apache.tomee.webapp.Application;
+import org.apache.openejb.BeanContext;
+import org.apache.openejb.loader.SystemInstance;
+import org.apache.openejb.spi.ContainerSystem;
import org.apache.tomee.webapp.command.Command;
import org.apache.tomee.webapp.command.IsProtected;
-import javax.naming.Context;
-import javax.naming.NameClassPair;
-import javax.naming.NamingEnumeration;
-import javax.naming.NamingException;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
@@ -36,32 +34,18 @@ public class GetJndi implements Command
@Override
public Object execute(final MapString, Object params) throws Exception
{
final String sessionId = (String) params.get(sessionId);
-final Application.Session session =
Application.getInstance().getSession(sessionId);
final ListString jndi = new ArrayListString();
-list(session.getContext(), jndi, );
+ContainerSystem container =
SystemInstance.get().getComponent(ContainerSystem.class);
+BeanContext[] deployments = container.deployments();
+if (deployments != null) {
+for (BeanContext beanContext : deployments) {
+jndi.add(String.valueOf(beanContext.getDeploymentID()));
+}
+}
+
final MapString, Object json = new HashMapString, Object();
json.put(jndi, jndi);
-
return json;
}
-
-private void list(final Context context, final ListString jndi,
String path) throws NamingException {
-final NamingEnumerationNameClassPair namingEnum = context.list();
-while (namingEnum.hasMore()) {
-final NameClassPair pair = namingEnum.next();
-
-String namePath = (path + / + pair.getName()).trim();
-if (namePath.startsWith(/)) {
-namePath = namePath.substring(1);
-}
-jndi.add(namePath);
-
-final Object obj = context.lookup(pair.getName());
-if (Context.class.isInstance(obj)) {
-list((Context) obj, jndi, namePath);
-}
-}
-}
-
}
Re: svn commit: r1423544 - /openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Cool... tkx!
I will try that.
[]s,
Thiago.
On Tue, Dec 18, 2012 at 2:01 PM, Romain Manni-Bucau
rmannibu...@gmail.com wrote:
hmm they are in
SystemInstance.get().getComponent(ContainerSystem.class).getJNDIContext()
context
don't think you can get they without reproducing the logic used for
the log (and that's not a solution ;)
BTW listing
SystemInstance.get().getComponent(ContainerSystem.class).getJNDIContext().lookup(java:global)
should be fine as a first step
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2012/12/18 Thiago Veronezi thi...@veronezi.org:
Hi Romain,
It is still wrong... working on that.
btw, do you know a good way to get the JNDI names? I just want to list
the same jndi strings shown in the log file.
[]s,
Thiago.
On Tue, Dec 18, 2012 at 12:54 PM, Romain Manni-Bucau
rmannibu...@gmail.com wrote:
Hi Thiago,
if i understand here jndi = ejbs?
it doesn't really match, there is not the resources and all the user
could have bound.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
-- Forwarded message --
From: tveron...@apache.org
Date: 2012/12/18
Subject: svn commit: r1423544 -
/openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
To: comm...@openejb.apache.org
Author: tveronezi
Date: Tue Dec 18 17:32:42 2012
New Revision: 1423544
URL: http://svn.apache.org/viewvc?rev=1423544view=rev
Log:
Better way to list the JNDI values.
Modified:
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Modified:
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java?rev=1423544r1=1423543r2=1423544view=diff
==
---
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
(original)
+++
openejb/trunk/openejb/tomee/tomee-webapp/src/main/java/org/apache/tomee/webapp/command/impl/GetJndi.java
Tue Dec 18 17:32:42 2012
@@ -17,14 +17,12 @@
package org.apache.tomee.webapp.command.impl;
-import org.apache.tomee.webapp.Application;
+import org.apache.openejb.BeanContext;
+import org.apache.openejb.loader.SystemInstance;
+import org.apache.openejb.spi.ContainerSystem;
import org.apache.tomee.webapp.command.Command;
import org.apache.tomee.webapp.command.IsProtected;
-import javax.naming.Context;
-import javax.naming.NameClassPair;
-import javax.naming.NamingEnumeration;
-import javax.naming.NamingException;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
@@ -36,32 +34,18 @@ public class GetJndi implements Command
@Override
public Object execute(final MapString, Object params) throws
Exception {
final String sessionId = (String) params.get(sessionId);
-final Application.Session session =
Application.getInstance().getSession(sessionId);
final ListString jndi = new ArrayListString();
-list(session.getContext(), jndi, );
+ContainerSystem container =
SystemInstance.get().getComponent(ContainerSystem.class);
+BeanContext[] deployments = container.deployments();
+if (deployments != null) {
+for (BeanContext beanContext : deployments) {
+jndi.add(String.valueOf(beanContext.getDeploymentID()));
+}
+}
+
final MapString, Object json = new HashMapString, Object();
json.put(jndi, jndi);
-
return json;
}
-
-private void list(final Context context, final ListString jndi,
String path) throws NamingException {
-final NamingEnumerationNameClassPair namingEnum =
context.list();
-while (namingEnum.hasMore()) {
-final NameClassPair pair = namingEnum.next();
-
-String namePath = (path + / + pair.getName()).trim();
-if (namePath.startsWith(/)) {
-namePath = namePath.substring(1);
-}
-jndi.add(namePath);
-
-final Object obj = context.lookup(pair.getName());
-if (Context.class.isInstance(obj)) {
-list((Context) obj, jndi, namePath);
-}
-}
-}
-
}
Fwd: svn commit: r1423006 - in /openejb/trunk/openejb: arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/ arquillian/arquillian-
hi Andy,
why depending on a snapshot?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
-- Forwarded message --
From: andygumbre...@apache.org
Date: 2012/12/17
Subject: svn commit: r1423006 - in /openejb/trunk/openejb:
arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/
arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/ja...
To: comm...@openejb.apache.org
Author: andygumbrecht
Date: Mon Dec 17 16:21:41 2012
New Revision: 1423006
URL: http://svn.apache.org/viewvc?rev=1423006view=rev
Log:
Fix
Modified:
openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/EarTest.java
openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/requestdispose/ServletDisposeRequestScopeTest.java
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/config/DeploymentModule.java
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/config/WebModule.java
openejb/trunk/openejb/examples/groovy-spock/pom.xml
openejb/trunk/openejb/examples/groovy-spock/src/test/java/org/superbiz/groovy/HelloSpecification.groovy
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/GlobalListenerSupport.java
Modified:
openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/EarTest.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/EarTest.java?rev=1423006r1=1423005r2=1423006view=diff
==
---
openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/EarTest.java
(original)
+++
openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/ear/EarTest.java
Mon Dec 17 16:21:41 2012
@@ -73,9 +73,16 @@ public class EarTest {
@Test
public void test() throws Exception {
-System.out.println(url);
final URL servlet = new URL(url, /red/green/blue);
+
+//boolean bob = true;
+//
+//while(bob){
+//Thread.sleep(1000);
+//}
+
+System.out.println(servlet.toExternalForm());
final String slurp = IO.slurp(servlet);
Assert.assertEquals(Test.class.getName(), slurp);
System.out.println(slurp);
Modified:
openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/requestdispose/ServletDisposeRequestScopeTest.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/requestdispose/ServletDisposeRequestScopeTest.java?rev=1423006r1=1423005r2=1423006view=diff
==
---
openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/requestdispose/ServletDisposeRequestScopeTest.java
(original)
+++
openejb/trunk/openejb/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/requestdispose/ServletDisposeRequestScopeTest.java
Mon Dec 17 16:21:41 2012
@@ -65,7 +65,7 @@ public class ServletDisposeRequestScopeT
final ByteArrayOutputStream os = new ByteArrayOutputStream();
int bytesRead;
-byte[] buffer = new byte[512];
+final byte[] buffer = new byte[512];
while ((bytesRead = is.read(buffer)) -1) {
os.write(buffer, 0, bytesRead);
}
Modified:
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/config/DeploymentModule.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/config/DeploymentModule.java?rev=1423006r1=1423005r2=1423006view=diff
==
---
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/config/DeploymentModule.java
(original)
+++
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/config/DeploymentModule.java
Mon Dec 17 16:21:41 2012
@@ -66,7 +66,7 @@ public interface DeploymentModule {
*/
private
Re: Blog entry - TomEE 1.5.1 release
I got a 404 :) On Sun, Dec 16, 2012 at 12:57 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes. -- Jean-Louis
Re: Blog entry - TomEE 1.5.1 release
404 too, :-( Il 16/12/2012 12:57, Jean-Louis MONTEIRO ha scritto: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes.
Re: Blog entry - TomEE 1.5.1 release
you need roller account, think only committer can get it @daniel: you don't have? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/16 Enrico Olivelli eolive...@gmail.com: 404 too, :-( Il 16/12/2012 12:57, Jean-Louis MONTEIRO ha scritto: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes.
Re: Blog entry - TomEE 1.5.1 release
Here's the preview link: https://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 Looks like my little script is slightly broken. -David On Dec 16, 2012, at 1:39 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: you need roller account, think only committer can get it @daniel: you don't have? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/16 Enrico Olivelli eolive...@gmail.com: 404 too, :-( Il 16/12/2012 12:57, Jean-Louis MONTEIRO ha scritto: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes.
Re: Blog entry - TomEE 1.5.1 release
Try this URL: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 I might add some links in there and maybe some highlights of the release notes. -David On Dec 16, 2012, at 1:47 PM, David Blevins david.blev...@gmail.com wrote: Here's the preview link: https://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 Looks like my little script is slightly broken. -David On Dec 16, 2012, at 1:39 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: you need roller account, think only committer can get it @daniel: you don't have? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/16 Enrico Olivelli eolive...@gmail.com: 404 too, :-( Il 16/12/2012 12:57, Jean-Louis MONTEIRO ha scritto: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes.
Re: Blog entry - TomEE 1.5.1 release
Expanded it a bit with some summary details: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 -David On Dec 16, 2012, at 2:18 PM, David Blevins david.blev...@gmail.com wrote: Try this URL: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 I might add some links in there and maybe some highlights of the release notes. -David On Dec 16, 2012, at 1:47 PM, David Blevins david.blev...@gmail.com wrote: Here's the preview link: https://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 Looks like my little script is slightly broken. -David On Dec 16, 2012, at 1:39 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: you need roller account, think only committer can get it @daniel: you don't have? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/16 Enrico Olivelli eolive...@gmail.com: 404 too, :-( Il 16/12/2012 12:57, Jean-Louis MONTEIRO ha scritto: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes.
Re: Blog entry - TomEE 1.5.1 release
Tomcat 7.0.34 no? Le 17 déc. 2012 06:54, David Blevins david.blev...@gmail.com a écrit : Expanded it a bit with some summary details: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 -David On Dec 16, 2012, at 2:18 PM, David Blevins david.blev...@gmail.com wrote: Try this URL: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 I might add some links in there and maybe some highlights of the release notes. -David On Dec 16, 2012, at 1:47 PM, David Blevins david.blev...@gmail.com wrote: Here's the preview link: https://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 Looks like my little script is slightly broken. -David On Dec 16, 2012, at 1:39 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: you need roller account, think only committer can get it @daniel: you don't have? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/16 Enrico Olivelli eolive...@gmail.com: 404 too, :-( Il 16/12/2012 12:57, Jean-Louis MONTEIRO ha scritto: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes.
Re: Blog entry - TomEE 1.5.1 release
About the 'downloads.html' that we link to.. During each release, we update this page and then users don't have quick access to download links of previous releases. I think it would be a good idea to have the old download.html content, copied on to a new static page (say download-1.5.html) before updating. (likewise for each release) I'll add a page with old links later today. -Vishwa On Mon, Dec 17, 2012 at 12:25 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Tomcat 7.0.34 no? Le 17 déc. 2012 06:54, David Blevins david.blev...@gmail.com a écrit : Expanded it a bit with some summary details: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 -David On Dec 16, 2012, at 2:18 PM, David Blevins david.blev...@gmail.com wrote: Try this URL: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 I might add some links in there and maybe some highlights of the release notes. -David On Dec 16, 2012, at 1:47 PM, David Blevins david.blev...@gmail.com wrote: Here's the preview link: https://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 Looks like my little script is slightly broken. -David On Dec 16, 2012, at 1:39 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: you need roller account, think only committer can get it @daniel: you don't have? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/16 Enrico Olivelli eolive...@gmail.com: 404 too, :-( Il 16/12/2012 12:57, Jean-Louis MONTEIRO ha scritto: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes.
Re: Blog entry - TomEE 1.5.1 release
Thanks David for fixing. It was only meant to get people used to visit our website and also to make sure TomEE is still active. @Romain, yes, updating the Tomcat version. Jean-Louis 2012/12/17 Romain Manni-Bucau rmannibu...@gmail.com Tomcat 7.0.34 no? Le 17 déc. 2012 06:54, David Blevins david.blev...@gmail.com a écrit : Expanded it a bit with some summary details: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 -David On Dec 16, 2012, at 2:18 PM, David Blevins david.blev...@gmail.com wrote: Try this URL: http://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 I might add some links in there and maybe some highlights of the release notes. -David On Dec 16, 2012, at 1:47 PM, David Blevins david.blev...@gmail.com wrote: Here's the preview link: https://blogs.apache.org/preview/openejb/?previewEntry=apache_tomee_1_5_1 Looks like my little script is slightly broken. -David On Dec 16, 2012, at 1:39 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: you need roller account, think only committer can get it @daniel: you don't have? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/16 Enrico Olivelli eolive...@gmail.com: 404 too, :-( Il 16/12/2012 12:57, Jean-Louis MONTEIRO ha scritto: Hi, Just prepared two words on the blog. If not feedback, it will publish it on Monday or next week. https://blogs.apache.org/openejb/entry/apache_tomee_1_5_1 The goal is not to write a huge story, but just to keep people focus on TomEE and to see it's alive and produces releases (more or less regular). I updated the download page with all link and the release notes. -- Jean-Louis
[RESULT] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
Vote closed. Vote passes with 9 +1s and a 0 +1s Romain Manni-Bucau Jean-Louis Monteiro David Blevins Jeff Genender Jonathan Gallimore Vishwanath Krishnamurthi Thiago Veronezi Alan Cabrera Joerg Jans 0 Andy Gumbrecht Thanks everyone who voted! Will promote binaries and update download links and so on. Jean-Louis 2012/12/10 Jean-Louis MONTEIRO jeano...@gmail.com [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html Vote will be open for 72 hours or as needed. -- Jean-Louis
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
+1 Regards, Alan On Dec 10, 2012, at 5:48 AM, Jean-Louis MONTEIRO wrote: [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html Vote will be open for 72 hours or as needed.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
(not sure I can vote, but here's the deal) I installed Apache TomEE+ 1.5.1 from http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/, on a 64-bit Windows 7 machine, after having added a suitable JRE_HOME into startup.bat. I tried to register TomEE+ as a service : 1. set JRE_HOME=c:\Program Files\Java\jdk1.7.0_09 2. From a command prompt with current working directory in TomEE's bin/ directory, typed: service.bat install Here's what I get: E:\NoSave\tomEE\apache-tomee-plus-1.5.1\binservice.bat install Installing the service 'TomEE' ... Using CATALINA_HOME:E:\NoSave\tomEE\apache-tomee-plus-1.5.1 Using CATALINA_BASE:E:\NoSave\tomEE\apache-tomee-plus-1.5.1 Using JAVA_HOME: Using JRE_HOME: c:\Program Files\Java\jdk1.7.0_09 Using JVM: auto E:\NoSave\tomEE\apache-tomee-plus-1.5.1\bin\TomEE.AMD64.exe //IS//TomEE [2012-12-13 16:51:53] [error] Unrecognized cmd option E:\NoSave\tomEE\apache-tom ee-plus-1.5.1\bin\TomEE.AMD64.exe [2012-12-13 16:51:53] [error] Invalid command line arguments [2012-12-13 16:51:53] [error] Commons Daemon procrun failed with exit value: 1 ( Failed to parse command line arguments) Failed installing 'TomEE' service Baseline, TomEE registry as a Windows service seems to be broken like it was in 1.5.0 and in 1.0.0, but in a slightly different way. I doubt it can be released as is, don't you think? Thanks, Alex On Thu, Dec 13, 2012 at 3:43 PM, Alan Cabrera l...@toolazydogs.com wrote: +1 Regards, Alan On Dec 10, 2012, at 5:48 AM, Jean-Louis MONTEIRO wrote: [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html Vote will be open for 72 hours or as needed.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
i don't think and the time is out so the release passed (isn't it JL?) btw anyone having this issue too? i didn't see any commit on it and it was working fine for me last time i checked the win scripts. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/13 Alex The Rocker alex.m3...@gmail.com: (not sure I can vote, but here's the deal) I installed Apache TomEE+ 1.5.1 from http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/, on a 64-bit Windows 7 machine, after having added a suitable JRE_HOME into startup.bat. I tried to register TomEE+ as a service : 1. set JRE_HOME=c:\Program Files\Java\jdk1.7.0_09 2. From a command prompt with current working directory in TomEE's bin/ directory, typed: service.bat install Here's what I get: E:\NoSave\tomEE\apache-tomee-plus-1.5.1\binservice.bat install Installing the service 'TomEE' ... Using CATALINA_HOME:E:\NoSave\tomEE\apache-tomee-plus-1.5.1 Using CATALINA_BASE:E:\NoSave\tomEE\apache-tomee-plus-1.5.1 Using JAVA_HOME: Using JRE_HOME: c:\Program Files\Java\jdk1.7.0_09 Using JVM: auto E:\NoSave\tomEE\apache-tomee-plus-1.5.1\bin\TomEE.AMD64.exe //IS//TomEE [2012-12-13 16:51:53] [error] Unrecognized cmd option E:\NoSave\tomEE\apache-tom ee-plus-1.5.1\bin\TomEE.AMD64.exe [2012-12-13 16:51:53] [error] Invalid command line arguments [2012-12-13 16:51:53] [error] Commons Daemon procrun failed with exit value: 1 ( Failed to parse command line arguments) Failed installing 'TomEE' service Baseline, TomEE registry as a Windows service seems to be broken like it was in 1.5.0 and in 1.0.0, but in a slightly different way. I doubt it can be released as is, don't you think? Thanks, Alex On Thu, Dec 13, 2012 at 3:43 PM, Alan Cabrera l...@toolazydogs.com wrote: +1 Regards, Alan On Dec 10, 2012, at 5:48 AM, Jean-Louis MONTEIRO wrote: [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html Vote will be open for 72 hours or as needed.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
Done!
2012/12/11 David Blevins david.blev...@gmail.com
wget
https://repository.apache.org/content/repositories/orgapacheopenejb-132/org/apache/openejb/openejb-standalone/4.5.1/openejb-standalone-4.5.1.{tar.gz,zip}{,.asc,sha1,md5}
--
Jean-Louis
R: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
My webapps are running better on Tomee 1.5.1 Thanks Great work ! Enrico Olivelli Software Development Manager @Diennea Tel.: (+39) 0546 667432 - Int. 925 Viale G.Marconi 30/14 - 48018 Faenza (RA) MagNews - E-mail Marketing Solutions http://www.magnews.it Diennea - Digital Marketing Solutions http://www.diennea.com -Messaggio originale- Da: Jean-Louis MONTEIRO [mailto:jeano...@gmail.com] Inviato: lunedì 10 dicembre 2012 14:49 A: dev@openejb.apache.org Oggetto: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132) [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html Vote will be open for 72 hours or as needed. Scarica la ricerca completa di MagNews “Digital Marketing Trends 2012” Quali sono le percezioni relative all’utilizzo dell’email privata e aziendale da parte degli utenti internet italiani? E’ cambiato qualcosa rispetto al 2011? http://www.magnews.it/it/risorse/ricerche/digital-marketing-trends
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
+0 Still some minor Win platform test failures. We should disable the tests. Other than that everything looks good to go. -- View this message in context: http://openejb.979440.n4.nabble.com/VOTE-OpenEJB-4-5-1-TomEE-1-5-1-staging-132-tp4659354p4659401.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
+1 On Tue, Dec 11, 2012 at 5:20 AM, AndyG andy.gumbre...@orprovision.com wrote: +0 Still some minor Win platform test failures. We should disable the tests. Other than that everything looks good to go. -- View this message in context: http://openejb.979440.n4.nabble.com/VOTE-OpenEJB-4-5-1-TomEE-1-5-1-staging-132-tp4659354p4659401.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
+1 I just tested our project with the preview of 1.5.1 running on a windows machine. All the problems we encountered with 1.5 are gone. -- View this message in context: http://openejb.979440.n4.nabble.com/VOTE-OpenEJB-4-5-1-TomEE-1-5-1-staging-132-tp4659354p4659428.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
On Dec 10, 2012, at 5:48 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote:
Binaries Source:
http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/
Whoops. I just noticed the OpenEJB Standalone zip/tar are not in the binaries
directory. This is a bug in the release-tools I thought I fixed -- it happened
in 1.5.0 as well.
Meanwhile, we can manually pull down the openejb-standalone binaries with a
slick bash command like so:
wget
https://repository.apache.org/content/repositories/orgapacheopenejb-132/org/apache/openejb/openejb-standalone/4.5.1/openejb-standalone-4.5.1.{tar.gz,zip}{,.asc,sha1,md5}
-David
[preview] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
[generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html
Re: [preview] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
Everything ready for vote. Anyone wants to get into before I fire the real vote? Jean-Louis 2012/12/10 jlmonte...@apache.org [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html -- Jean-Louis
Re: [preview] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
go for it Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/10 Jean-Louis MONTEIRO jeano...@gmail.com: Everything ready for vote. Anyone wants to get into before I fire the real vote? Jean-Louis 2012/12/10 jlmonte...@apache.org [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html -- Jean-Louis
[VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
[generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~a102126/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~a102126/staging-132/legal/archives.html Vote will be open for 72 hours or as needed.
[CANCELED] [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
Sorry, bad user name ... 2012/12/10 a102...@apache.org [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~a102126/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~a102126/staging-132/legal/archives.html Vote will be open for 72 hours or as needed. -- Jean-Louis
[VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
[generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html Vote will be open for 72 hours or as needed.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
Additional information Release Notes: http://people.apache.org/~jlmonteiro/staging-132/releasenotes-1.5.1.html Rat report: http://people.apache.org/~jlmonteiro/staging-132/rat-1.5.1.txt Binaries comparison report: http://people.apache.org/~jlmonteiro/staging-132/compareLibraries-1.5.1.txt Buildbot latest result on branch: http://ci.apache.org/builders/openejb-4.5.1/builds/22 Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/VOTE-OpenEJB-4-5-1-TomEE-1-5-1-staging-132-tp4659354p4659355.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
Here is my +1 Jean-Louis 2012/12/10 Romain Manni-Bucau rmannibu...@gmail.com +1 Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/10 Jean-Louis MONTEIRO jeano...@gmail.com: Additional information Release Notes: http://people.apache.org/~jlmonteiro/staging-132/releasenotes-1.5.1.html Rat report: http://people.apache.org/~jlmonteiro/staging-132/rat-1.5.1.txt Binaries comparison report: http://people.apache.org/~jlmonteiro/staging-132/compareLibraries-1.5.1.txt Buildbot latest result on branch: http://ci.apache.org/builders/openejb-4.5.1/builds/22 Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/VOTE-OpenEJB-4-5-1-TomEE-1-5-1-staging-132-tp4659354p4659355.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Jean-Louis
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
TCK looks good as well. My +1! Such an excellent job Jean-Louis! This is a big milestone for the project. Getting more people familiar with the release process is critical and you've done a fantastic job at it. Thank you as well to Elisa and Luna for donating their Jean-Louis time to us :) Really awesome. -David On Dec 10, 2012, at 5:48 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html Vote will be open for 72 hours or as needed.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
+1 Jeff On Dec 10, 2012, at 6:58 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Additional information Release Notes: http://people.apache.org/~jlmonteiro/staging-132/releasenotes-1.5.1.html Rat report: http://people.apache.org/~jlmonteiro/staging-132/rat-1.5.1.txt Binaries comparison report: http://people.apache.org/~jlmonteiro/staging-132/compareLibraries-1.5.1.txt Buildbot latest result on branch: http://ci.apache.org/builders/openejb-4.5.1/builds/22 Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/VOTE-OpenEJB-4-5-1-TomEE-1-5-1-staging-132-tp4659354p4659355.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [VOTE] OpenEJB 4.5.1/TomEE 1.5.1 (staging-132)
+1 Jon On Mon, Dec 10, 2012 at 1:48 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.1/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-132 Binaries Source: http://people.apache.org/~jlmonteiro/staging-132/openejb-4.5.1/ Legal: http://people.apache.org/~jlmonteiro/staging-132/legal/archives.html Vote will be open for 72 hours or as needed.
TomEE 1.5.1 binaries preview
Hi devs, Ok, hope that set of binaries will be ok for everybody. All patches should be in. https://repository.apache.org/content/repositories/orgapacheopenejb-132/ Will republish everything and fire a vote by tomorrow. -- Jean-Louis
TomEE 1.5.1: new release notes (to review)
Hi, Just a small message to let you start reviewing the 1.5.1 release notes. http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html -- Jean-Louis
TomEE 1.5.1: release process status
Hi all, Here are some news about the release process. Check out all points in https://issues.apache.org/jira/browse/TOMEE-526 Some useful links http://people.apache.org/~jlmonteiro/rat-1.5.1.txt http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html http://people.apache.org/~rmannibucau/orgapacheopenejb-118/archives.html -- Jean-Louis
Re: TomEE 1.5.1: release process status
Some minor fixes, so here are new binaries https://repository.apache.org/content/repositories/orgapacheopenejb-123/ http://people.apache.org/~rmannibucau/orgapacheopenejb-123/ Jaen-Louis 2012/12/7 Jean-Louis MONTEIRO jeano...@gmail.com Hi all, Here are some news about the release process. Check out all points in https://issues.apache.org/jira/browse/TOMEE-526 Some useful links http://people.apache.org/~jlmonteiro/rat-1.5.1.txt http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html http://people.apache.org/~rmannibucau/orgapacheopenejb-118/archives.html -- Jean-Louis -- Jean-Louis 2012/12/7 Jean-Louis MONTEIRO jeano...@gmail.com Hi all, Here are some news about the release process. Check out all points in https://issues.apache.org/jira/browse/TOMEE-526 Some useful links http://people.apache.org/~jlmonteiro/rat-1.5.1.txt http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html http://people.apache.org/~rmannibucau/orgapacheopenejb-118/archives.html -- Jean-Louis -- Jean-Louis
Re: TomEE 1.5.1: release process status
here the new binaries: https://repository.apache.org/content/repositories/orgapacheopenejb-124/ (just a java patch applied) 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 Jean-Louis MONTEIRO jeano...@gmail.com: Some minor fixes, so here are new binaries https://repository.apache.org/content/repositories/orgapacheopenejb-123/ http://people.apache.org/~rmannibucau/orgapacheopenejb-123/ Jaen-Louis 2012/12/7 Jean-Louis MONTEIRO jeano...@gmail.com Hi all, Here are some news about the release process. Check out all points in https://issues.apache.org/jira/browse/TOMEE-526 Some useful links http://people.apache.org/~jlmonteiro/rat-1.5.1.txt http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html http://people.apache.org/~rmannibucau/orgapacheopenejb-118/archives.html -- Jean-Louis -- Jean-Louis 2012/12/7 Jean-Louis MONTEIRO jeano...@gmail.com Hi all, Here are some news about the release process. Check out all points in https://issues.apache.org/jira/browse/TOMEE-526 Some useful links http://people.apache.org/~jlmonteiro/rat-1.5.1.txt http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html http://people.apache.org/~rmannibucau/orgapacheopenejb-118/archives.html -- Jean-Louis -- Jean-Louis
Fwd: svn commit: r1418530 - /openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/LazyStopWebappClassLoader.java
Think we should catch noclassdeffounderror too,
Anyone to add it on trunk + branch please? Cant do it before monday
-- Message transféré --
De : jlmonte...@apache.org
Date : 7 déc. 2012 23:44
Objet : svn commit: r1418530 -
/openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/LazyStopWebappClassLoader.java
À : comm...@openejb.apache.org
Author: jlmonteiro
Date: Fri Dec 7 22:43:47 2012
New Revision: 1418530
URL: http://svn.apache.org/viewvc?rev=1418530view=rev
Log:
Add a fallback to the parent classloader for Atmosphere mainly
Modified:
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/LazyStopWebappClassLoader.java
Modified:
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/LazyStopWebappClassLoader.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/LazyStopWebappClassLoader.java?rev=1418530r1=1418529r2=1418530view=diff
==
---
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/LazyStopWebappClassLoader.java
(original)
+++
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/LazyStopWebappClassLoader.java
Fri Dec 7 22:43:47 2012
@@ -87,7 +87,11 @@ public class LazyStopWebappClassLoader e
// avoid to redefine classes from server in this classloader is it
not already loaded
if (URLClassLoaderFirst.shouldSkip(name)) {
-return OpenEJB.class.getClassLoader().loadClass(name);
+try {
+return OpenEJB.class.getClassLoader().loadClass(name);
+} catch (ClassNotFoundException e) {
+return super.loadClass(name);
+}
}
return super.loadClass(name);
}
Re: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-web
Hi Romain, Would be nice to have these added to it. I'll get started with this, this evening. -Vishwa On Thu, Dec 6, 2012 at 2:54 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi guys, with JL we got as feedback we were missing a real archetype with tomee maven plugin etc configured. i pushed a simple one i commented all the arquillian stuff (to avoid to need to pull it if not used) currently it only contain a servlet, and a beans.xml wonder if 1) we should put some basic persistence (1 entity + 1 persistence.xml + openjpa-maven-plugin to enhance the entity) 2) add a cdi bean and inject it in the servlet 3) add an ejb 4) add a test ... any help on such a topic is welcomed Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau -- Forwarded message -- From: rmannibu...@apache.org Date: 2012/12/5 Subject: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-webapp-archetype/src/main/resources/META-INF/ tomee-webapp-... To: comm...@openejb.apache.org Author: rmannibucau Date: Wed Dec 5 21:19:35 2012 New Revision: 1417653 URL: http://svn.apache.org/viewvc?rev=1417653view=rev Log: TOMEE-630 basic maven artifact (to enhance) Added: openejb/trunk/openejb/maven/tomee-webapp-archetype/ openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/META-INF/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/META-INF/archetype.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/pom.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/java/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/java/Index.java openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/beans.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/java/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/resources/arquillian.xml Modified: openejb/trunk/openejb/maven/pom.xml Modified: openejb/trunk/openejb/maven/pom.xml URL: http://svn.apache.org/viewvc/openejb/trunk/openejb/maven/pom.xml?rev=1417653r1=1417652r2=1417653view=diff == --- openejb/trunk/openejb/maven/pom.xml (original) +++ openejb/trunk/openejb/maven/pom.xml Wed Dec 5 21:19:35 2012 @@ -15,7 +15,6 @@ See the License for the specific language governing permissions and limitations under the License. -- - project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; @@ -41,6 +40,7 @@ modulemaven-util/module modulespi-helper-maven-plugin/module modulespi-helper-jee6-profile/module +moduletomee-webapp-archetype/module /modules dependencyManagement Added: openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml URL: http://svn.apache.org/viewvc/openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml?rev=1417653view=auto == --- openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml (added) +++ openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml Wed Dec 5 21:19:35 2012 @@ -0,0 +1,30 @@ +?xml version=1.0 encoding=UTF-8? +!-- +Licensed
Re: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-web
great! thinking to it i think a very simple crud with jsf front can be the expected quickstart wdyt? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/6 Vishwanath Krishnamurthi tovishwan...@gmail.com: Hi Romain, Would be nice to have these added to it. I'll get started with this, this evening. -Vishwa On Thu, Dec 6, 2012 at 2:54 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi guys, with JL we got as feedback we were missing a real archetype with tomee maven plugin etc configured. i pushed a simple one i commented all the arquillian stuff (to avoid to need to pull it if not used) currently it only contain a servlet, and a beans.xml wonder if 1) we should put some basic persistence (1 entity + 1 persistence.xml + openjpa-maven-plugin to enhance the entity) 2) add a cdi bean and inject it in the servlet 3) add an ejb 4) add a test ... any help on such a topic is welcomed Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau -- Forwarded message -- From: rmannibu...@apache.org Date: 2012/12/5 Subject: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-webapp-archetype/src/main/resources/META-INF/ tomee-webapp-... To: comm...@openejb.apache.org Author: rmannibucau Date: Wed Dec 5 21:19:35 2012 New Revision: 1417653 URL: http://svn.apache.org/viewvc?rev=1417653view=rev Log: TOMEE-630 basic maven artifact (to enhance) Added: openejb/trunk/openejb/maven/tomee-webapp-archetype/ openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/META-INF/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/META-INF/archetype.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/pom.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/java/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/java/Index.java openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/beans.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/java/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/resources/arquillian.xml Modified: openejb/trunk/openejb/maven/pom.xml Modified: openejb/trunk/openejb/maven/pom.xml URL: http://svn.apache.org/viewvc/openejb/trunk/openejb/maven/pom.xml?rev=1417653r1=1417652r2=1417653view=diff == --- openejb/trunk/openejb/maven/pom.xml (original) +++ openejb/trunk/openejb/maven/pom.xml Wed Dec 5 21:19:35 2012 @@ -15,7 +15,6 @@ See the License for the specific language governing permissions and limitations under the License. -- - project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; @@ -41,6 +40,7 @@ modulemaven-util/module modulespi-helper-maven-plugin/module modulespi-helper-jee6-profile/module +moduletomee-webapp-archetype/module /modules dependencyManagement Added: openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml URL: http://svn.apache.org/viewvc/openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml
Re: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-web
Sounds good to me ! -Vishwa On Thu, Dec 6, 2012 at 1:36 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: great! thinking to it i think a very simple crud with jsf front can be the expected quickstart wdyt? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/6 Vishwanath Krishnamurthi tovishwan...@gmail.com: Hi Romain, Would be nice to have these added to it. I'll get started with this, this evening. -Vishwa On Thu, Dec 6, 2012 at 2:54 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi guys, with JL we got as feedback we were missing a real archetype with tomee maven plugin etc configured. i pushed a simple one i commented all the arquillian stuff (to avoid to need to pull it if not used) currently it only contain a servlet, and a beans.xml wonder if 1) we should put some basic persistence (1 entity + 1 persistence.xml + openjpa-maven-plugin to enhance the entity) 2) add a cdi bean and inject it in the servlet 3) add an ejb 4) add a test ... any help on such a topic is welcomed Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau -- Forwarded message -- From: rmannibu...@apache.org Date: 2012/12/5 Subject: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-webapp-archetype/src/main/resources/META-INF/ tomee-webapp-... To: comm...@openejb.apache.org Author: rmannibucau Date: Wed Dec 5 21:19:35 2012 New Revision: 1417653 URL: http://svn.apache.org/viewvc?rev=1417653view=rev Log: TOMEE-630 basic maven artifact (to enhance) Added: openejb/trunk/openejb/maven/tomee-webapp-archetype/ openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/META-INF/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/META-INF/archetype.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/pom.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/java/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/java/Index.java openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/beans.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/java/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/resources/arquillian.xml Modified: openejb/trunk/openejb/maven/pom.xml Modified: openejb/trunk/openejb/maven/pom.xml URL: http://svn.apache.org/viewvc/openejb/trunk/openejb/maven/pom.xml?rev=1417653r1=1417652r2=1417653view=diff == --- openejb/trunk/openejb/maven/pom.xml (original) +++ openejb/trunk/openejb/maven/pom.xml Wed Dec 5 21:19:35 2012 @@ -15,7 +15,6 @@ See the License for the specific language governing permissions and limitations under the License. -- - project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; @@ -41,6 +40,7 @@ modulemaven-util/module modulespi-helper-maven-plugin/module modulespi-helper-jee6
CMS diff: TomEE and WebSphere MQ
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/tomee-and-webspheremq.mdtext rohid...@gmail.com Index: trunk/content/tomee-and-webspheremq.mdtext === --- trunk/content/tomee-and-webspheremq.mdtext (revision 1418184) +++ trunk/content/tomee-and-webspheremq.mdtext (working copy) @@ -15,3 +15,117 @@ KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. + +**Steps to integrate TomEE with Websphere MQ** br + +1. Unzip rar file place jars under tomee/lib + +2. Added the below to conf/tomee.xml + + + tomee /br + Container id=wmq type=MESSAGEbr +ResourceAdapter=wmqRA +MessageListenerInterface=javax.jms.MessageListener +ActivationSpecClass=com.ibm.mq.connector.inbound.ActivationSpecImpl +/br + /Container + + + Resource id=wmqRA type=com.ibm.mq.connector.ResourceAdapterImpl brclass-name=com.ibm.mq.connector.ResourceAdapterImpl +brconnectionConcurrency=5 /br +maxConnections=10 /br +logWriterEnabled=true /br +reconnectionRetryCount=5 /br +reconnectionRetryInterval=30 /br +traceEnabled=false /br +traceLevel=3 /br + /Resource + + Resource **id=qcf** /br type=javax.jms.ConnectionFactory class-name=com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl +TransactionSupport=none /br +ResourceAdapter=wmqRA /br +HostName=10.a.b.c /br +Port=1414 /br +QueueManager=QM_TIERL/br + Channel=SYSTEM.ADMIN.SVRCONN/br + TransportType=Client/br + UserName=xyz/br + Password=*/br + /Resource + + Resource id=wmq-javax.jms.QueueConnectionFactory /br type=javax.jms.QueueConnectionFactory class-name=com.ibm.mq.connector.outbound.ManagedQueueConnectionFactoryImpl +TransactionSupport=xa /br +ResourceAdapter=wmqRA /br + /Resource + + Resource id=wmq-javax.jms.TopicConnectionFactory /br type=javax.jms.TopicConnectionFactory class-name=com.ibm.mq.connector.outbound.ManagedTopicConnectionFactoryImpl +TransactionSupport=xa /br +ResourceAdapter=wmqRA /br + /Resource + + Resource **id=queue** type=javax.jms.Queue /br +class-name=com.ibm.mq.connector.outbound.MQQueueProxy /br +arbitraryProperties /br +baseQueueManagerName /br +baseQueueName /br +CCSID=1208 /br +encoding=NATIVE /br +expiry=APP /br +failIfQuiesce=true /br +persistence=APP /br +priority=APP /br +readAheadClosePolicy=ALL /br +targetClient=JMS /br + /Resource + + Resource id=wmq-javax.jms.Topic type=javax.jms.Topic class-name=com.ibm.mq.connector.outbound.MQTopicProxy +arbitraryProperties /br +baseTopicName /br +brokerCCDurSubQueue=SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE /br +brokerDurSubQueue=SYSTEM.JMS.D.SUBSCRIBER.QUEUE /br +brokerPubQueue /br +brokerPubQueueManager /br +brokerVersion=1 /br +CCSID=1208 /br +encoding=NATIVE /br +expiry=APP /br +failIfQuiesce=true /br +persistence=APP /br +priority=APP /br +readAheadClosePolicy=ALL /br +targetClient=JMS /br + /Resource /br + + /tomee + +3. in web.xml add the below to access resources/br + resource-ref /br + res-ref-namemyqcf /res-ref-name /br + res-typejavax.jms.ConnectionFactory /res-type/br + res-authContainer/res-auth /br + res-sharing-scopeShareable /res-sharing-scope/br + mapped-nameqcf /mapped-name/br + /resource-ref + + resource-env-ref/br +resource-env-ref-namemyqueue /resource-env-ref-name/br +resource-env-ref-typejavax.jms.Queue /resource-env-ref-type/br +mapped-namequeue /mapped-name/br + /resource-env-ref/br + +**Java Code: /br** + +@Resource(name = qcf) /br +private ConnectionFactory connectionFactory; /br +@Resource(name = queue) /br +private Queue queue;/br/br +Connection connection = connectionFactory.createConnection();/br +Session session = connection.createSession(false, QueueSession.AUTO_ACKNOWLEDGE); +MessageProducer producer = session.createProducer(queue);/br +TextMessage message = session.createTextMessage();/br +message.setText(Test Message);/br +connection.start();/br +producer.send(message);/br +session.close();/br +connection.close();/br
Fwd: [jira] [Created] (TOMEE-635) Revamp resources.xml deployment to not immediately install
Hi, What's the goal excepting get another resolution? -- Message transféré -- De : David Blevins (JIRA) j...@apache.org Date : 7 déc. 2012 03:33 Objet : [jira] [Created] (TOMEE-635) Revamp resources.xml deployment to not immediately install À : comm...@openejb.apache.org David Blevins created TOMEE-635: --- Summary: Revamp resources.xml deployment to not immediately install Key: TOMEE-635 URL: https://issues.apache.org/jira/browse/TOMEE-635 Project: TomEE Issue Type: Improvement Reporter: David Blevins Delay the installation of the of the resources, by adding them to the AppInfo, perhaps as a fake ConnectorInfo -- it has all the right Info object collections -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Fwd: [jira] [Created] (TOMEE-634) Resource class-name=org.foo.Bar/ requires org.foo.Bar to exist in server classloader
Same question ;) This requirement is normal and implicit (since a new is done), what's the issue? -- Message transféré -- De : David Blevins (JIRA) j...@apache.org Date : 7 déc. 2012 03:29 Objet : [jira] [Created] (TOMEE-634) Resource class-name=org.foo.Bar/ requires org.foo.Bar to exist in server classloader À : comm...@openejb.apache.org David Blevins created TOMEE-634: --- Summary: Resource class-name=org.foo.Bar/ requires org.foo.Bar to exist in server classloader Key: TOMEE-634 URL: https://issues.apache.org/jira/browse/TOMEE-634 Project: TomEE Issue Type: Bug Affects Versions: 1.5.1 Reporter: David Blevins -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
DeploymentLoader.java Revision 1416096 TOMEE-613: Extracted EARs do not deploy without META-INF/application.xml file
Pretty obvious what's going on here due to changes in DeploymentLoader.java on revision 1416096: UnknownModuleTypeException: Unable to determine module type for jar: file:/[path]/apps/*.svn* I have added some code to filter directory names, but not sure it's the best way to filter. Shouldn't we just check for the existence of an 'META-INF' sub-directory? Input would be welcome. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/DeploymentLoader-java-Revision-1416096-TOMEE-613-Extracted-EARs-do-not-deploy-without-META-INF-applie-tp4659113.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: DeploymentLoader.java Revision 1416096 TOMEE-613: Extracted EARs do not deploy without META-INF/application.xml file
Hi, your fix is fine IMO wonder about .git, .hg too (i have to admit i never had such dir in a binary) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/12/5 AndyG andy.gumbre...@orprovision.com: Pretty obvious what's going on here due to changes in DeploymentLoader.java on revision 1416096: UnknownModuleTypeException: Unable to determine module type for jar: file:/[path]/apps/*.svn* I have added some code to filter directory names, but not sure it's the best way to filter. Shouldn't we just check for the existence of an 'META-INF' sub-directory? Input would be welcome. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/DeploymentLoader-java-Revision-1416096-TOMEE-613-Extracted-EARs-do-not-deploy-without-META-INF-applie-tp4659113.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Fwd: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-we
Hi guys, with JL we got as feedback we were missing a real archetype with tomee maven plugin etc configured. i pushed a simple one i commented all the arquillian stuff (to avoid to need to pull it if not used) currently it only contain a servlet, and a beans.xml wonder if 1) we should put some basic persistence (1 entity + 1 persistence.xml + openjpa-maven-plugin to enhance the entity) 2) add a cdi bean and inject it in the servlet 3) add an ejb 4) add a test ... any help on such a topic is welcomed Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau -- Forwarded message -- From: rmannibu...@apache.org Date: 2012/12/5 Subject: svn commit: r1417653 - in /openejb/trunk/openejb/maven: ./ tomee-webapp-archetype/ tomee-webapp-archetype/src/ tomee-webapp-archetype/src/main/ tomee-webapp-archetype/src/main/resources/ tomee-webapp-archetype/src/main/resources/META-INF/ tomee-webapp-... To: comm...@openejb.apache.org Author: rmannibucau Date: Wed Dec 5 21:19:35 2012 New Revision: 1417653 URL: http://svn.apache.org/viewvc?rev=1417653view=rev Log: TOMEE-630 basic maven artifact (to enhance) Added: openejb/trunk/openejb/maven/tomee-webapp-archetype/ openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/META-INF/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/META-INF/archetype.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/pom.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/java/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/java/Index.java openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/beans.xml openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/java/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/resources/ openejb/trunk/openejb/maven/tomee-webapp-archetype/src/main/resources/archetype-resources/src/test/resources/arquillian.xml Modified: openejb/trunk/openejb/maven/pom.xml Modified: openejb/trunk/openejb/maven/pom.xml URL: http://svn.apache.org/viewvc/openejb/trunk/openejb/maven/pom.xml?rev=1417653r1=1417652r2=1417653view=diff == --- openejb/trunk/openejb/maven/pom.xml (original) +++ openejb/trunk/openejb/maven/pom.xml Wed Dec 5 21:19:35 2012 @@ -15,7 +15,6 @@ See the License for the specific language governing permissions and limitations under the License. -- - project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; @@ -41,6 +40,7 @@ modulemaven-util/module modulespi-helper-maven-plugin/module modulespi-helper-jee6-profile/module +moduletomee-webapp-archetype/module /modules dependencyManagement Added: openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml URL: http://svn.apache.org/viewvc/openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml?rev=1417653view=auto == --- openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml (added) +++ openejb/trunk/openejb/maven/tomee-webapp-archetype/pom.xml Wed Dec 5 21:19:35 2012 @@ -0,0 +1,30 @@ +?xml version=1.0 encoding=UTF-8? +!-- +Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses
CMS diff: tomee-and-netbeans.page/
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/tomee-and-netbeans.page%2F Tiklu Ganguly
java:app rules (TOMEE-597)
Moving the discussion to the dev list. Seems there's some confusion on the rules around java:app visibility. From a purely specification and compliance perspective, the basic rule is that java:app is visible to the entire application, universally. No exceptions and no conditions. If it is running *inside* the application, it can do lookups from java:app The confusing part comes in that the same is not true for *declaring* these names. To be specific `@Resource` is effectively only available to Java EE components. So, non-JavaEE components effectively cannot declare names to be added to java:app, nor can they get dependency injection via `@Resource` Easy to get confused. From an implementation perspective, right, Tomcat does not add java:app names. I suspect this, in combination with the above non-intuative rules about declaring vs using java:app names, is the source of the confusion on TOMEE-597. It seems possible Tomcat misinterprets java:app/Foo names and binds them to java:comp/env/app/Foo, in which case we should likely remove the non-portable java:comp/env/app/Foo binding. Effectively, it's a Tomcat bug from not understanding the new java:app namespace. We definitely shouldn't be merging java:comp/env/app/ to java:app/ if we can avoid it. If there is some odd situation in the integration that is causing this idiosyncrasy, we should do our best to eliminate it. -David
Re: java:app rules (TOMEE-597)
Not the whole story, Dont have it in mind exactly but you need both because fron ee tomcat components it is hitten from comp/env and from the rest of the app with the real name (spring for instance to our integration Think we have it too in our integration since we use openejb/resource and in tomcat integ where we merge in comp/env...but works for ee injections What the issue with this rebinding? Le 30 nov. 2012 01:14, David Blevins david.blev...@gmail.com a écrit : Moving the discussion to the dev list. Seems there's some confusion on the rules around java:app visibility. From a purely specification and compliance perspective, the basic rule is that java:app is visible to the entire application, universally. No exceptions and no conditions. If it is running *inside* the application, it can do lookups from java:app The confusing part comes in that the same is not true for *declaring* these names. To be specific `@Resource` is effectively only available to Java EE components. So, non-JavaEE components effectively cannot declare names to be added to java:app, nor can they get dependency injection via `@Resource` Easy to get confused. From an implementation perspective, right, Tomcat does not add java:app names. I suspect this, in combination with the above non-intuative rules about declaring vs using java:app names, is the source of the confusion on TOMEE-597. It seems possible Tomcat misinterprets java:app/Foo names and binds them to java:comp/env/app/Foo, in which case we should likely remove the non-portable java:comp/env/app/Foo binding. Effectively, it's a Tomcat bug from not understanding the new java:app namespace. We definitely shouldn't be merging java:comp/env/app/ to java:app/ if we can avoid it. If there is some odd situation in the integration that is causing this idiosyncrasy, we should do our best to eliminate it. -David
Re: TomEE 1.5.1 release notes preview
On Nov 22, 2012, at 5:53 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: The release notes preview is available here http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html Excellent to see it working! I always have problems getting it to run. Seems I always have to patch something. That script is a little funny -- the versions are hardcoded in the velocity template. We just need to update it for 1.5.1. -David
Re: TomEE 1.5.1 release notes preview
Hi guys... Yeap. I can't run it. Both trunk and branch throw lots of the following exception... at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) java.lang.Exception: Could not load tomee-jaxrs-webapp/target/tomee-jaxrs-webapp-1/5/1-SNAPSHOT/WEB-INF/classes/org/apache/tomee/webapp/servlet/CommandExecutorServlet$1.class at org.apache.openejb.util.AnnotationFinder.readClassDef(AnnotationFinder.java:289) at org.apache.openejb.util.AnnotationFinder.find(AnnotationFinder.java:162) at org.apache.openejb.config.DeploymentLoader.checkAnnotations(DeploymentLoader.java:1539) at org.apache.openejb.config.DeploymentLoader.discoverModuleType(DeploymentLoader.java:1483) Guys, let me know when is a good time to do commits to the trunk. I have tons of code to submit. It is almost time to graduate the new gui. :O) []s, Thiago. On Fri, Nov 23, 2012 at 1:32 PM, David Blevins david.blev...@gmail.comwrote: On Nov 22, 2012, at 5:53 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: The release notes preview is available here http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html Excellent to see it working! I always have problems getting it to run. Seems I always have to patch something. That script is a little funny -- the versions are hardcoded in the velocity template. We just need to update it for 1.5.1. -David
Re: TomEE 1.5.1 release notes preview
Ah... note that the drop-in war works fine. []s, Thiago. On Fri, Nov 23, 2012 at 1:47 PM, Thiago Veronezi thi...@veronezi.orgwrote: Hi guys... Yeap. I can't run it. Both trunk and branch throw lots of the following exception... at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) java.lang.Exception: Could not load tomee-jaxrs-webapp/target/tomee-jaxrs-webapp-1/5/1-SNAPSHOT/WEB-INF/classes/org/apache/tomee/webapp/servlet/CommandExecutorServlet$1.class at org.apache.openejb.util.AnnotationFinder.readClassDef(AnnotationFinder.java:289) at org.apache.openejb.util.AnnotationFinder.find(AnnotationFinder.java:162) at org.apache.openejb.config.DeploymentLoader.checkAnnotations(DeploymentLoader.java:1539) at org.apache.openejb.config.DeploymentLoader.discoverModuleType(DeploymentLoader.java:1483) Guys, let me know when is a good time to do commits to the trunk. I have tons of code to submit. It is almost time to graduate the new gui. :O) []s, Thiago. On Fri, Nov 23, 2012 at 1:32 PM, David Blevins david.blev...@gmail.comwrote: On Nov 22, 2012, at 5:53 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: The release notes preview is available here http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html Excellent to see it working! I always have problems getting it to run. Seems I always have to patch something. That script is a little funny -- the versions are hardcoded in the velocity template. We just need to update it for 1.5.1. -David
Re: TomEE 1.5.1 release notes preview
Thiago, Go ahead, I will re create the branch as soon as OWB 1.1.7 will get released. The first shoot was to try the tooling and the whole process. It also allowed me to review commits and JIRA which is time saved for the real release. It should go faster next time (at least I hope so). Please commit before the end of the weekend if possible. I hope to go through the release again next week at the office. Thanks, Jean-Louis 2012/11/23 Thiago Veronezi thi...@veronezi.org Ah... note that the drop-in war works fine. []s, Thiago. On Fri, Nov 23, 2012 at 1:47 PM, Thiago Veronezi thi...@veronezi.org wrote: Hi guys... Yeap. I can't run it. Both trunk and branch throw lots of the following exception... at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) java.lang.Exception: Could not load tomee-jaxrs-webapp/target/tomee-jaxrs-webapp-1/5/1-SNAPSHOT/WEB-INF/classes/org/apache/tomee/webapp/servlet/CommandExecutorServlet$1.class at org.apache.openejb.util.AnnotationFinder.readClassDef(AnnotationFinder.java:289) at org.apache.openejb.util.AnnotationFinder.find(AnnotationFinder.java:162) at org.apache.openejb.config.DeploymentLoader.checkAnnotations(DeploymentLoader.java:1539) at org.apache.openejb.config.DeploymentLoader.discoverModuleType(DeploymentLoader.java:1483) Guys, let me know when is a good time to do commits to the trunk. I have tons of code to submit. It is almost time to graduate the new gui. :O) []s, Thiago. On Fri, Nov 23, 2012 at 1:32 PM, David Blevins david.blev...@gmail.com wrote: On Nov 22, 2012, at 5:53 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: The release notes preview is available here http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html Excellent to see it working! I always have problems getting it to run. Seems I always have to patch something. That script is a little funny -- the versions are hardcoded in the velocity template. We just need to update it for 1.5.1. -David -- Jean-Louis
CMS diff: Installing TomEE using the drop-in .war approach
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/installation-drop-in-war.mdtext Index: trunk/content/installation-drop-in-war.mdtext === --- trunk/content/installation-drop-in-war.mdtext (revision 1412723) +++ trunk/content/installation-drop-in-war.mdtext (working copy) @@ -24,9 +24,9 @@ - Update $CATALINA_HOME/conf/tomcat-users.xml to add a tomee user to allow access to the console - !-- Activate those lines to get access to TomEE GUI -- - role rolename=tomee-admin / - user username=tomee password=tomee roles=tomee-admin,manager-gui / + lt;!-- Activate those lines to get access to TomEE GUI --gt;br / + lt;role rolename=tomee-admin /gt;br / + lt;user username=tomee password=tomee roles=tomee-admin,manager-gui /gt; - Download the .war file you wish to use - either the tomee-webapp-1.5.0.war (for the webprofile installation) or tomee-webapp-plus-1.5.0.war (for the plus version).
Re: TomEE 1.5.1 release notes preview
Done, Now it is time for the new bugs. :O) Please, fire the bugs as soon as you guys find it. I will try to fix everything as soon as possible. []s, Thiago. On Fri, Nov 23, 2012 at 1:51 PM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Thiago, Go ahead, I will re create the branch as soon as OWB 1.1.7 will get released. The first shoot was to try the tooling and the whole process. It also allowed me to review commits and JIRA which is time saved for the real release. It should go faster next time (at least I hope so). Please commit before the end of the weekend if possible. I hope to go through the release again next week at the office. Thanks, Jean-Louis 2012/11/23 Thiago Veronezi thi...@veronezi.org Ah... note that the drop-in war works fine. []s, Thiago. On Fri, Nov 23, 2012 at 1:47 PM, Thiago Veronezi thi...@veronezi.org wrote: Hi guys... Yeap. I can't run it. Both trunk and branch throw lots of the following exception... at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) java.lang.Exception: Could not load tomee-jaxrs-webapp/target/tomee-jaxrs-webapp-1/5/1-SNAPSHOT/WEB-INF/classes/org/apache/tomee/webapp/servlet/CommandExecutorServlet$1.class at org.apache.openejb.util.AnnotationFinder.readClassDef(AnnotationFinder.java:289) at org.apache.openejb.util.AnnotationFinder.find(AnnotationFinder.java:162) at org.apache.openejb.config.DeploymentLoader.checkAnnotations(DeploymentLoader.java:1539) at org.apache.openejb.config.DeploymentLoader.discoverModuleType(DeploymentLoader.java:1483) Guys, let me know when is a good time to do commits to the trunk. I have tons of code to submit. It is almost time to graduate the new gui. :O) []s, Thiago. On Fri, Nov 23, 2012 at 1:32 PM, David Blevins david.blev...@gmail.com wrote: On Nov 22, 2012, at 5:53 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: The release notes preview is available here http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html Excellent to see it working! I always have problems getting it to run. Seems I always have to patch something. That script is a little funny -- the versions are hardcoded in the velocity template. We just need to update it for 1.5.1. -David -- Jean-Louis
Re: TomEE 1.5.1 release notes preview
Really nice! thank you - Enrico Il 23/11/2012 19:32, David Blevins ha scritto: On Nov 22, 2012, at 5:53 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: The release notes preview is available here http://people.apache.org/~jlmonteiro/releasenotes-1.5.1.html Excellent to see it working! I always have problems getting it to run. Seems I always have to patch something. That script is a little funny -- the versions are hardcoded in the velocity template. We just need to update it for 1.5.1. -David
Re: [DISCUSS] TomEE as the TLP name
Well, the problem is that we would need to pick one package name. Afair the policy so far has been that all packages must be under the TLP name. That was the reason why CODI also has org.apache.myfaces.extension.cdi and not simply org.apache.codi. That was the main reason for proposing two TLPs even if there is lots of overlap. Not sure if this argument is still valid or if we could get an exception from board though... LieGrue, strub - Original Message - From: Jacek Laskowski ja...@japila.pl To: dev@openejb.apache.org Cc: Sent: Sunday, November 18, 2012 10:41 PM Subject: Re: [DISCUSS] TomEE as the TLP name On Tue, Nov 13, 2012 at 4:04 PM, David Blevins david.blev...@gmail.com wrote: What do people think about renaming this TLP from OpenEJB to TomEE? Just to let you know I've read the thread, but still have no idea what the solution should be. TomEE is all over the place and eclipses OpenEJB. On the other hand, there's so little code-wise to say TomEE drives OpenEJB and not vice-versa. As of now, I'm fine with whatever consensus will emerge from the discussion. Jacek -- Jacek Laskowski Functional languages (Clojure), Java EE, and IBM WebSphere - http://blog.japila.pl Never discourage anyone who continually makes progress, no matter how slow. Plato
Re: [DISCUSS] TomEE as the TLP name
On Nov 19, 2012, at 7:49 AM, Mark Struberg strub...@yahoo.de wrote: Afair the policy so far has been that all packages must be under the TLP name. That was the reason why CODI also has org.apache.myfaces.extension.cdi and not simply org.apache.codi. That was the main reason for proposing two TLPs even if there is lots of overlap. Not sure if this argument is still valid or if we could get an exception from board though... It's as much of a rule as we want to make it. Some popular Apache packages that are not TLPs: - org.apache.derby - org.apache.torque - org.apache.yoko - org.apache.xbean - org.apache.woden - org.apache.neethi If you use a clear brand, it's not a problem. If you do org.apache.naming, that's awfully frowned upon. :) If we want to change package names on code we can do that, but there certainly won't be anyone forcing us to do that. -David
Re: [DISCUSS] TomEE as the TLP name
So all is fine? What are we waiting for now? Le 19 nov. 2012 22:39, David Blevins david.blev...@gmail.com a écrit : On Nov 19, 2012, at 7:49 AM, Mark Struberg strub...@yahoo.de wrote: Afair the policy so far has been that all packages must be under the TLP name. That was the reason why CODI also has org.apache.myfaces.extension.cdi and not simply org.apache.codi. That was the main reason for proposing two TLPs even if there is lots of overlap. Not sure if this argument is still valid or if we could get an exception from board though... It's as much of a rule as we want to make it. Some popular Apache packages that are not TLPs: - org.apache.derby - org.apache.torque - org.apache.yoko - org.apache.xbean - org.apache.woden - org.apache.neethi If you use a clear brand, it's not a problem. If you do org.apache.naming, that's awfully frowned upon. :) If we want to change package names on code we can do that, but there certainly won't be anyone forcing us to do that. -David
Re: [DISCUSS] TomEE as the TLP name
At this point we draft up a board resolution to amend our TLP name and description and vote on it. Then we wait till next board meeting till its official. The next board meeting is actually Wednesday morning, so not enough time for a 72 hour vote, but that's ok. We have time. On Monday, November 19, 2012, Romain Manni-Bucau wrote: So all is fine? What are we waiting for now? Le 19 nov. 2012 22:39, David Blevins david.blev...@gmail.comjavascript:; a écrit : On Nov 19, 2012, at 7:49 AM, Mark Struberg strub...@yahoo.dejavascript:; wrote: Afair the policy so far has been that all packages must be under the TLP name. That was the reason why CODI also has org.apache.myfaces.extension.cdi and not simply org.apache.codi. That was the main reason for proposing two TLPs even if there is lots of overlap. Not sure if this argument is still valid or if we could get an exception from board though... It's as much of a rule as we want to make it. Some popular Apache packages that are not TLPs: - org.apache.derby - org.apache.torque - org.apache.yoko - org.apache.xbean - org.apache.woden - org.apache.neethi If you use a clear brand, it's not a problem. If you do org.apache.naming, that's awfully frowned upon. :) If we want to change package names on code we can do that, but there certainly won't be anyone forcing us to do that. -David -- Sent from my iPhone
Re: [DISCUSS] TomEE as the TLP name
If this is really fine then let's go for it! OpenEJB could be a sub project of TomEE with no problems in that case. LieGrue, strub - Original Message - From: Romain Manni-Bucau rmannibu...@gmail.com To: dev@openejb.apache.org Cc: Sent: Monday, November 19, 2012 10:51 PM Subject: Re: [DISCUSS] TomEE as the TLP name So all is fine? What are we waiting for now? Le 19 nov. 2012 22:39, David Blevins david.blev...@gmail.com a écrit : On Nov 19, 2012, at 7:49 AM, Mark Struberg strub...@yahoo.de wrote: Afair the policy so far has been that all packages must be under the TLP name. That was the reason why CODI also has org.apache.myfaces.extension.cdi and not simply org.apache.codi. That was the main reason for proposing two TLPs even if there is lots of overlap. Not sure if this argument is still valid or if we could get an exception from board though... It's as much of a rule as we want to make it. Some popular Apache packages that are not TLPs: - org.apache.derby - org.apache.torque - org.apache.yoko - org.apache.xbean - org.apache.woden - org.apache.neethi If you use a clear brand, it's not a problem. If you do org.apache.naming, that's awfully frowned upon. :) If we want to change package names on code we can do that, but there certainly won't be anyone forcing us to do that. -David
