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: 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
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
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
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
[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: 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
Re: CMS diff: Deploy Tool
Applied. For code snippet I prefer the grey background instead of html blockquote, but anyway, thx for fixing. JLouis 2012/12/28 Danylo Vashchilenko anonym...@apache.org Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openejb.apache.org/deploy-tool.mdtext Danylo Vashchilenko Index: trunk/content/deploy-tool.mdtext === --- trunk/content/deploy-tool.mdtext(revision 1426368) +++ trunk/content/deploy-tool.mdtext(working copy) @@ -1,14 +1,14 @@ Title: Deploy Tool + a name=DeployTool-NAME/a # NAME - openejb deploy - OpenEJB Deploy Tool a name=DeployTool-SYNOPSIS/a # SYNOPSIS -openejb deploy [#options](#options.html) file \[file...\] + openejb deploy [options](#DeployTool-OPTIONS) lt;filegt; \[lt;filegt; ...\] a name=DeployTool-NOTE/a # NOTE @@ -16,37 +16,37 @@ The OpenEJB Deploy tool is an OPTIONAL tool that allows you to deploy into a running server and get feedback as if the app was deployed and how it was -deployed (deploymentIds, jndi names, etc.). +deployed (deploymentIds, jndi names, etc.). It can be used to deploy into an offline server, however in this scenario -it simply copies the archive into the openejb.base/apps directory which is +it simply copies the archive into the deployment directory (by default `openejb.base/apps`) which is something that can be done manually with a simple copy command or drag and drop. The OpenEJB Deploy tool can be executed from any directory as long as -OPENEJB_HOME/bin is in the system PATH. OPENEJB_HOME is the directory +`openejb.home/bin` is in the system PATH. `openejb.home` is the directory where OpenEJB was installed or unpacked. For for the remainder of this document we will assume you unpacked OpenEJB into the directory -C:\openejb-3.0. +`C:\openejb-3.0` under Windows. In Windows, the deploy tool can be executed as follows: -*C:\openejb-3.0 bin\openejb deploy --help* + C:\openejb-3.0 bin\openejb deploy --help In UNIX, Linux, or Mac OS X, the deploy tool can be executed as follows: -\[user@host openejb-3.0](u...@host-openejb-3.0.html)# bin/openejb deploy --help + user@host# bin/openejb deploy --help Depending on your OpenEJB version, you may need to change execution bits to make the scripts executable. You can do this with the following command. -\[user@host openejb-3.0](u...@host-openejb-3.0.html)# chmod 755 bin/openejb + user@host# chmod +x bin/openejb From here on out, it will be assumed that you know how to execute the right openejb script for your operating system and commands will appear in shorthand as show below. -*openejb deploy --help* + openejb deploy --help a name=DeployTool-DESCRIPTION/a @@ -54,51 +54,68 @@ The files passed to the Deploy Tool can be any combination of the following: - - ejb 1.1, 2.0, 2.1 or 3.0 jar - - application client jar - - ear file containing only libraries, ejbs and application clients -- + +* EJB 1.1, 2.0, 2.1, 3.0 or 3.1 jar +* application client jar +* EAR file containing only libraries, EJBs and application clients -- everything else will be ignored. -Archives ending in *.ear* or containing a META-INF/application.xml are -assumed to be ear files. +The type of the files passed is determined as follows: -Archives containing a META-INF/ejb-jar.xml file or any classes annotated -with @Stateless, @Stateful or @MessageDriven, are assumed to be *EJB* -applications. EJB applications older that EJB 3.0 should contain a -complete META-INF/ejb-jar.xml inside the jar, however we do not strictly +* Archives ending in `.ear` or containing a `META-INF/application.xml` are +assumed to be EAR files. +* Archives containing a `META-INF/ejb-jar.xml` file or any classes annotated +with `@Stateless`, `@Stateful` or `@MessageDriven`, are assumed to be *EJB* +applications. EJB applications older that EJB 3.0 should contain a +complete `META-INF/ejb-jar.xml` inside the jar, however we do not strictly enforce that -- the act of it being incomplete makes it an EJB 3.0 application by nature. - -Archives containing a META-INF/application-client.xml or with a -META-INF/MANIFEST.MF containing the Main-Class attribute, are assumed to +* Archives containing a `META-INF/application-client.xml` or with a +`META-INF/MANIFEST.MF` containing the `Main-Class` attribute, are assumed to be *Application Client* archives. a name=DeployTool-OPTIONS/a # OPTIONS +table +tr +td-d, --debug /td +tdIncreases the level of detail on validation errors and +deployment summary./td +/tr -table -trtd-d, --debug /tdtdIncreases the level of detail on validation errors and -deployment summary./td/tr -trtd--dir /tdtdSets the destination directory where the app will be deployed. +trtd--dir /td +tdSets the destination directory where the app will be deployed. The default is
Re: svn commit: r1425700 - /openejb/trunk/sandbox/release-tools/src/main_java_org_apache_openejb_tools_release_cmd_Binaries.java
David?
Are u right?
Le 25 déc. 2012 03:01, dblev...@apache.org a écrit :
Author: dblevins
Date: Tue Dec 25 02:00:46 2012
New Revision: 1425700
URL: http://svn.apache.org/viewvc?rev=1425700view=rev
Log:
Are you actually reading this?
Added:
openejb/trunk/sandbox/release-tools/src/main_java_org_apache_openejb_tools_release_cmd_Binaries.java
(with props)
Added:
openejb/trunk/sandbox/release-tools/src/main_java_org_apache_openejb_tools_release_cmd_Binaries.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/sandbox/release-tools/src/main_java_org_apache_openejb_tools_release_cmd_Binaries.java?rev=1425700view=auto
==
---
openejb/trunk/sandbox/release-tools/src/main_java_org_apache_openejb_tools_release_cmd_Binaries.java
(added)
+++
openejb/trunk/sandbox/release-tools/src/main_java_org_apache_openejb_tools_release_cmd_Binaries.java
Tue Dec 25 02:00:46 2012
@@ -0,0 +1,6 @@
+public class main_java_org_apache_openejb_tools_release_cmd_Binaries {
+
+public static void main(String... s) {
+System.out.println(*pt*);
+}
+}
\ No newline at end of file
Propchange:
openejb/trunk/sandbox/release-tools/src/main_java_org_apache_openejb_tools_release_cmd_Binaries.java
--
svn:eol-style = native
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
Re: [VOTE] Name change resolution
+1 Jean-Louis 2012/12/14 David Blevins david.blev...@gmail.com Discussion concluded some time ago on changing the name of the project to Apache TomEE. The consensus is clear to move ahead with the name change and in the weeks since the discussion, no other views have been expressed, it's time for an official vote. To do this we need a resolution to: a) Rename the TLP from OpenEJB to TomEE and since our official changes[1] give room for going beyond EJB, it would be good to update them to explicitly mention the Java Enterprise Edition: b) enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications Consider the vote for these two items a and b above. The resolution for which will look something like, if not identical to: WHEREAS, the Project Management Committee of the Apache OpenEJB Project has chosen by vote to recommend a change of name to Apache TomEE and revision of its charges to include implementation of the Java Enterprise Edition, and WHEREAS, the Board of Directors is receipt of this and deems it to be in the best interests of the Foundation and consistent with the Foundation's propose; NOW, THEREFORE, BE IT RESOLVED, that the Project Management Committee (PMC), heretofore known as The Apache OpenEJB Project be hereby known as the The Apache TomEE Project, and BE IT FURHER RESOLVED, that the Apache TomEE Project be and hereby is responsible for enterprise application containers and services based on, but not limited to the Enterprise JavaBeans Specification and Java Enterprise Edition Specifications. Let's give this 72 hours to vote, then I'll put it to the board for inclusion in the board meeting on the 19th. They'll likely adjust the legal wording, but not the intent. And, of course, it's never too late for someone to say stop the show. There's a meeting every month. -David [1] http://svn.apache.org/repos/asf/openejb/trunk/graduation-resolution.txt -- 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)
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
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
[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: New staging repo with the latest fix
created new tag uploading new binaries: https://repository.apache.org/content/repositories/orgapacheopenejb-127/ Sent my signing key to a public server Should be finished within one hour (crossing fingers that it's the latest shoot). JLouis 2012/12/9 Romain Manni-Bucau rmannibu...@gmail.com There is no 4.5.1 tag So i guess we need to push it again Le 8 déc. 2012 22:58, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Check the crurent tag Le 8 déc. 2012 20:42, Romain Manni-Bucau rmannibu...@gmail.com a écrit : Are you sure the repo is sync with last commits? Le 8 déc. 2012 19:48, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Good catch Vishwa. My key is already on people.a.o but maybe not in the link. I don't have it with me (referee at a handball match). Back home tomorrow. Will give it a try. Jlouis Le 8 déc. 2012 19:35, Vishwanath Krishnamurthi tovishwan...@gmail.com a écrit : Hi Jean, Maybe because of https://issues.apache.org/jira/browse/INFRA-5459? -Vishwa On Sat, Dec 8, 2012 at 7:03 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi, Just uploaded new binaries in the following staging repo. https://repository.apache.org/content/repositories/orgapacheopenejb-126/ Unfortunately, I cannot close it so you can't see it outside nexus. Don't know why so if someone can help on that area ... I won't have anytime to push new ones. If someone can check that everything is ok and push the vote, that'd be cool. Otherwise, will do that on next Monday. -- Jean-Louis -- Jean-Louis
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
New staging repo with the latest fix
Hi, Just uploaded new binaries in the following staging repo. https://repository.apache.org/content/repositories/orgapacheopenejb-126/ Unfortunately, I cannot close it so you can't see it outside nexus. Don't know why so if someone can help on that area ... I won't have anytime to push new ones. If someone can check that everything is ok and push the vote, that'd be cool. Otherwise, will do that on next Monday. -- Jean-Louis
Re: New staging repo with the latest fix
Check the crurent tag Le 8 déc. 2012 20:42, Romain Manni-Bucau rmannibu...@gmail.com a écrit : Are you sure the repo is sync with last commits? Le 8 déc. 2012 19:48, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Good catch Vishwa. My key is already on people.a.o but maybe not in the link. I don't have it with me (referee at a handball match). Back home tomorrow. Will give it a try. Jlouis Le 8 déc. 2012 19:35, Vishwanath Krishnamurthi tovishwan...@gmail.com a écrit : Hi Jean, Maybe because of https://issues.apache.org/jira/browse/INFRA-5459 ? -Vishwa On Sat, Dec 8, 2012 at 7:03 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi, Just uploaded new binaries in the following staging repo. https://repository.apache.org/content/repositories/orgapacheopenejb-126/ Unfortunately, I cannot close it so you can't see it outside nexus. Don't know why so if someone can help on that area ... I won't have anytime to push new ones. If someone can check that everything is ok and push the vote, that'd be cool. Otherwise, will do that on next Monday. -- Jean-Louis
Re: diff between binaries 1.5.0 and 1.5.1
starting that now. 2012/12/7 David Blevins david.blev...@gmail.com Awesome. Reviewing the LICENSE/NOTICE files will be easy :) -David On Dec 6, 2012, at 8:34 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi, here the diff (size) between 1.5.0 and 1.5.1 (current) branch: apache-tomee 1.5.1 webprofile change: +0.22 MB total : 27.13 MB apache-tomee 1.5.1 jaxrs change: +0.30 MB total : 29.49 MB apache-tomee 1.5.1 plus change: +0.30 MB total : 43.56 MB openejb-standalone 4.5.1 change: +0.10 MB total : 31.76 MB FYI the binaries repo is https://repository.apache.org/content/repositories/orgapacheopenejb-118/ Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau -- 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
DISCUSS - Wait or not OWB 1.1.7
Hi, do we really want to wait OWB 1.1.7? -- Jean-Louis
Re: DISCUSS - Wait or not OWB 1.1.7
+1, what is so important we cannot afford? No idea of when, but our users are waiting for a long time. If we always wait for something, we will never get more frequent releases out. Just my thoughts. I even prefer more frequent releases when necessary that always waiting to have a perfect release (which never occurs actually). JLouis 2012/11/26 Jonathan Gallimore jonathan.gallim...@gmail.com I'm sure you're correct. Out of curiosity, when will OWB 1.1.7 be out and what are the benefits? Cheers Jon Sent from my iPad On 26 Nov 2012, at 22:16, Romain Manni-Bucau rmannibu...@gmail.com wrote: yes *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* 2012/11/26 Jean-Louis MONTEIRO jeano...@gmail.com Hi, do we really want to wait OWB 1.1.7? -- Jean-Louis -- Jean-Louis
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
Re: drop old maven plugins?
Nobody uses it, so +1. Let's remove them. If there is really a need we can restore them. JLouis 2012/11/22 Romain Manni-Bucau rmannibu...@gmail.com Hi, do we drop dd-maven-plugin/ http://svn.apache.org/repos/asf/openejb/trunk/openejb/maven/dd-maven-plugin/ and spi-helper-maven-plugin/ http://svn.apache.org/repos/asf/openejb/trunk/openejb/maven/spi-helper-maven-plugin/ (+ its jee6 profile)? the first one was to help to merge descriptors coming from jee5 apps but not sure it is relevant anymore (and think nobody uses it) the second one was mainly created before scan.xml managed packages. Since it is done it looks quite useless 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* -- Jean-Louis
Re: svn commit: r1412143 - /openejb/trunk/openejb/examples/pom.xml
Hi Jon, No worries. I just removed the movie then if it's no more relevant. Hope i didn't do any mistake, otherwise, shoot and I can restore. Jean-Louis 2012/11/21 Jonathan Gallimore jonathan.gallim...@gmail.com I played around with moviefun as part of an article I'm doing. The new code should build ok, but if you're running into any problems please shout - I'm happy to fix the issues or revert it out. Cheers Jon Sent from my iPad On 21 Nov 2012, at 15:06, jlmonte...@apache.org wrote: Author: jlmonteiro Date: Wed Nov 21 15:06:51 2012 New Revision: 1412143 URL: http://svn.apache.org/viewvc?rev=1412143view=rev Log: Changing moviefun to moviefun-old as per the recent Jon's changes Modified: openejb/trunk/openejb/examples/pom.xml Modified: openejb/trunk/openejb/examples/pom.xml URL: http://svn.apache.org/viewvc/openejb/trunk/openejb/examples/pom.xml?rev=1412143r1=1412142r2=1412143view=diff == --- openejb/trunk/openejb/examples/pom.xml (original) +++ openejb/trunk/openejb/examples/pom.xml Wed Nov 21 15:06:51 2012 @@ -87,7 +87,7 @@ modulembean-auto-registration/module modulemovies-complete-meta/module modulemovies-complete/module -modulemoviefun/module +modulemoviefun-old/module modulemulti-jpa-provider-testing/module modulemultiple-arquillian-adapters/module modulemultiple-tomee-arquillian/module -- Jean-Louis
[STATUS] Release 1.5.1
Hi, Here is a small status about the next release. The JIRA to follow the process is https://issues.apache.org/jira/browse/TOMEE-526 Regarding all steps: - TCK no build for a while. A problem? - Buildbot: CDI Query sample not working - All commits reviewed - Buildbot created for the branche Next steps for today: - publish RAT report preview - close JIRAs and mark them fixed for 1.5.1 - publish release notes preview - publish report of changed binaries - publish report for LICENSE/NOTICE Would be great if you could review all those reports as well. We are waiting OWB which is about pushing a new vote for 1.1.7 we want to include. As soon as OWB is available, I can integrate it and recreate the branch. Additional question: we have bugfixes and improvements but we also have new features, hence the question 1.5.1 or 1.6.0? -- Jean-Louis
Re: svn commit: r1409700 - /openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/resource/activemq/ActiveMQResourceAdapter.java
Thanks you Andy, I will update commit logs. It will also appear in release notes. Thanks JLouis 2012/11/16 AndyG andy.gumbre...@orprovision.com Done. https://issues.apache.org/jira/browse/OPENEJB-1938 Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Re-svn-commit-r1409700-openejb-trunk-openejb-container-openejb-core-src-main-java-org-apache-openejba-tp4658619p4658638.html Sent from the OpenEJB Dev mailing list archive at Nabble.com. -- Jean-Louis
Re: svn commit: r1409700 - /openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/resource/activemq/ActiveMQResourceAdapter.java
Andy,
can you fill a JIRA please?
That's an important information to share on release notes I think.
Jean-Louis
2012/11/15 andygumbre...@apache.org
Author: andygumbrecht
Date: Thu Nov 15 09:06:27 2012
New Revision: 1409700
URL: http://svn.apache.org/viewvc?rev=1409700view=rev
Log:
Now we hold the broker instance it is up to us to 'stop' it ;-)
Modified:
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/resource/activemq/ActiveMQResourceAdapter.java
Modified:
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/resource/activemq/ActiveMQResourceAdapter.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/resource/activemq/ActiveMQResourceAdapter.java?rev=1409700r1=1409699r2=1409700view=diff
==
---
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/resource/activemq/ActiveMQResourceAdapter.java
(original)
+++
openejb/trunk/openejb/container/openejb-core/src/main/java/org/apache/openejb/resource/activemq/ActiveMQResourceAdapter.java
Thu Nov 15 09:06:27 2012
@@ -121,9 +121,9 @@ public class ActiveMQResourceAdapter ext
ActiveMQFactory.setThreadProperties(properties);
try {
-
+//The returned broker should be started, but calling start is
harmless.
+//We do not need to track the instance as the factory takes
care of this.
ActiveMQFactory.createBroker(URI.create(getBrokerXmlConfig())).start();
-//super.start(bootstrapContext);
} catch (Exception e) {
org.apache.openejb.util.Logger.getInstance(LogCategory.OPENEJB_STARTUP,
ActiveMQResourceAdapter.class).getChildLogger(service).fatal(Failed to
start ActiveMQ, e);
} finally {
@@ -191,8 +191,12 @@ public class ActiveMQResourceAdapter ext
final IteratorBrokerService it = brokers.iterator();
while (it.hasNext()) {
+
+final BrokerService bs = it.next();
+
try {
-it.next().waitUntilStopped();
+bs.stop();
+bs.waitUntilStopped();
} catch (Throwable t) {
//Ignore
}
--
Jean-Louis
Re: [DISCUSS] TomEE as the TLP name
Fully agree. TomEE as a TLP and OpenEJB as a subproject is the preferable solution IMHO. JLouis 2012/11/14 Romain Manni-Bucau rmannibu...@gmail.com Hmm, If people on both projects are the same not sure it makes so much sense...and tomee code is really really small and doesnt do enough work to let it be another project IMO (in fact it only does integration so fixes are mainly in openejb) Wdyt? Le 13 nov. 2012 23:45, Mark Struberg strub...@yahoo.de a écrit : What about having 2 TLPs? Actually OpenEJB is still very valuable as own standalone project. So I'd rather go for having TomEE AND OpenEJB as TLPs. It is already pretty much separated from the build structure. LieGrue, strub - Original Message - From: David Blevins david.blev...@gmail.com To: dev@openejb.apache.org dev@openejb.apache.org Cc: Sent: Tuesday, November 13, 2012 4:04 PM Subject: [DISCUSS] TomEE as the TLP name Since it came up in the other thread, good time to officially raise the discussion on how we want to identify ourselves as a TLP. There have been concerns raised on how we identify to the public in terms of our primary identity -- the website says TomEE in letters as big as my hand was one quote. This was many months ago and my feedback then was we're still experimenting and we need time to figure ourselves out. It's been a year since TomEE has been released and officially certified. The popularity is skyrocketing with no signs of slowing. As TomEE eclipses OpenEJB it becomes more and more strange to call the TLP OpenEJB given our website says TomEE all over it and that's all we present at conferences. What do people think about renaming this TLP from OpenEJB to TomEE? -David
Re: JPA 2.0, JUnit, OpenEJB, createEntityManager() - NoInitialContextException
Hi, Arquillian is definitely something you could try, but after we get that issue fixed maybe. We have a great integration with OpenEJB of course but also with TomEE. Anyway, we have a sample in trunk using Eclipselink with OpenEJB. Could you give it a try or provide us with a simple example to reproduce? Thanks, JLouis 2012/11/12 SvRekaaa svre...@gmail.com I have posted our problem in StackOverflow, but haven't got any answer: http://stackoverflow.com/questions/13289994/jpa-2-0-junit-openejb-createentitymanager-noinitialcontextexception Shall I re-post it here, or is this enough? Regards Sveinung Rekaa System developer EVRY Grenland -- View this message in context: http://openejb.979440.n4.nabble.com/JPA-2-0-JUnit-OpenEJB-createEntityManager-NoInitialContextException-tp4658532.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [DISCUSS] - Project name
The discussion thread is pretty accurate actually. Regarding the name, TomEE seems to be definietly the name we wanna keep. But, that bring the question: should OPENEJB be renamed to TomEE as the TLP at Apache? That's the question I guess, and I'm for it. JLouis 2012/11/13 Mohammad Nour El-Din nour.moham...@gmail.com Hi... On Tue, Nov 13, 2012 at 11:34 AM, Alex The Rocker alex.m3...@gmail.com wrote: I agree with Romain : I work in a major software company, about to release products with dependency on Tomcat replaced by TomEE. It would be annoying to change the prerequisite name at the last minute. If the name changes, then please consider a deprecation period during which both TomEE and *whatevernewname* will cohexist. Perfect :) No worries, there is no prior intention to rename, thats why I marked the e-mail thread [DISCUSS] so it is now only for discussing the validity of renaming in general and the name *in case* there is enough consensus to rename Thanks, Alex. On Tue, Nov 13, 2012 at 11:30 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Mohammad, i think TomEE just starts to be a bit known so i don't think we can (should) change this name even if you are right. *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* 2012/11/13 Mohammad Nour El-Din nour.moham...@gmail.com Hi OEJBers 1st of all it was so great to see most of you in ACEU. As a side discussion initiated by David about renaming the project, he can give more details about that here :), I thought it might be the right time to re-discuss the project name, I know we depend on Tomcat right now but I thought it might be better to think about a name that does not tight couple of with Tomcat who knows whats going to change in the future To be honest I don't have a name in mind atm but out of my mind I would start the discussion by suggesting: BeanEE - Which indicates the direction into which the JEE technology is going which is to make things as simple as just writing simple Java Beans Thoughts ? -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: 1.5 Clarification
Hi all, Sorry for the delay, just took some time to update the page. Lemme know if that's clearer. You are also free to edit it (top right button) so that we'll receive your patch to integrate. Jean-Louis 2012/10/10 Neale Rudd ne...@metawerx.net This is good actually: http://tomee.apache.org/tomee-**directory-structure.htmlhttp://tomee.apache.org/tomee-directory-structure.html (but very out of date) Best Regards, Neale - Original Message - From: Neale Rudd ne...@metawerx.net To: dev@openejb.apache.org Sent: Wednesday, October 10, 2012 6:37 PM Subject: Re: 1.5 Clarification Hi David, Do you mean like this? - http://tomee.apache.org/tomee-**1.5.0-release-notes.htmlhttp://tomee.apache.org/tomee-1.5.0-release-notes.html Or do you want all the release notes from the previous releases? Or did you mean something else? Yes that's pretty good, guess I'd like a little more detail in general. eg: http://tomcat.apache.org/**tomcat-7.0-doc/changelog.htmlhttp://tomcat.apache.org/tomcat-7.0-doc/changelog.html The sentences describe why the change was made a little more whereas the tomee ones seem to be a copy of the jira title, so it takes a lot longer to see what and why changed. Also the tomcat one shows change by version number and the final committer (just for fun) Any ideas on how we can improve these to better match what you imagine? - http://tomee.apache.org/**examples-trunk/index.htmlhttp://tomee.apache.org/examples-trunk/index.html These are great examples, but none are bundled with TomEE. I understand they can't be put into a production folder (like Tomcat does) but maybe then can be easily moved into webapps to try things out rather than downloading them. Just an opinion though. I understand you want to keep download size low. - upgrade notes (per revision + per major revision) - very important if used in a production system, I review these personally for every Tomcat subrelease and make changes to our templates as necessary We definitely don't have anything there. Wondering how we could realistically capture that information. Getting something in place and getting people to use it are always difficult initiatives. This would include a simple migration guide from 1.0.x to 1.5.x. ie: if your app runs in 1.0, what is going to break in 1.5? what needs to be changed? what do we need to be aware of? ie: the /openejb app being change to /tomee pre the 1.0 release would be a good example of a major change. Any information available here can be critical for assisting smooth transitions to newer versions, and that means less time supporting people on older revisions. Much easier to say can you try it on 1.5? the migration docs are here: http And more docs :) Yes - I'd definitely start with configuration reference stuff. ie: a description of all non-Tomcat config files and their components - alpha, beta, rc - release strategy (this would have avoided the 1.5.0 win issue) We did have about 3 sets of potential release binaries and another 2-3 sets of preview binaries (not quite ready for voting). I think Tomcat generally follows this pattern, not sure if it's the Apache standard way, but it seems to generate pretty stable releases: - an alpha-release (people start trying out the new version, normal users never download a snapshot) - a beta-release (more heavy testing, because it's about to go live) - a release-candidate (more testing, people have a very last chance to deploy and test at their workplace, or risk missing all the new features for another N months) - release vote (2-3 days or whatever is decided/mandated) - release Then you immediately branch whatever branches you want, such as a 1.5.1 for fixes-only, a 1.6.0 for the next main version. Whether or not Tomcat upgrades go into the 1.5.1 or the 1.6.0 is up to you. Then within 2 months you release 1.6.0. The 1.5.1 would be released in the case of important new fixes or deployment problems (eg: the windows 1.5.0 issue), and never include new features. Something like that? Best Regards, Neale - Original Message - From: David Blevins david.blev...@gmail.com To: dev@openejb.apache.org Sent: Tuesday, October 09, 2012 6:42 AM Subject: Re: 1.5 Clarification On Oct 8, 2012, at 12:15 PM, Neale Rudd wrote: Suggest following Tomcat-style change-log. One file which has all 1.x.x release notes with a one-liner describing the change/feature and a link to Jira if people want to investigate. Do you mean like this? - http://tomee.apache.org/tomee-**1.5.0-release-notes.htmlhttp://tomee.apache.org/tomee-1.5.0-release-notes.html Or do you want all the release notes from the previous releases? Or did you mean something else? - simple examples (helps get people started, helps to demonstrate why TomEE is useful to their company) Any ideas on how we can improve these to better match what you imagine? -
New TomEE web app and next release
Hey guys, As discuss many times, a new release has to be done. Spent time with David yesterday on the release process and all wrapping tools he put around for the project. Then, I started looking how it will be and saw some stuff to fix/clarify regarding the new webapp. Thiago, it looks like you added some stuff that needs to be checked in regards to headers, licensing, etc Could you please do that? I mean, add excludes to rat.xml, add licenses, etc Jean-Louis
Re: Using comments.apache.org for our live docs
+1 with Vishwa 2012/11/8 Vishwanath Krishnamurthi tovishwan...@gmail.com Looks great ! We are slow on adding the changes to the docs and until a change is integrated to the doc, comments section could prove to be useful. -Vishwa On Thu, Nov 8, 2012 at 4:14 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: do we want it too? *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* -- Forwarded message -- From: Rainer Jung rainer.j...@kippdata.de Date: 2012/11/7 Subject: Using comments.apache.org for our live docs To: Tomcat Developers List d...@tomcat.apache.org, Tomcat Users List us...@tomcat.apache.org Cross posting intentionally, because our long time users list supporters might want to comment as well. A few months ago a new Web Server committer, Daniel Gruno, suggested to use a commenting system as part of the online documentation. He wanted to include the disqus system. Some of his fellow committers were not very glad with using an external system for the users comments and he sat down and wrote an ASF commenting system. It is now running as an ASF service under comments.apache.org. It allows users to add comments to documentation pages. Comments without URLs and HTML tags are going live immediately without moderation, the other ones need moderation first. We are using it in the web server project since a few months and we observe close to no spam. Comment activity isn't to high, about 1 comments per day. Some of those are not actually docs comments and they are responded by referring the users to the users list. Some of them are really useful because they help to clarify and improve documentation. In the meantime, the trafficserver project also uses the feature. The comments are not meant to stay forever. Important content should be integrated into the docs. Technically the commenting is done by adding a few lines of html and inline JavaScript to each page, which then calls comments.apache.org. For the Tomcat docs this can be done by adding those items to the XSL stylesheet used to generate the HTML pages. I prepared a simple demo at: http://people.apache.org/~**rjung/tomcat-docs-comments/**tomcat-8.0-docs/ http://people.apache.org/~rjung/tomcat-docs-comments/tomcat-8.0-docs/ It would be nice if you would have a look and we would discuss, whether we find it useful or not. The patch for build.xml and the xsl that I applied to build the comment enabled docs can be found at http://people.apache.org/~**rjung/patches/tc-trunk-**comments.patch http://people.apache.org/~rjung/patches/tc-trunk-comments.patch A final version would include a reference to tomcat.apache.org instead of people.apache.org/... The JavaScript checks the host header in order to disable the feature if the docs are running on a different server, e.g. inside a localhost Tomcat etc. Regards, Rainer --**--**- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.**orgdev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [DISCUSS] New release by the end of October
Nobody seems to be against. AFAIK all is ready so we can start the process. Will give it a first try tomorrow. Jean-Louis 2012/10/27 Jacek Laskowski ja...@japila.pl On Tue, Oct 23, 2012 at 10:59 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: was wandering if we could get a release by the end of this month (October). ... AFAIR, there is no new feature nor improvement, only bug fixes, so a 1.5.1 would be great I guess. Otherwise, we have to push a 1.6.0. I'm for releasing a new version just to have TomEE caught up with Tomcat 7.0.32 as people seem to need it and asked me a few times about the latest Tomcat under the covers. 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] New release by the end of October
No other opinions? Nobody against? JLouis 2012/10/24 Alex The Rocker alex.m3...@gmail.com +1 for a 1.5.1 bug fixes release end of October : fixes to Windows specific issues are available in current snapshot, and that would avoid first timers Windows addicts to run away from TomEE, ihmo Alex On Tue, Oct 23, 2012 at 9:59 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hello, was wandering if we could get a release by the end of this month (October). Would be great cause we have ApacheCon on early November and we could speak about it. There are some painful bugs I would like to get fixed. AFAIR, there is no new feature nor improvement, only bug fixes, so a 1.5.1 would be great I guess. Otherwise, we have to push a 1.6.0. WDYT? The difference is really small between the latest release, so it should be quite easy to check and to deliver. Jean-Louis
[DISCUSS] New release by the end of October
Hello, was wandering if we could get a release by the end of this month (October). Would be great cause we have ApacheCon on early November and we could speak about it. There are some painful bugs I would like to get fixed. AFAIR, there is no new feature nor improvement, only bug fixes, so a 1.5.1 would be great I guess. Otherwise, we have to push a 1.6.0. WDYT? The difference is really small between the latest release, so it should be quite easy to check and to deliver. Jean-Louis
Re: Replacing the current GUI by the JS version
If We can more or less the same I don't see any issue to switch and BTW, I don't see any good reason to maintain both. Jean Louis Le 18 oct. 2012 19:31, Romain Manni-Bucau rmannibu...@gmail.com a écrit : well for me the gui (i didnt put a 's' ;)) is the one matching index.html (BTW we need to add it to welcome list files in web.xml) so +1 *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* 2012/10/18 Thiago Veronezi thi...@veronezi.org Guys, Keeping track of two GUIs wont be an easy task. I was wondering if you guys *agree* on replacing the current GUI by the one I am working on. The new GUI is based on websockets, but the ApplicationModel.js file can manage both type of connections because the connection to the server is hidden from the rest of the application. The new console panel is a pretty good replacement of the current 'EJB', 'Class' and 'Invoke' panels, since we can run any arbitrary server-side script code from it (including ejb lookups). I still need to work on the new 'JNDI' panel. The new 'JNDI' panel would be used as a global view of the JNDI tree, and it would help the users to find jndi lookup strings. So, my proposal for the next steps would be: * improve the ApplicationModel.js in order to use regular XMLHttp calls is the WebSocket object is not available; * create the new JNDI panel * kill the old gui. []s, Thiago.
Fwd: ASF Board Meeting Summary - October 17, 2012
Hum, did not remember it was already time to send a report. If nobody cares I can write sthg and submit it to you pretty soon for validation (or not :)). Jlouis -- Message transféré -- De : Greg Stein gst...@apache.org Date : 18 oct. 2012 10:13 Objet : ASF Board Meeting Summary - October 17, 2012 À : committ...@apache.org The October board meeting took place on the 17th, at 10:30am Pacific time. The following directors were present: Rich Bowen Roy T. Fielding Ross Gardler Brett Porter Sam Ruby Greg Stein Doug was unable to attend, so I stood in (as Vice Chairman) to help run the meeting. The following officers and guests were present: Chris Mattmann Craig L Russell Shane Curcuru Dan Kulp The September board meeting minutes were approved, and have been published. All of the reports the Board received, were approved. The following communities did NOT submit a report, and are expected to submit a report next month: Apache Conference Planning Project Apache ACE Project Apache Avro Project Apache Hadoop Project Apache ODE Project Apache OpenEJB Project Apache Shindig Project Apache Steve Project We had lots of resolutions this month, and they all passed: A. Change the Apache DB Project Chair B. Change the Apache Mahout Project Chair C. Establish the Apache ISIS Project D. Change Officers to Serve at the Direction of the President E. Change to the Apache Xalan Project Chair F. Establish the Apache OpenOffice Project G. Change the Apache Community Development Project Chair H. Establish the Apache Cordova Project Congratulations to our new TLPs! ... and welcome to the Apache family :-) The next Board meeting will be on November 21. (yup, the day before the US Thanksgiving holiday) Cheers, Greg Stein Vice Chairman, ASF
Re: TomEE Logo
Hi, From my understanding Yes. At least I used it. Jlouis Le 17 oct. 2012 18:54, Neale Rudd ne...@metawerx.net a écrit : Hi Guys, Just noticed the use of the paw-print logo in the photo from Jean-Louis' TomEE talk! Can we use this logo on our site now to promote TomEE? Are we all agreeing it's the official logo (for now anyway)? Best Regards, Neale
Re: First TomEE 1.5.0 signup
Awesome Neale. That'd great to read such a good news. Jean-Louis 2012/10/10 Neale Rudd ne...@metawerx.net Hi Guys, Just thought you'd like to know we've just had our first 1.5 customer signup today! Plan selection was Starter (128mb MaxHeap, 64mb MaxPerm, 48mb MaxCodeCache, MySQL 5.5). TomEE started up nice and fast and plugged straight in to our dashboard tools without any problems. After a fresh install it's sitting at: Heap: 54mb allocated, 18-47 in use (changes every minute) Perm: 51mb allocated, 27mb in use CC: 8mb allocated, 1mb in use ... so looks nice and comfortable on the above RAM settings - and this is TomEE Plus. * One thing I noticed was the /tomee webapp still doesn't like DIGEST authentication which means we'd have to disable DIGEST for the Tomcat Manager to use the /tomee webapp. Romain I think we ran into this problem with your test-account as well because we switch everything to DIGEST by default. I'll let you know how it goes :-) Best Regards, Neale Rudd Metawerx Java Hosting
Re: I have a limited number of cycles... to spend on TomEE/OpenEJB
For sure Stephen, go ahead. JLouis 2012/10/10 Stephen Connolly stephen.alan.conno...@gmail.com There are a couple of bits of low hanging fruit and I have a limited (few) number of cycles. I will create issues for anything I think I can make progress and I hope that some committers will help me get the patches I create applied. Thanks -Stephen
Fwd: [VOTE] Release XBean 3.12
FYI and for thoses who can vote. JLouis -- Forwarded message -- From: Guillaume Nodet gno...@gmail.com Date: 2012/10/9 Subject: Re: [VOTE] Release XBean 3.12 To: xbean-...@geronimo.apache.org Cc: dev d...@geronimo.apache.org +1 On Wed, Oct 3, 2012 at 1:47 PM, Guillaume Nodet gno...@gmail.com wrote: I've staged a release of bean at: https://repository.apache.org/content/repositories/orgapachegeronimo-088/ Tag: http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.12/ , revision 1393394 Release notes: ** Bug * [XBEAN-119] - ContextUtil$ReadOnlyBinding#isRelative() always returns false * [XBEAN-121] - Constructor injection doesn't work with constructor argument of type array * [XBEAN-146] - xsd for list elements should be unbounded, not max=1 * [XBEAN-190] - XBeanNamespaceHandler does not close resource input streams ** Improvement * [XBEAN-187] - SVN:IGNORE is missing for beanutils * [XBEAN-200] - be able to use annotationfinder for non runtime retention annotation * [XBEAN-203] - Performance improvement by adding local cache for MultiParentClassLoader#loadClass * [XBEAN-207] - FileArchive doesn't have a way to specify the base package * [XBEAN-208] - DelegatingBundle performance issues * [XBEAN-227] - Add support for Spring 3.1 bean profiles * [XBEAN-228] - Support aries blueprint 1.0 * [XBEAN-229] - Make jexl an optional import on xbean-blueprint Please review and vote: [ ] +1 release xbean 3.12 [ ] -1 do not release -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
Re: tomee on openshift
Hi, We started to have a look at CloudFoundry for the moment. We did a successful proto and make it work easily and in an efficient manner. OpenShift is definitely another candidate and we'd like to also give it a try. If you have some request/hints/ etc Let us know so that it will be easier. JLouis 2012/10/9 slawek s.wojciechow...@gmail.com Hello, Has onyone try to run tomee on openshift cloud? I started tomee success there and easy (servlet, jsp, spring -mvc) applications works fine. But when I deploy application contains ejb or jpa jvm fail. This cloud looks fine, but is it possible to use it with tomee? Best Regards sw - Best Regards sw -- View this message in context: http://openejb.979440.n4.nabble.com/tomee-on-openshift-tp4657935.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: tomee on openshift
Just downloaded it on my Mac to run on a VM but did not got time until now :-( 2012/10/9 dsh daniel.hais...@gmail.com Slightly off-topic: did you as well try micro cloud foundry? Cheers Daniel On Tue, Oct 9, 2012 at 5:32 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi, We started to have a look at CloudFoundry for the moment. We did a successful proto and make it work easily and in an efficient manner. OpenShift is definitely another candidate and we'd like to also give it a try. If you have some request/hints/ etc Let us know so that it will be easier. JLouis 2012/10/9 slawek s.wojciechow...@gmail.com Hello, Has onyone try to run tomee on openshift cloud? I started tomee success there and easy (servlet, jsp, spring -mvc) applications works fine. But when I deploy application contains ejb or jpa jvm fail. This cloud looks fine, but is it possible to use it with tomee? Best Regards sw - Best Regards sw -- View this message in context: http://openejb.979440.n4.nabble.com/tomee-on-openshift-tp4657935.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: 1.5.1?
+1, we have some fixes to deliver. A maintenance release would be great. If we deliver a 1.5.1, we should not include something else that bugfix to avoid side effects for end users. So, if enhancements or new features, it should be a 1.6. Regarding the release date, it would be awesome to deliver it before end of October (ie. before ApacheCon). Romain and I can help or do it. Jean-Louis 2012/10/7 Romain Manni-Bucau rmannibu...@gmail.com Hi all, which date do we target for 1.5.1? since we have a windows issue we should release quickly. That's said i already pushed some change which can be very interesting: 1) cdi injection in servlet for eat works (never said all cdi+ear stuff was working :p) 2) deploying war as normal war even with our Deployer (== arquillian tests use normal classloading and not our old one which was wrong) - this affects ear too :) 3) support of shrinkwrap file which are not in filesystem for embedded arquillian adapter 4) make basic bundle working back with KarafEE Because of 2 i don't know if we should versionned it 1.5.1 or 1.6. wdyt? BTW, JL and I will not be very available next week so if the release needs help i think we should target the 20th. wdyt? does it sound possible for you? any new stuff to push? *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*
Re: Logo contest
Up! No answer? JLouis 2012/9/24 Romain Manni-Bucau rmannibu...@gmail.com +1 we need it for next release! (can be an issue too and can explain the .5 ;)) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* *LinkedIn: http://www.linkedin.com/pub/romain-manni-bucau/43/544/956* 2012/9/24 Jean-Louis MONTEIRO jeano...@gmail.com Any news on that topic? I guess the elapsed time is enough? Could we agree on something? I do not like the actual logo (or no logo). The feather with TomEE on top is just aweful :) Looks like we only have Romain's proposal. How could we proceed? Would be great to get it for the 1.5 release. WDYT? Jean-Louis 2012/6/19 David Blevins david.blev...@gmail.com On Jun 19, 2012, at 1:07 AM, Neale Rudd wrote: That sounds better, we can open it up to the users list then and try to get a lot more involvement. We could easily reach a few thousand people if we threw up a blog post, tweeted and posted it to the Google+ and Facebook pages. Ok so the current 40-day vote is cancelled then. FYI for the future, an official vote has to be a new thread with a [VOTE] prefix in the subject. That said, we don't really need a vote till the end when we decide on the logo. Then we'll want to give it like a week or something. Do you want to run it on the main site or link it into cwiki so I can run it from there? We can use cwiki if we want, you could certain do it either way -- submitting patches is easy. We'll want to get some content up and make sure everyone likes it, then go ahead and make the announcement and get it officially started. -David - Original Message - From: David Blevins david.blev...@gmail.com To: dev@openejb.apache.org Sent: Tuesday, June 19, 2012 6:01 PM Subject: Re: Logo contest On Jun 18, 2012, at 10:40 PM, Neale Rudd wrote: Just wanted to remind everyone the 40 day vote ends 9th of July. So far we've had: - no new submissions - 1 new suggestion on a paw holding on the apache feather (Daniel) - 2 votes for paying money for a design (Thiago, Daniel) - 2 votes for Romain's pawprint design (Romain, me) * let me know if you think any of these are incorrect We never really shifted out of discussion mode into actual execution. If we're going to actually have a logo contest there needs to be an official announcement with along with a page on the website saying how to enter, giving guidelines, showing current entries and saying when it will close. -David
Re: [VOTE] OpenEJB 4.5.0/TomEE 1.5.0 (staging-060)
Hi David, I wrote the announcements and sent them to you but did not get any feedback. WDYT about them? Should I re write new ones? Any feedback would be appreciated. For others, here is the first draft I wrote. http://openejb.staging.apache.org/tomee-1.5.0.html Jean-Louis 2012/10/2 David Blevins david.blev...@gmail.com Ok, vote passes with 10 +1s and no other votes! +1s Jean-Louis Monteiro David Blevins Dain Sundstrom Jeff Genender Romain Manni-Bucau Jonathan Gallimore Alan Cabrera Daniel Haischt Thiago Veronezi Karan Malhi Will push all the binaries. Then we need to wait a bit for the mirrors to sync. We can push announcements tomorrow. -David On Sep 28, 2012, at 2:40 PM, dblev...@apache.org wrote: [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.0/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-060 Binaries Source: http://people.apache.org/~dblevins/staging-060/openejb-4.5.0/ Legal: http://people.apache.org/~dblevins/staging-060/legal/archives.html Vote will be open for 72 hours or as needed.
Re: [VOTE] OpenEJB 4.5.0/TomEE 1.5.0 (staging-060)
Alex, Have a look to http://tomee.apache.org/downloads.html You will find all JIRAs affecting the release. Is that what you are looking for? JLouis 2012/10/8 Alex The Rocker alex.m3...@gmail.com My two cents: could you include a list of topmost known bugs ? as far as I understand (i read users list), there's a big issue specific to Windows operation system that breaks even basic annotation servlet sample. This would help not flooding the lists JIRA with such generic known issues Alex On Mon, Oct 8, 2012 at 10:31 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi David, I wrote the announcements and sent them to you but did not get any feedback. WDYT about them? Should I re write new ones? Any feedback would be appreciated. For others, here is the first draft I wrote. http://openejb.staging.apache.org/tomee-1.5.0.html Jean-Louis 2012/10/2 David Blevins david.blev...@gmail.com Ok, vote passes with 10 +1s and no other votes! +1s Jean-Louis Monteiro David Blevins Dain Sundstrom Jeff Genender Romain Manni-Bucau Jonathan Gallimore Alan Cabrera Daniel Haischt Thiago Veronezi Karan Malhi Will push all the binaries. Then we need to wait a bit for the mirrors to sync. We can push announcements tomorrow. -David On Sep 28, 2012, at 2:40 PM, dblev...@apache.org wrote: [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.0/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-060 Binaries Source: http://people.apache.org/~dblevins/staging-060/openejb-4.5.0/ Legal: http://people.apache.org/~dblevins/staging-060/legal/archives.html Vote will be open for 72 hours or as needed.
Re: [VOTE] OpenEJB 4.5.0/TomEE 1.5.0 (staging-060)
Then, that should be in JIRA https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320version=12323315 All opened/reopened JIRAs are here. Some of them could go to a 1.5.1 or a 1.6.0 JLouis 2012/10/8 Romain Manni-Bucau rmannibu...@gmail.com i think the known issues of the last release is what is asked JL. Kind of pre-next-release report *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* 2012/10/8 Jean-Louis MONTEIRO jeano...@gmail.com Alex, Have a look to http://tomee.apache.org/downloads.html You will find all JIRAs affecting the release. Is that what you are looking for? JLouis 2012/10/8 Alex The Rocker alex.m3...@gmail.com My two cents: could you include a list of topmost known bugs ? as far as I understand (i read users list), there's a big issue specific to Windows operation system that breaks even basic annotation servlet sample. This would help not flooding the lists JIRA with such generic known issues Alex On Mon, Oct 8, 2012 at 10:31 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi David, I wrote the announcements and sent them to you but did not get any feedback. WDYT about them? Should I re write new ones? Any feedback would be appreciated. For others, here is the first draft I wrote. http://openejb.staging.apache.org/tomee-1.5.0.html Jean-Louis 2012/10/2 David Blevins david.blev...@gmail.com Ok, vote passes with 10 +1s and no other votes! +1s Jean-Louis Monteiro David Blevins Dain Sundstrom Jeff Genender Romain Manni-Bucau Jonathan Gallimore Alan Cabrera Daniel Haischt Thiago Veronezi Karan Malhi Will push all the binaries. Then we need to wait a bit for the mirrors to sync. We can push announcements tomorrow. -David On Sep 28, 2012, at 2:40 PM, dblev...@apache.org wrote: [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.0/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-060 Binaries Source: http://people.apache.org/~dblevins/staging-060/openejb-4.5.0/ Legal: http://people.apache.org/~dblevins/staging-060/legal/archives.html Vote will be open for 72 hours or as needed.
[RESULT] Paw-print logo to become official TomEE logo
Hi guys, Following what we decided 4 months ago (more than 40 days). So even if someone else disagree, the paw-print will be used as the official Apache TomEE logo. Jean-Louis 2012/6/4 Romain Manni-Bucau rmannibu...@gmail.com i globally agree even if i would have had it on the 12th. - Romain 2012/6/4 David Blevins david.blev...@gmail.com On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote: If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days) we'll just go with it - pending David's decision of course. All things are project decisions of course. I get one vote like everyone else :) My vote would be for the 40 day logo contest. If we don't do it we'd be passing up a great chance to make some noise, attract some attention and get several people contributing logos to the project which means more people contributing to the project. Would be a shame to miss out on all that buzz and excitement. -David
Re: [RESULT] Paw-print logo to become official TomEE logo
So even if someone else disagree, the paw-print will be used as the official Apache TomEE logo. Sorry, wrong sentence, the good one is: So except if someone disagree, the paw-print will be used as the official Apache TomEE logo. JLouis 2012/10/8 Jean-Louis MONTEIRO jeano...@gmail.com Hi guys, Following what we decided 4 months ago (more than 40 days). So even if someone else disagree, the paw-print will be used as the official Apache TomEE logo. Jean-Louis 2012/6/4 Romain Manni-Bucau rmannibu...@gmail.com i globally agree even if i would have had it on the 12th. - Romain 2012/6/4 David Blevins david.blev...@gmail.com On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote: If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days) we'll just go with it - pending David's decision of course. All things are project decisions of course. I get one vote like everyone else :) My vote would be for the 40 day logo contest. If we don't do it we'd be passing up a great chance to make some noise, attract some attention and get several people contributing logos to the project which means more people contributing to the project. Would be a shame to miss out on all that buzz and excitement. -David
Re: [RESULT] Paw-print logo to become official TomEE logo
Sorry David, but we have been talking about that for months. Some people already voted for the paw-print. Maybe they voted here on the idea to actually close the vote :D That's really important IMO to get something for TomEE. If you think that is important we can push a new VOTE on the list and let it open for 72 hours as usual. but to be honest I don't think at all we'll get more votes. Jean-Louis 2012/10/8 David Blevins david.blev...@gmail.com I think the fact that we're getting votes on a '[RESULTS]' thread is a sign there was no actual vote :) That said, it's pretty clear people like the direction. It would still be great to have an actual logo contest and promote the project with it. I'll be happy to get that started this week. -David On Oct 8, 2012, at 8:19 AM, Jean-Louis MONTEIRO wrote: Hi guys, Following what we decided 4 months ago (more than 40 days). So even if someone else disagree, the paw-print will be used as the official Apache TomEE logo. Jean-Louis 2012/6/4 Romain Manni-Bucau rmannibu...@gmail.com i globally agree even if i would have had it on the 12th. - Romain 2012/6/4 David Blevins david.blev...@gmail.com On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote: If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days) we'll just go with it - pending David's decision of course. All things are project decisions of course. I get one vote like everyone else :) My vote would be for the 40 day logo contest. If we don't do it we'd be passing up a great chance to make some noise, attract some attention and get several people contributing logos to the project which means more people contributing to the project. Would be a shame to miss out on all that buzz and excitement. -David
Re: [VOTE] OpenEJB 4.5.0/TomEE 1.5.0 (staging-060)
Excellente! 2012/10/8 David Blevins david.blev...@gmail.com On Oct 8, 2012, at 1:31 AM, Jean-Louis MONTEIRO wrote: Hi David, I wrote the announcements and sent them to you but did not get any feedback. WDYT about them? Should I re write new ones? Any feedback would be appreciated. For others, here is the first draft I wrote. http://openejb.staging.apache.org/tomee-1.5.0.html Hacked on it some last night along with trying to get the list of jiras generated and on the downloads page http://openejb.staging.apache.org/tomee-1.5.0.html On the JAX-RS certification note, I saw Lance at JavaOne (TCK certification guy). We're good on the JAX-RS front, we just need to refile our paperwork which I did last night. -David
Re: 1.5 Clarification
Yes, 1.5.0 as been officially released and is available on Apache Mirrors as well as on Central Repo. Regarding tomee.apache.org or openejb.apache.org, there were the same as far as I know, but i's not if I understand :D tomee.apache.org was supposed to be just a new domain name pointing to openejb.apache.org Maybe David can give u more insights. JLouis 2012/10/8 Neale Rudd ne...@metawerx.net Also just wanted to check: Has 1.5.0 been officially released yet? We've been offering it for almost for a week now. As far as I know: - 1.5.0 is good on Linux - pending 1.5.1 release to fix windows deployer bug - http://tomee.apache.org/**downloads.htmlhttp://tomee.apache.org/downloads.htmlshows 1.0.0, but http://openejb.apache.org/**downloads.htmlhttp://openejb.apache.org/downloads.htmlshows 1.5.0 as latest release, aren't these the same site? Maybe they should be redirected or auto-synced to remove inconsistencies? Or maybe it's better to 301 one of them (1)? (better for google) Best Regards, Neale (1) 301 Moved Permanently http://www.ietf.org/rfc/**rfc2616.txthttp://www.ietf.org/rfc/rfc2616.txt #footnotesarecool
Re: [jira] [Resolved] (TOMEE-447) Using Handlebars
Great work Thiago! I'm glad to see the new interface. Jlouis Le 6 oct. 2012 19:45, Thiago Veronezi thi...@veronezi.org a écrit : Hi guys! I hope this new way of implementing the UI will help us to bring more help from the community. I re-re-implemented the Console page with this new approach. Basically we can now use handlebars.js (http://handlebarsjs.com/) for our templates. I will move on and re-re-implement :O) the Log page and then I will re-re-implement the JNDI panel using something like http://mbostock.github.com/d3/talk/2016/force-collapsible.html . It is very fancy and I think I will going to have a lot of fun with it. The application also uses websockets communication. We will keep the previous webapp ui version available in case the user access the application with an old browser. wdyt? []s, Thiago. On Sat, Oct 6, 2012 at 1:21 PM, Thiago Veronezi (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/TOMEE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiago Veronezi resolved TOMEE-447. --- Resolution: Fixed Using Handlebars Key: TOMEE-447 URL: https://issues.apache.org/jira/browse/TOMEE-447 Project: TomEE Issue Type: Improvement Affects Versions: 1.5.0 Environment: webapp Reporter: Thiago Veronezi Assignee: Thiago Veronezi Fix For: 1.5.1 Using the handlebars.js framework to make it easier for non-developers to help the implementation of the new interface. It also makes the js code cleaner and more elegant. -- 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
Re: [jira] [Resolved] (TOMEE-447) Using Handlebars
Hi Enrico, No 1.1 version. Due to many changes and improvement We jumped to 1.5. We plan to roll a maintenance release 1.5.1 by end of this month hopefully. Next big release with probably this new UI will be 1.7. Jlouis Le 7 oct. 2012 09:26, Enrico Olivelli eolive...@gmail.com a écrit : Hi Thiago, will this new console be bundled in TomEE 1.1 ? - Enrico Il 06/10/2012 19:45, Thiago Veronezi ha scritto: Hi guys! I hope this new way of implementing the UI will help us to bring more help from the community. I re-re-implemented the Console page with this new approach. Basically we can now use handlebars.js (http://handlebarsjs.com/) for our templates. I will move on and re-re-implement :O) the Log page and then I will re-re-implement the JNDI panel using something like http://mbostock.github.com/d3/**talk/2016/force-**collapsible.htmlhttp://mbostock.github.com/d3/talk/2016/force-collapsible.html. It is very fancy and I think I will going to have a lot of fun with it. The application also uses websockets communication. We will keep the previous webapp ui version available in case the user access the application with an old browser. wdyt? []s, Thiago. On Sat, Oct 6, 2012 at 1:21 PM, Thiago Veronezi (JIRA) j...@apache.org wrote: [ https://issues.apache.org/**jira/browse/TOMEE-447?page=** com.atlassian.jira.plugin.**system.issuetabpanels:all-**tabpanelhttps://issues.apache.org/jira/browse/TOMEE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiago Veronezi resolved TOMEE-447. --**- Resolution: Fixed Using Handlebars Key: TOMEE-447 URL: https://issues.apache.org/**jira/browse/TOMEE-447https://issues.apache.org/jira/browse/TOMEE-447 Project: TomEE Issue Type: Improvement Affects Versions: 1.5.0 Environment: webapp Reporter: Thiago Veronezi Assignee: Thiago Veronezi Fix For: 1.5.1 Using the handlebars.js framework to make it easier for non-developers to help the implementation of the new interface. It also makes the js code cleaner and more elegant. -- 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 http://www.atlassian.com/software/jira
Re: TomEE should be secure by default and/or have profile management tool
Fully agree with all Alex. Maybe you could fill a jira and propose kinda profile or at least sine peace if code. Regarding the doc, That's also an area where you could help. It became simpler with the new website based on Apache cms. Jlouis Le 6 oct. 2012 22:01, Alex The Rocker alex.m3...@gmail.com a écrit : This would be acceptable to postpone this JIRA after 1.5.1 if you could add an Hardening TomEE security item in documentation and list there the steps we have in mind for the profile management tool in a future release. Providing this type of information will give more credits to TomEE as suitable production app server (there are many sites about Tomcat hardening, TomEE can't be weaker than Tomcat :)) Alex On Sat, Oct 6, 2012 at 9:55 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: like i said in the Jira i talked about it so i'm +0.8 (not +1 since the conf is still small) then it will not be in 1.5.1 i think (wouldnt add too much security or something like that so it needs some testing) does it sound reasonable for you? *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* 2012/10/6 Alex The Rocker alex.m3...@gmail.com Okay, i agree with that. So how about a profile management tool to generate a TomEE configuration with minimal surface of attack? Alex On Sat, Oct 6, 2012 at 9:49 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: hmm that's not exactly what i said Alex :p on a project you generally have N (5) developpers using the container to develop (let say with tomee-maven-pugin or WTP or something else...) then when it is about production you have 2-3 people configuring the server then it can be deployed in cluster automatically from the config. So my statement is the config work in dev is the prod one So IMO it should work out of the box in dev then the prod should adapt the conf. That's for instance what we do about datasources: we provide some default datasources to let people use JPA out of the box then in production you configure your real datasource, your pooling etc... Sorry if it was not clear. *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* 2012/10/6 Alex The Rocker alex.m3...@gmail.com Hello, This is to continue the discussion started in users@ list around JIRA improvement item https://issues.apache.org/jira/browse/TOMEE-450 I'm a bit surprised by Romain's statement that TomEE is primarily used by developers : I thought that in real world there are more app servers used to deploy than to develop ; even if since TomEE is new it's not yet the case. Any opinion? Alex
Re: 4.5.1 1.5.1 versions in jira
I would say that 1.5.1 and 4.5.1 are for maintenance (patches mainly from the 4.5.x/1.5.x branches). If we wanna add new features, the best versioning IMHO is 1.6.0 and 4.6.0. JLouis 2012/9/30 Romain Manni-Bucau rmannibu...@gmail.com Hi, just created next versions in jira project so we can start hacking on next features ;) *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*
Re: 4.5.1 1.5.1 versions in jira
+1 then Le 1 oct. 2012 08:30, Romain Manni-Bucau rmannibu...@gmail.com a écrit : that's why i created x.5.1 :p we have a stupid windows issue and since we can't fix the OS we have to re-release soon. i don't want the same kind of issue as for last release where ejb injections didn't work in jsf managed beans. Branching now is too early and we'll need to merge all fixes (was the cause for this release) so just let do a maintenance release soon and then add features (well if some new features are in the release that's not an issue but the main purpose will be the fix even if it is the less important in line number) *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* 2012/10/1 Jean-Louis MONTEIRO jeano...@gmail.com I would say that 1.5.1 and 4.5.1 are for maintenance (patches mainly from the 4.5.x/1.5.x branches). If we wanna add new features, the best versioning IMHO is 1.6.0 and 4.6.0. JLouis 2012/9/30 Romain Manni-Bucau rmannibu...@gmail.com Hi, just created next versions in jira project so we can start hacking on next features ;) *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*
Re: [VOTE] OpenEJB 4.5.0/TomEE 1.5.0 (staging-060)
Agree. Here is my +1 JLouis 2012/9/28 dblev...@apache.org [generated email] SVN Tag: https://svn.apache.org/repos/asf/openejb/tags/openejb-4.5.0/ Maven Repo: https://repository.apache.org/content/repositories/orgapacheopenejb-060 Binaries Source: http://people.apache.org/~dblevins/staging-060/openejb-4.5.0/ Legal: http://people.apache.org/~dblevins/staging-060/legal/archives.html Vote will be open for 72 hours or as needed.
ApacheCon EU meet up / Annual Get Together in Germany
Hi all, Just to figure out how we could organize the venue to ApacheCon EU. First question: who finally comes? and when? In other words, how many are we? ApacheCon is from 5th to 8th of November. David and Mark have to leave on Wednesday and Thursday. David's proposal was We could move the fun over to Munich and continue our get-together there and use the subsequent weekend for hacking and touring. I'm open to any other proposal as I don't have any constraints. It time to start looking to hotels for ApacheCon, hotels where we wanna meet up if not in the same place. Moreover, our (Romain and I) company needs to buy also train and flight tickets or to rent a car if needed, so we can't wait until the last week of October. I plan to arrive on Saturday, 3rd or Sunday, 4th of November and the departure is planned on Sunday, 12th of November. Jean-Louis
Re: diff between 1.0.0 and 1.5.0
Great work Romain. Jean-Louis 2012/9/24 Romain Manni-Bucau rmannibu...@gmail.com with some exclusions on AMQ + avoiding to use asm because of owb/openjpa we get (waiting buildbot to valid some AMQ exclusions): apache-tomee 1.5.0 webprofile D jaxb-impl-2.2.5.jar [1105.271 ko] D kahadb-5.5.1.jar [154.609 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D scannotation-1.0.2.jar [18.47 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jdbc-1.5.0.jar [14.81 ko] A tomee-mojarra-1.5.0.jar [12.27 ko] change: -0,45 MB total : 26,89 MB apache-tomee 1.5.0 plus D activeio-core-3.1.2.jar [102.631 ko] D aopalliance-1.0.jar [4.4675 ko] D jaxb-impl-2.2.5.jar [1105.271 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D org.osgi.core-4.2.0.jar [246.924 ko] D scannotation-1.0.2.jar [18.47 ko] A cxf-api-2.6.2.jar [992.498 ko] A cxf-rt-bindings-soap-2.6.2.jar [190.095 ko] A cxf-rt-bindings-xml-2.6.2.jar [38.1110004 ko] A cxf-rt-core-2.6.2.jar [356.149 ko] A cxf-rt-databinding-jaxb-2.6.2.jar [108.396 ko] A cxf-rt-frontend-jaxrs-2.6.2.jar [504.16 ko] A cxf-rt-frontend-jaxws-2.6.2.jar [364.712 ko] A cxf-rt-frontend-simple-2.6.2.jar [63.537 ko] A cxf-rt-rs-extension-providers-2.6.2.jar [69.256 ko] A cxf-rt-rs-extension-search-2.6.2.jar [56.772 ko] A cxf-rt-rs-security-cors-2.6.2.jar [16.81 ko] A cxf-rt-rs-security-oauth2-2.6.2.jar [84.346 ko] A cxf-rt-transports-http-2.6.2.jar [218.688002 ko] A cxf-rt-ws-addr-2.6.2.jar [77.112 ko] A cxf-rt-ws-policy-2.6.2.jar [198.485 ko] A cxf-rt-ws-security-2.6.2.jar [612.462 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jaxrs-1.5.0.jar [16.758 ko] A tomee-jdbc-1.5.0.jar [14.81 ko] A tomee-mojarra-1.5.0.jar [12.27 ko] change: -1,77 MB total : 43,22 MB openejb-standalone 4.5.0 D activeio-core-3.1.2.jar [102.631 ko] D geronimo-j2ee-management_1.1_spec-1.0.1.jar [20.22 ko] D jettison-1.3.1.jar [75.963001 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D scannotation-1.0.2.jar [18.47 ko] D stax-api-1.0-2.jar [23.346 ko] A cxf-api-2.6.2.jar [992.498 ko] A cxf-rt-bindings-soap-2.6.2.jar [190.095 ko] A cxf-rt-bindings-xml-2.6.2.jar [38.1110004 ko] A cxf-rt-core-2.6.2.jar [356.149 ko] A cxf-rt-databinding-jaxb-2.6.2.jar [108.396 ko] A cxf-rt-frontend-jaxws-2.6.2.jar [364.712 ko] A cxf-rt-frontend-simple-2.6.2.jar [63.537 ko] A cxf-rt-transports-http-2.6.2.jar [218.688002 ko] A cxf-rt-ws-addr-2.6.2.jar [77.112 ko] A cxf-rt-ws-policy-2.6.2.jar [198.485 ko] A cxf-rt-ws-security-2.6.2.jar [612.462 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] change: -1,51 MB total : 31,66 MB *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* 2012/9/24 Romain Manni-Bucau rmannibu...@gmail.com here the resul of CompareLibrariries (compare tomee and openejb-standalone binaries): apache-tomee 1.5.0 webprofile D jaxb-impl-2.2.5.jar [1105.271 ko] D kahadb-5.5.1.jar [154.609 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D openjpa-asm-shaded-2.2.0.jar [4571.60505 ko] D scannotation-1.0.2.jar [18.47 ko] A asm-3.3.1.jar [43.581 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openjpa-2.2.0.jar [4616.782 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jdbc-1.5.0.jar [14.8090001 ko] A tomee-mojarra-1.5.0.jar [12.333 ko] change: -0,40 MB total : 26,95 MB apache-tomee 1.5.0 plus D activeio-core-3.1.2.jar [102.631 ko] D aopalliance-1.0.jar [4.4675 ko] D jaxb-impl-2.2.5.jar [1105.271 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D openjpa-asm-shaded-2.2.0.jar [4571.60505 ko] D org.osgi.core-4.2.0.jar [246.924 ko] D scannotation-1.0.2.jar [18.47 ko] A asm-3.3.1.jar [43.581 ko] A cxf-api-2.6.2.jar [992.498 ko] A cxf-rt-bindings-soap-2.6.2.jar [190.095 ko] A cxf-rt-bindings-xml-2.6.2.jar [38.1110004 ko] A cxf-rt-core-2.6.2.jar [356.149 ko] A
TomEE 1.5.0 release: tasks
Hi, Just to give you some details about next steps for me. Following the following JIRA https://issues.apache.org/jira/browse/TOMEE-283 I plan to work on: - running RAT and fix - running license/notice tools and fix Jean-Louis
Legal (license/notice) for a first check
http://people.apache.org/~jlmonteiro/staging-001/legal/archives.html Jean-Louis 2012/9/24 Romain Manni-Bucau rmannibu...@gmail.com with some exclusions on AMQ + avoiding to use asm because of owb/openjpa we get (waiting buildbot to valid some AMQ exclusions): apache-tomee 1.5.0 webprofile D jaxb-impl-2.2.5.jar [1105.271 ko] D kahadb-5.5.1.jar [154.609 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D scannotation-1.0.2.jar [18.47 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jdbc-1.5.0.jar [14.81 ko] A tomee-mojarra-1.5.0.jar [12.27 ko] change: -0,45 MB total : 26,89 MB apache-tomee 1.5.0 plus D activeio-core-3.1.2.jar [102.631 ko] D aopalliance-1.0.jar [4.4675 ko] D jaxb-impl-2.2.5.jar [1105.271 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D org.osgi.core-4.2.0.jar [246.924 ko] D scannotation-1.0.2.jar [18.47 ko] A cxf-api-2.6.2.jar [992.498 ko] A cxf-rt-bindings-soap-2.6.2.jar [190.095 ko] A cxf-rt-bindings-xml-2.6.2.jar [38.1110004 ko] A cxf-rt-core-2.6.2.jar [356.149 ko] A cxf-rt-databinding-jaxb-2.6.2.jar [108.396 ko] A cxf-rt-frontend-jaxrs-2.6.2.jar [504.16 ko] A cxf-rt-frontend-jaxws-2.6.2.jar [364.712 ko] A cxf-rt-frontend-simple-2.6.2.jar [63.537 ko] A cxf-rt-rs-extension-providers-2.6.2.jar [69.256 ko] A cxf-rt-rs-extension-search-2.6.2.jar [56.772 ko] A cxf-rt-rs-security-cors-2.6.2.jar [16.81 ko] A cxf-rt-rs-security-oauth2-2.6.2.jar [84.346 ko] A cxf-rt-transports-http-2.6.2.jar [218.688002 ko] A cxf-rt-ws-addr-2.6.2.jar [77.112 ko] A cxf-rt-ws-policy-2.6.2.jar [198.485 ko] A cxf-rt-ws-security-2.6.2.jar [612.462 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jaxrs-1.5.0.jar [16.758 ko] A tomee-jdbc-1.5.0.jar [14.81 ko] A tomee-mojarra-1.5.0.jar [12.27 ko] change: -1,77 MB total : 43,22 MB openejb-standalone 4.5.0 D activeio-core-3.1.2.jar [102.631 ko] D geronimo-j2ee-management_1.1_spec-1.0.1.jar [20.22 ko] D jettison-1.3.1.jar [75.963001 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D scannotation-1.0.2.jar [18.47 ko] D stax-api-1.0-2.jar [23.346 ko] A cxf-api-2.6.2.jar [992.498 ko] A cxf-rt-bindings-soap-2.6.2.jar [190.095 ko] A cxf-rt-bindings-xml-2.6.2.jar [38.1110004 ko] A cxf-rt-core-2.6.2.jar [356.149 ko] A cxf-rt-databinding-jaxb-2.6.2.jar [108.396 ko] A cxf-rt-frontend-jaxws-2.6.2.jar [364.712 ko] A cxf-rt-frontend-simple-2.6.2.jar [63.537 ko] A cxf-rt-transports-http-2.6.2.jar [218.688002 ko] A cxf-rt-ws-addr-2.6.2.jar [77.112 ko] A cxf-rt-ws-policy-2.6.2.jar [198.485 ko] A cxf-rt-ws-security-2.6.2.jar [612.462 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] change: -1,51 MB total : 31,66 MB *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* 2012/9/24 Romain Manni-Bucau rmannibu...@gmail.com here the resul of CompareLibrariries (compare tomee and openejb-standalone binaries): apache-tomee 1.5.0 webprofile D jaxb-impl-2.2.5.jar [1105.271 ko] D kahadb-5.5.1.jar [154.609 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D openjpa-asm-shaded-2.2.0.jar [4571.60505 ko] D scannotation-1.0.2.jar [18.47 ko] A asm-3.3.1.jar [43.581 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openjpa-2.2.0.jar [4616.782 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jdbc-1.5.0.jar [14.8090001 ko] A tomee-mojarra-1.5.0.jar [12.333 ko] change: -0,40 MB total : 26,95 MB apache-tomee 1.5.0 plus D activeio-core-3.1.2.jar [102.631 ko] D aopalliance-1.0.jar [4.4675 ko] D jaxb-impl-2.2.5.jar [1105.271 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D openjpa-asm-shaded-2.2.0.jar [4571.60505 ko] D org.osgi.core-4.2.0.jar [246.924 ko] D scannotation-1.0.2.jar [18.47 ko] A asm-3.3.1.jar [43.581 ko] A cxf-api-2.6.2.jar [992.498 ko] A cxf-rt-bindings-soap-2.6.2.jar [190.095 ko] A cxf-rt-bindings-xml-2.6.2.jar
Re: Legal (license/notice) for a first check
Lemme me arrive at home and I gonna fix that and check everything. Le 25 sept. 2012 18:07, David Blevins david.blev...@gmail.com a écrit : Thanks, Jean-Louis! Still looking, but at first glance the openejb-provisionning-4.5.0 zip seems to be missing the LICENSE file. -David On Sep 25, 2012, at 11:02 AM, Jean-Louis MONTEIRO wrote: http://people.apache.org/~jlmonteiro/staging-001/legal/archives.html Jean-Louis 2012/9/24 Romain Manni-Bucau rmannibu...@gmail.com with some exclusions on AMQ + avoiding to use asm because of owb/openjpa we get (waiting buildbot to valid some AMQ exclusions): apache-tomee 1.5.0 webprofile D jaxb-impl-2.2.5.jar [1105.271 ko] D kahadb-5.5.1.jar [154.609 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D scannotation-1.0.2.jar [18.47 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jdbc-1.5.0.jar [14.81 ko] A tomee-mojarra-1.5.0.jar [12.27 ko] change: -0,45 MB total : 26,89 MB apache-tomee 1.5.0 plus D activeio-core-3.1.2.jar [102.631 ko] D aopalliance-1.0.jar [4.4675 ko] D jaxb-impl-2.2.5.jar [1105.271 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D org.osgi.core-4.2.0.jar [246.924 ko] D scannotation-1.0.2.jar [18.47 ko] A cxf-api-2.6.2.jar [992.498 ko] A cxf-rt-bindings-soap-2.6.2.jar [190.095 ko] A cxf-rt-bindings-xml-2.6.2.jar [38.1110004 ko] A cxf-rt-core-2.6.2.jar [356.149 ko] A cxf-rt-databinding-jaxb-2.6.2.jar [108.396 ko] A cxf-rt-frontend-jaxrs-2.6.2.jar [504.16 ko] A cxf-rt-frontend-jaxws-2.6.2.jar [364.712 ko] A cxf-rt-frontend-simple-2.6.2.jar [63.537 ko] A cxf-rt-rs-extension-providers-2.6.2.jar [69.256 ko] A cxf-rt-rs-extension-search-2.6.2.jar [56.772 ko] A cxf-rt-rs-security-cors-2.6.2.jar [16.81 ko] A cxf-rt-rs-security-oauth2-2.6.2.jar [84.346 ko] A cxf-rt-transports-http-2.6.2.jar [218.688002 ko] A cxf-rt-ws-addr-2.6.2.jar [77.112 ko] A cxf-rt-ws-policy-2.6.2.jar [198.485 ko] A cxf-rt-ws-security-2.6.2.jar [612.462 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jaxrs-1.5.0.jar [16.758 ko] A tomee-jdbc-1.5.0.jar [14.81 ko] A tomee-mojarra-1.5.0.jar [12.27 ko] change: -1,77 MB total : 43,22 MB openejb-standalone 4.5.0 D activeio-core-3.1.2.jar [102.631 ko] D geronimo-j2ee-management_1.1_spec-1.0.1.jar [20.22 ko] D jettison-1.3.1.jar [75.963001 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D scannotation-1.0.2.jar [18.47 ko] D stax-api-1.0-2.jar [23.346 ko] A cxf-api-2.6.2.jar [992.498 ko] A cxf-rt-bindings-soap-2.6.2.jar [190.095 ko] A cxf-rt-bindings-xml-2.6.2.jar [38.1110004 ko] A cxf-rt-core-2.6.2.jar [356.149 ko] A cxf-rt-databinding-jaxb-2.6.2.jar [108.396 ko] A cxf-rt-frontend-jaxws-2.6.2.jar [364.712 ko] A cxf-rt-frontend-simple-2.6.2.jar [63.537 ko] A cxf-rt-transports-http-2.6.2.jar [218.688002 ko] A cxf-rt-ws-addr-2.6.2.jar [77.112 ko] A cxf-rt-ws-policy-2.6.2.jar [198.485 ko] A cxf-rt-ws-security-2.6.2.jar [612.462 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] change: -1,51 MB total : 31,66 MB *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* 2012/9/24 Romain Manni-Bucau rmannibu...@gmail.com here the resul of CompareLibrariries (compare tomee and openejb-standalone binaries): apache-tomee 1.5.0 webprofile D jaxb-impl-2.2.5.jar [1105.271 ko] D kahadb-5.5.1.jar [154.609 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D openejb-openwebbeans-jsf-1.1.4.jar [23.102 ko] D openjpa-asm-shaded-2.2.0.jar [4571.60505 ko] D scannotation-1.0.2.jar [18.47 ko] A asm-3.3.1.jar [43.581 ko] A jansi-1.8.jar [111.638 ko] A openejb-jpa-integration-4.5.0.jar [19.387 ko] A openjpa-2.2.0.jar [4616.782 ko] A openwebbeans-jsf-1.1.6-20120924.005131-13.jar [20.198 ko] A tomee-jdbc-1.5.0.jar [14.8090001 ko] A tomee-mojarra-1.5.0.jar [12.333 ko] change: -0,40 MB total : 26,95 MB apache-tomee 1.5.0 plus D activeio-core-3.1.2.jar [102.631 ko] D aopalliance-1.0.jar [4.4675 ko] D jaxb-impl-2.2.5.jar [1105.271 ko] D openejb-cxf-bundle-2.5.2.jar [5881.267 ko] D openejb-javaagent-4.0.0.jar [13.081 ko] D openejb-jsf-4.0.0.jar [14.493 ko] D
Re: Legal (license/notice) for a first check
Done. Thx Romain Le 25 sept. 2012 18:26, David Blevins david.blev...@gmail.com a écrit : On Sep 25, 2012, at 11:02 AM, Jean-Louis MONTEIRO wrote: openejb-standalone 4.5.0 A jansi-1.8.jar [111.638 ko] Missing the JANSI entry for the standalone NOTICE file, but other than that everything looked good with TomEE WebProfile, TomEE Plus and OpenEJB Standalone. Still need to look over the JAXRS distro. -David
Re: Logo contest
Any news on that topic? I guess the elapsed time is enough? Could we agree on something? I do not like the actual logo (or no logo). The feather with TomEE on top is just aweful :) Looks like we only have Romain's proposal. How could we proceed? Would be great to get it for the 1.5 release. WDYT? Jean-Louis 2012/6/19 David Blevins david.blev...@gmail.com On Jun 19, 2012, at 1:07 AM, Neale Rudd wrote: That sounds better, we can open it up to the users list then and try to get a lot more involvement. We could easily reach a few thousand people if we threw up a blog post, tweeted and posted it to the Google+ and Facebook pages. Ok so the current 40-day vote is cancelled then. FYI for the future, an official vote has to be a new thread with a [VOTE] prefix in the subject. That said, we don't really need a vote till the end when we decide on the logo. Then we'll want to give it like a week or something. Do you want to run it on the main site or link it into cwiki so I can run it from there? We can use cwiki if we want, you could certain do it either way -- submitting patches is easy. We'll want to get some content up and make sure everyone likes it, then go ahead and make the announcement and get it officially started. -David - Original Message - From: David Blevins david.blev...@gmail.com To: dev@openejb.apache.org Sent: Tuesday, June 19, 2012 6:01 PM Subject: Re: Logo contest On Jun 18, 2012, at 10:40 PM, Neale Rudd wrote: Just wanted to remind everyone the 40 day vote ends 9th of July. So far we've had: - no new submissions - 1 new suggestion on a paw holding on the apache feather (Daniel) - 2 votes for paying money for a design (Thiago, Daniel) - 2 votes for Romain's pawprint design (Romain, me) * let me know if you think any of these are incorrect We never really shifted out of discussion mode into actual execution. If we're going to actually have a logo contest there needs to be an official announcement with along with a page on the website saying how to enter, giving guidelines, showing current entries and saying when it will close. -David
Please VOTE: ConFoo submits
Hi all, Just submitted with Romain 3 talks to the next ConFoo conference. FYI, here is a translation of the 3 presentations 1. Apache TomEE, from development to production 2. Apache KarafEE, when Java EE meets OSGi world 3. Arquillian, when writing tests become a pleasure Thanks in advance for voting. Jean-Louis and Romain
Re: TomEE Jira clean up
Created a component TomEE Maven plugin and affecting related issues to it. Reviewed and changed all types to better define improvements, bugs, new features, dependency update, etc Adding link, duplicates, etc Removed 2 not relevant issues Some labels or summary would need to be rephrased or updated to be clearer but, it's already a long task to review everything, then I will now focus on OpenEJB and go back again if I get time before the release. Hope to not break something, nor do errors. And sorry for the SPAM ;-) Guess I can also close that one https://issues.apache.org/jira/browse/TOMEE-335 ;-) Nothing else assigned to me :D Jean-Louis 2012/9/20 Romain Manni-Bucau rmannibu...@gmail.com could be nice to get a maven plugin project no? *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/20 Jean-Louis MONTEIRO jeano...@gmail.com Hello, just to keep you informed that I prepared TomEE jira project for the next release. Done - remove 1.0.1 version as most people are running on trunk because of important fixes. If necessary, we can create it again, merge necessary fixes and release. Let's proceed if there is a demand. All fixes marked to that release have been switched to 1.5.0 - renamed 1.1.0 to 1.5.0 - go thought all Jiras and review/adapt fixVersion and affectedVersion Todo - There is still 81 issues with no affectedVersion nor fixVersion. Would be great if anyone could have a look and check if some issues are fixed or should be fixed for 1.5.0. The Jira query to get them is : project = TOMEE AND status not in (Closed, Resolved) ORDER BY key DESC, priority DESC - there are 170 issues marked as fixed for 1.5.0 to review and to rephrase if necessary. Will try to do that today. For now, I noticed some significant changes: - JAX-RS distribution (David checking what can be do with certification) - Multiple data source implementations supported out of the box - Multiple JPA providers supported out of the box (dynamic webapp lib enhancer) - Arquillian rework and re-engineering to get a full support - EAR support And some bonus: - Performances enhancements (scanning) - TomEE Maven plugin greatly improved (would need a release as well) - clustering remote deployment support Next step for me: have a look to OpenEJB as well. Jean-Louis
Re: TomEE Jira clean up
FYI, the release notes are available here https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320version=12321654 JLouis 2012/9/20 Jean-Louis MONTEIRO jeano...@gmail.com Created a component TomEE Maven plugin and affecting related issues to it. Reviewed and changed all types to better define improvements, bugs, new features, dependency update, etc Adding link, duplicates, etc Removed 2 not relevant issues Some labels or summary would need to be rephrased or updated to be clearer but, it's already a long task to review everything, then I will now focus on OpenEJB and go back again if I get time before the release. Hope to not break something, nor do errors. And sorry for the SPAM ;-) Guess I can also close that one https://issues.apache.org/jira/browse/TOMEE-335 ;-) Nothing else assigned to me :D Jean-Louis 2012/9/20 Romain Manni-Bucau rmannibu...@gmail.com could be nice to get a maven plugin project no? *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/20 Jean-Louis MONTEIRO jeano...@gmail.com Hello, just to keep you informed that I prepared TomEE jira project for the next release. Done - remove 1.0.1 version as most people are running on trunk because of important fixes. If necessary, we can create it again, merge necessary fixes and release. Let's proceed if there is a demand. All fixes marked to that release have been switched to 1.5.0 - renamed 1.1.0 to 1.5.0 - go thought all Jiras and review/adapt fixVersion and affectedVersion Todo - There is still 81 issues with no affectedVersion nor fixVersion. Would be great if anyone could have a look and check if some issues are fixed or should be fixed for 1.5.0. The Jira query to get them is : project = TOMEE AND status not in (Closed, Resolved) ORDER BY key DESC, priority DESC - there are 170 issues marked as fixed for 1.5.0 to review and to rephrase if necessary. Will try to do that today. For now, I noticed some significant changes: - JAX-RS distribution (David checking what can be do with certification) - Multiple data source implementations supported out of the box - Multiple JPA providers supported out of the box (dynamic webapp lib enhancer) - Arquillian rework and re-engineering to get a full support - EAR support And some bonus: - Performances enhancements (scanning) - TomEE Maven plugin greatly improved (would need a release as well) - clustering remote deployment support Next step for me: have a look to OpenEJB as well. Jean-Louis
OpenEJB Jira clean up
Hello again, Just did the same with OpenEJB, unfortunately was not able to close as some Jira are not so clear for me. I noticed there are 228 issues marked as resolved but not closed. Would like to bulk close all them because they are no more relevant I guess. To not forget something in the release notes, maybe I can have a look to issues closed after the 4.0.0 release and mark them fixed for 4.5.0. For others, I can say if they are relevant to be displayed in release notes. If we agree on that, I can then bulk close all resolved issues. Any thoughts are welcome. Jean-Louis
[QUESTION] Next release number?
Hello guys, Was looking to release notes and all the work we did since last release 1.0.0. I was wondering if we could jump to a 1.5.0? IMHO, the gap between both is really big (large improvements, classloading changes, ear support, lot of bugfixes, and lot of new features) and require also a gap in versioning. Moreover, I think it's great for the community and for external users to reflect all those changes in the version number. Thoughts? Anyone against the idea? Happy to discuss furthermore if needed. Jean-Louis
Re: svn commit: r1384123 - in /openejb/trunk/openejb: pom.xml tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/OpenEJBContextConfig.java
No ... Just don't forget to fill a JIRA for OWB update ;-)
2012/9/12 Romain Manni-Bucau rmannibu...@gmail.com
sorry i updated OWB in the same commit (// taks + some network latency :s)
is it an issue for anyone?
*Romain Manni-Bucau*
*Twitter: @rmannibucau*
*Blog: http://rmannibucau.wordpress.com*
-- Forwarded message --
From: rmannibu...@apache.org
Date: 2012/9/12
Subject: svn commit: r1384123 - in /openejb/trunk/openejb: pom.xml
tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/OpenEJBContextConfig.java
To: comm...@openejb.apache.org
Author: rmannibucau
Date: Wed Sep 12 21:01:26 2012
New Revision: 1384123
URL: http://svn.apache.org/viewvc?rev=1384123view=rev
Log:
tomcat 7.0.30 doesn't scan exactly the same way servlet 3 annotations and
sometimes give subfolder instead of webinf/classes. just adapting the
classname to manage it
Modified:
openejb/trunk/openejb/pom.xml
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/OpenEJBContextConfig.java
Modified: openejb/trunk/openejb/pom.xml
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/pom.xml?rev=1384123r1=1384122r2=1384123view=diff
==
--- openejb/trunk/openejb/pom.xml (original)
+++ openejb/trunk/openejb/pom.xml Wed Sep 12 21:01:26 2012
@@ -143,7 +143,7 @@
junit.version4.9/junit.version
org.apache.axis2.version1.4.1/org.apache.axis2.version
scannotation.version1.0.2/scannotation.version
-
org.apache.openwebbeans.version1.1.5/org.apache.openwebbeans.version
+
org.apache.openwebbeans.version1.1.6-SNAPSHOT/org.apache.openwebbeans.version
geronimo.connector.version3.1.1/geronimo.connector.version
geronimo-osgi.version1.1/geronimo-osgi.version
geronimo-javamail_1.4_spec.version1.7.1/geronimo-javamail_1.4_spec.version
Modified:
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/OpenEJBContextConfig.java
URL:
http://svn.apache.org/viewvc/openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/OpenEJBContextConfig.java?rev=1384123r1=1384122r2=1384123view=diff
==
---
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/OpenEJBContextConfig.java
(original)
+++
openejb/trunk/openejb/tomee/tomee-catalina/src/main/java/org/apache/tomee/catalina/OpenEJBContextConfig.java
Wed Sep 12 21:01:26 2012
@@ -25,6 +25,7 @@ import org.apache.openejb.assembler.clas
import org.apache.openejb.loader.SystemInstance;
import org.apache.openejb.util.LogCategory;
import org.apache.openejb.util.Logger;
+import org.apache.xbean.finder.util.Classes;
import org.xml.sax.InputSource;
import javax.servlet.ServletContainerInitializer;
@@ -44,6 +45,9 @@ public class OpenEJBContextConfig extend
private static final String MYFACES_TOMEEM_CONTAINER_INITIALIZER =
org.apache.tomee.myfaces.TomEEMyFacesContainerInitializer;
private static final String TOMEE_MYFACES_CONTEXT_LISTENER =
org.apache.tomee.myfaces.TomEEMyFacesContextListener;
+private static final String CLASSES = classes;
+private static final String WEB_INF = WEB-INF;
+
private TomcatWebAppBuilder.StandardContextInfo info;
public OpenEJBContextConfig(TomcatWebAppBuilder.StandardContextInfo
standardContextInfo) {
@@ -144,7 +148,7 @@ public class OpenEJBContextConfig extend
final URLClassLoader loader = new URLClassLoader(new
URL[]{file.toURI().toURL()});
for (String webAnnotatedClassName :
webAppInfo.webAnnotatedClasses) {
-final String classFile =
webAnnotatedClassName.replace('.', '/') + .class;
+final String classFile =
webAnnotatedClassName.substring(getSubPackage(file).length()).replace('.',
'/') + .class;
final URL classUrl = loader.getResource(classFile);
if (classUrl == null) {
@@ -170,6 +174,34 @@ public class OpenEJBContextConfig extend
}
}
+// because we don't always get WEB-INF/classes folder, simply get the
already appended subpackage
+private static String getSubPackage(final File file) {
+File current = file.getParentFile();
+if (current == null) {
+return ;
+}
+
+File previous = file;
+while (current.getParentFile() != null) {
+if (CLASSES.equals(previous.getName())
WEB_INF.equals(current.getName())) {
+String path =
file.getAbsolutePath().replaceFirst(previous.getAbsolutePath(), );
+if (path.startsWith(File.separator)) {
+path = path.substring(File.separator.length());
+}
+if (path.endsWith(File.separator)) {
+path = path.substring(0, path.length() -
Re: moving modules to sandbox
+1 2012/9/11 Thiago Veronezi thi...@veronezi.org +1 [], Thiago On Tue, Sep 11, 2012 at 6:32 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: any objection to move openejb-spring and openejb-logging (from utils/) to sandbox? these modules are either not used or no more working for lifecycle reason in tomee (spring)? *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com*
Re: [DISCUSS] New descriptor format
Regarding tag names i'd remove upercase characters at the beginning, not really xml conventions. +1 to start with something simple even if incomplete. It's always easier to add things than to remove. If we want to have something clean, complete with all suggestions in, I feel like we won't have anything until months (years?). Jean-Louis 2012/9/10 Romain Manni-Bucau rmannibu...@gmail.com a little up since a minimum of this descriptor is mandatory for next release IMO. the webservices (soap/rest) config is today not very user friendly and i absolutely want an answer for *next* release. This is just a subset of the config we are talking about: properties tag + bean (pojo or not) properties any way to find a solution quickly about it? my thought is mainly we can use the following: application !-- i'd ignore the name in the parsing for the moment -- Properties !-- nested or not, just use what you need/want/like -- /Properties !-- here are the choices -- Ejb Properties foo = bar /Properties /Ejb Pojo Properties foo = bar /Properties /Pojo /application Then we have the question of the module/war: my thought is pretty simple on it: to find a pojo/ejb in a war/module (from its id) or globally it is simply a search algorithm so we could then really easily accept both config (knowing the previous config will be used at least for 80% of apps). So for next release i'd go for previous format then this format is extensible and not fixed IMO so for me it sounds fine wdyt? *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/2 Romain Manni-Bucau rmannibu...@gmail.com hmm, if you speak about info tree it is only regarding perf for me. all the cloud stuff should be managed from a provisionning tool (puppet, chef...). All other solution sounds pretty manually done. The cloud point if to keep the (dynamic) config in a single node then propagate it from template. Well, do we have any choice at this point or are we still discussing? *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com*
Re: [DISCUSS] New descriptor format
Ok then, no issue to not use caps ;-) 2012/9/10 Romain Manni-Bucau rmannibu...@gmail.com about tag names it is currently equalsIgnorecase and i want to keep it ;) *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/10 Jean-Louis MONTEIRO jeano...@gmail.com Regarding tag names i'd remove upercase characters at the beginning, not really xml conventions. +1 to start with something simple even if incomplete. It's always easier to add things than to remove. If we want to have something clean, complete with all suggestions in, I feel like we won't have anything until months (years?). Jean-Louis 2012/9/10 Romain Manni-Bucau rmannibu...@gmail.com a little up since a minimum of this descriptor is mandatory for next release IMO. the webservices (soap/rest) config is today not very user friendly and i absolutely want an answer for *next* release. This is just a subset of the config we are talking about: properties tag + bean (pojo or not) properties any way to find a solution quickly about it? my thought is mainly we can use the following: application !-- i'd ignore the name in the parsing for the moment -- Properties !-- nested or not, just use what you need/want/like -- /Properties !-- here are the choices -- Ejb Properties foo = bar /Properties /Ejb Pojo Properties foo = bar /Properties /Pojo /application Then we have the question of the module/war: my thought is pretty simple on it: to find a pojo/ejb in a war/module (from its id) or globally it is simply a search algorithm so we could then really easily accept both config (knowing the previous config will be used at least for 80% of apps). So for next release i'd go for previous format then this format is extensible and not fixed IMO so for me it sounds fine wdyt? *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/2 Romain Manni-Bucau rmannibu...@gmail.com hmm, if you speak about info tree it is only regarding perf for me. all the cloud stuff should be managed from a provisionning tool (puppet, chef...). All other solution sounds pretty manually done. The cloud point if to keep the (dynamic) config in a single node then propagate it from template. Well, do we have any choice at this point or are we still discussing? *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com*
Re: OpenEJB 2012 Meetup - EU or USA
Common guys, Time to book hotels, trains, etc. Would better/easier to get the same hotel if possible. BTW, thanks Daniel for the tip. JLouis 2012/9/8 dsh daniel.hais...@gmail.com It's September! Btw, if you plan to travel by ICE (train), you ought to reserve seats or otherwise you won't have any in the worst case until arriving in Munich. Cheers Daniel On Tue, Aug 28, 2012 at 12:04 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi all, Time to re activate that topic. Which option would you prefer? In regards to Daniel's comment, we can minimize cost avoiding many trips between the conference and Munich. Please vote on options. My preference is C). Start at ApacheCon on Monday, then get together for coding and touring on Friday, and the following weekend. I will be in another country the week before so unable to be there the weekend before. For the organization, did someone already book the hotel? Or maybe had a look to a list of hotels? Any suggestions? I'd like to get it booked by September. Jean-Louis 2012/6/25 dsh daniel.hais...@googlemail.com Probably 4 hours from Sinsheim to Munich city and you should take in account that you would spend about 70 - 80 euros for a single ride. Maybe there's a cheaper group ticket for all of us... try using this site to plan the trip or get any more information: - http://www.bahn.de/i/view/USA/en/index.shtml ICE = high speed train (whatever highspeed meens) IC = intercity (ICE minus express) EC - euro city - http://www.bahn.com/i/view/GBR/en/trains/overview/ic_and_ec.shtml Cheers Daniel On Sun, Jun 24, 2012 at 10:29 PM, David Blevins david.blev...@gmail.com wrote: On May 29, 2012, at 11:59 AM, David Blevins wrote: On May 29, 2012, at 1:48 AM, Jean-Louis MONTEIRO wrote: Ok guys, seems like Apache Con EU is the winner, isn't it? ApacheCon will be from 5th to 9th of November. The main question is how short nights will be to let us have some coding sessions ;-) That seems to be the case and that's definitely the question :) From experience, it's very hard to get everyone in one place at one time at conferences. We'll probably want to pick a day or two that are ours Nudging this forward a little. There's talk of doing a 'ApachEE' track at ApacheCon. Not sure what day that will be. Maybe Mark can comment. Mark will be speaking at W-JAX in Munich a few hours away later in the same week. They've asked me to speak as well and I think it would be great for the project. That would mean I'd have to split ApacheCon by Wednesday sometime as Thursday is the last day of W-JAX We have options. A We could have our time a few days before ApacheCon, like the preceeding weekend. B We could just do the week of ApacheCon -- I'll just only be able to hang out for three of the days. C We could move the fun over to Munich and continue our get-together there and use the subsequent weekend for hacking and touring. D Other? If we did option C, maybe we could do one day of hacking on say Sunday before the conference, the hacking again on Friday in Munich. Then touring in Munich Saturday. Seems like it's a three hour train ride from the ApacheCon location to Munic. Thoughts? -David
Re: OpenEJB 2012 Meetup - EU or USA
That'd be really awesome to get you as well. The week after is perfect for me (even if I made it also possible the weekend before). Nothing done except ApacheCon tickets that's why I'm asking. JLouis 2012/9/10 Jonathan Gallimore jonathan.gallim...@gmail.com Hi guys, I'm hoping I will be able to join you, but unfortunately I won't be able to come to the conference as I won't be able to get the time off work. I'm hoping to come out for one of the weekends, most likely the one after the conference (Munich?). Has anyone picked a hotel for Munich? Jon Sent from my iPad On 10 Sep 2012, at 08:44, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Common guys, Time to book hotels, trains, etc. Would better/easier to get the same hotel if possible. BTW, thanks Daniel for the tip. JLouis 2012/9/8 dsh daniel.hais...@gmail.com It's September! Btw, if you plan to travel by ICE (train), you ought to reserve seats or otherwise you won't have any in the worst case until arriving in Munich. Cheers Daniel On Tue, Aug 28, 2012 at 12:04 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Hi all, Time to re activate that topic. Which option would you prefer? In regards to Daniel's comment, we can minimize cost avoiding many trips between the conference and Munich. Please vote on options. My preference is C). Start at ApacheCon on Monday, then get together for coding and touring on Friday, and the following weekend. I will be in another country the week before so unable to be there the weekend before. For the organization, did someone already book the hotel? Or maybe had a look to a list of hotels? Any suggestions? I'd like to get it booked by September. Jean-Louis 2012/6/25 dsh daniel.hais...@googlemail.com Probably 4 hours from Sinsheim to Munich city and you should take in account that you would spend about 70 - 80 euros for a single ride. Maybe there's a cheaper group ticket for all of us... try using this site to plan the trip or get any more information: - http://www.bahn.de/i/view/USA/en/index.shtml ICE = high speed train (whatever highspeed meens) IC = intercity (ICE minus express) EC - euro city - http://www.bahn.com/i/view/GBR/en/trains/overview/ic_and_ec.shtml Cheers Daniel On Sun, Jun 24, 2012 at 10:29 PM, David Blevins david.blev...@gmail.com wrote: On May 29, 2012, at 11:59 AM, David Blevins wrote: On May 29, 2012, at 1:48 AM, Jean-Louis MONTEIRO wrote: Ok guys, seems like Apache Con EU is the winner, isn't it? ApacheCon will be from 5th to 9th of November. The main question is how short nights will be to let us have some coding sessions ;-) That seems to be the case and that's definitely the question :) From experience, it's very hard to get everyone in one place at one time at conferences. We'll probably want to pick a day or two that are ours Nudging this forward a little. There's talk of doing a 'ApachEE' track at ApacheCon. Not sure what day that will be. Maybe Mark can comment. Mark will be speaking at W-JAX in Munich a few hours away later in the same week. They've asked me to speak as well and I think it would be great for the project. That would mean I'd have to split ApacheCon by Wednesday sometime as Thursday is the last day of W-JAX We have options. A We could have our time a few days before ApacheCon, like the preceeding weekend. B We could just do the week of ApacheCon -- I'll just only be able to hang out for three of the days. C We could move the fun over to Munich and continue our get-together there and use the subsequent weekend for hacking and touring. D Other? If we did option C, maybe we could do one day of hacking on say Sunday before the conference, the hacking again on Friday in Munich. Then touring in Munich Saturday. Seems like it's a three hour train ride from the ApacheCon location to Munic. Thoughts? -David
Re: JIRA reports on website
Ok back to that subject. Gonna try to dig into JIRAs again. Just a small note: does anybody deal with all pending patches or is the page generation broken? See http://tomee.apache.org/dev/jira/patches.html JLouis 2012/7/18 Jean-Louis MONTEIRO jeano...@gmail.com With the same idea, I'd like to also add a widget from this page (the last one at the bottom of the page). And also try to generate dependency reports like this one. thoughts? Jean-Louis 2012/7/18 David Blevins david.blev...@gmail.com In efforts to help Jean-Louis with the JIRA cleaning and ensure his hard work can bring as much value as possible, I expanded the capabilities of our CMS usage so we can generate reports from JIRA I went ahead and made a couple of them: - http://tomee.apache.org/dev/jira/todo.html - http://tomee.apache.org/dev/jira/patches.html The functionality is driven by the Swizzle Jira Report tool. Example source looks like: - https://svn.apache.org/repos/asf/openejb/site/trunk/content/dev/jira/todo.swjira New reports added to that dir are automatically indexed. Feel free to tweak these reports as much as you want or add new ones. You can run any of them by hand via: $ wget https://svn.apache.org/repos/asf/openejb/site/trunk/lib/swizzle-jirareport-1.6.2-SNAPSHOT-dep.jar $ wget https://svn.apache.org/repos/asf/openejb/site/trunk/content/dev/jira/todo.swjira $ java -jar swizzle-jirareport-1.6.2-SNAPSHOT-dep.jar todo.swjira -David
Re: OpenEJB 2012 Meetup - EU or USA
Hi all, Time to re activate that topic. Which option would you prefer? In regards to Daniel's comment, we can minimize cost avoiding many trips between the conference and Munich. Please vote on options. My preference is C). Start at ApacheCon on Monday, then get together for coding and touring on Friday, and the following weekend. I will be in another country the week before so unable to be there the weekend before. For the organization, did someone already book the hotel? Or maybe had a look to a list of hotels? Any suggestions? I'd like to get it booked by September. Jean-Louis 2012/6/25 dsh daniel.hais...@googlemail.com Probably 4 hours from Sinsheim to Munich city and you should take in account that you would spend about 70 - 80 euros for a single ride. Maybe there's a cheaper group ticket for all of us... try using this site to plan the trip or get any more information: - http://www.bahn.de/i/view/USA/en/index.shtml ICE = high speed train (whatever highspeed meens) IC = intercity (ICE minus express) EC - euro city - http://www.bahn.com/i/view/GBR/en/trains/overview/ic_and_ec.shtml Cheers Daniel On Sun, Jun 24, 2012 at 10:29 PM, David Blevins david.blev...@gmail.com wrote: On May 29, 2012, at 11:59 AM, David Blevins wrote: On May 29, 2012, at 1:48 AM, Jean-Louis MONTEIRO wrote: Ok guys, seems like Apache Con EU is the winner, isn't it? ApacheCon will be from 5th to 9th of November. The main question is how short nights will be to let us have some coding sessions ;-) That seems to be the case and that's definitely the question :) From experience, it's very hard to get everyone in one place at one time at conferences. We'll probably want to pick a day or two that are ours Nudging this forward a little. There's talk of doing a 'ApachEE' track at ApacheCon. Not sure what day that will be. Maybe Mark can comment. Mark will be speaking at W-JAX in Munich a few hours away later in the same week. They've asked me to speak as well and I think it would be great for the project. That would mean I'd have to split ApacheCon by Wednesday sometime as Thursday is the last day of W-JAX We have options. A We could have our time a few days before ApacheCon, like the preceeding weekend. B We could just do the week of ApacheCon -- I'll just only be able to hang out for three of the days. C We could move the fun over to Munich and continue our get-together there and use the subsequent weekend for hacking and touring. D Other? If we did option C, maybe we could do one day of hacking on say Sunday before the conference, the hacking again on Friday in Munich. Then touring in Munich Saturday. Seems like it's a three hour train ride from the ApacheCon location to Munic. Thoughts? -David
Re: [DISCUSS] New descriptor format
Both would actually function. User preference would dictate which is used. Thoughts? Given the choice, which would you use? See any third options that might be cooler? AppContext, ModuleContext, and BeanContext would each get a `Configuration` bucket. There might be a better name than `Configuration`. Maybe `Properties` or perhaps even better, `Options` ? I prefer the properties tag first because we always used it, then (as already mentioned) because it reinforce the syntax we wanna use, and last because almost all the container can the configured (overridden) by system properties. The fully qualified names is better IMO. Ideas on something better? Better names maybe? Perhaps `PojoContext` for consistency. Perhaps get really basic and `ClassContext` ? ClassContext is ok for me as soon as we allow inheritance. I mean, define ClassContext (even for an ejb or an abstract name) and allow ejb (ie. BeanContext) inherit from it. That's useful when configurations are similar and painful to maintain for a lot of ejbs (wss4j for example) or when we want to deploy an ejb more than one. ## Standalone apps vs apps with many modules No special opinion. I'd say more or less like Karan, the less to remember, the better. With the validation framework and good messages, that should work fine. Otherwise a new root tag is also great. BTW, like exabrial sample (on pastee). Would be great to also support such a mechanism. Regarding XSD versus properties, definitely +1 for properties. XSD can be fine in IDE, but it will be painful for end users and for use to maintain and move forward. Hope it helps. I'm happy to contribute if necessary. Jean-Louis
[RESULT] ApacheCon EU submits
Hello guys, back from great holidays with sun. Just to know who finally submitted something to ApacheCon EU. Jean-Louis
Re: Call for Papers for ApacheCon Europe 2012 now open!
Hi David, Yes, that's also my opinion. I'd like to also present or co present with anybody interested in. My favorite topic features oriented (cloud maybe): with ssh, provisioning, cluster deployment, dynamic place holder, etc? WDYT? The point is that I will leave tomorrow morning, then I won't be able to push an abstract nor fill the call for paper. But, I can definitely work afterwards on the presentation itself (content, etc). Dunno, if you David or someone else can submit a talk for me. Jean-Louis 2012/7/25 David Blevins david.blev...@gmail.com It'd be great to see 3 or 4 submissions for TomEE and some of the more interesting features we have. I'd love to attend a KarafEE talk! It'd be great to have a general TomEE talk and then some talks specific to various features. I think it would be great to also have dual focused talks: TomEE and MyFaces, TomEE and OpenWebBeans. I'm giving this talk at JavaOne and was thinking of something along these lines for ApacheCon. We could have it earlier in the day and then use the tail end to say don't miss these other talks and entice people into attending the other sessions. If not a lot of TomEE talks get accepted, I'm happy to co present. I hope they do though because I'm really looking forward to attending a TomEE talk :) That will be a nice change of pace :) Title: Apache TomEE, Java EE 6 Web Profile on Tomcat Abstract: Making its Java EE 6 Web Profile certification debut at JavaOne 2011, Apache TomEE combines the simplicity of Tomcat with the power of Java EE. The first half of this session introduces TomEE and shows how Tomcat applications leveraging Java EE technologies can become simpler and lighter with a Java EE 6 certified solution built right on Tomcat. The second half focuses on those already familiar with TomEE and goes into detail on latest advancements, testing techniques including Arquillian, clustering features and production considerations. If you're a Tomcat lover or a TomEE enthusiast, this is the session you don't want to miss! Notes: Intended as a coverall session to get people as much TomEE information as they can handle, introduce TomEE to those who are not yet aware you don't have to choose between Tomcat and JavaEE, and let those following the project get a glimpse of project advancements around maven tooling, Arquillian support, clustering/failover, emerging concepts and more. Briskly paced, slide focused, key demos only. Objectives: - Introduce people to TomEE - Increase JavaEE adoption in Tomcat holdouts - Update those following TomEE on must know advancements and techniques Session Category Open Source Standards Experience Level: - Introductory
Re: openejb examples
Sorry Romain, can't get the point. In a standard Maven structure, there is commonly a hierarchy of project. If we have webapp example, that seems pretty fine to me to have a parent module containing sub modules. Anyway, could you give more details about your thoughts? Jean-Louis 2012/7/25 Romain Manni-Bucau rmannibu...@gmail.com Hi, we currently have some examples in a subfolder of examples directory - i think of webapps shouldn't we make it flat in our svn? in fact there are 2 choices IMO: 1) make it flat (mv webapps/* .) 2) create 2 children to examples (and move all examples in the good child): openejb and tomee I don't really like 2 since a lot of openejb stuff will work in tomee and it can be confusing thoughts? - Romain
Plugin mechanism
Hi devs, Was wondering if we could manage kinda plugin mechanism in a simple way. I mean, a way to add a resource, to ass the ssh extension or the provisioning one, without having to push/extract a set of jars in the catalina.home/lib (ie. in the same place where we also put our TomEE jars). The point is that, when pushing ssh, provisioning or if an end user wants to push a new resource let's say, it will have to deploy and mix his jars with our. It makes it difficult to update, or remove a new resource/extension (ssh, provisioning). Sometime, it also make sense to have a single catalina.home distro and get different catalina.base configuration per application where the set of plugins won't be the same. As we are not in OSGi, and we don't want to be in TomEE, we won't have a classloader hierarchy with a separate classloader per plugin. So it's only a matter of getting things separated to ease update/activation/deactivation and so on. So, i just would like to be able to have a catalina.base|home/plugins directory, where each plugin has its own directory like tomcat.home/ conf/ * plugins.properties* webapps/ mywebapplication/ WEB-INF/ ... lib/ openejb-XXX tomcat-YYY ... * plugins/ myplugin-A/ conf/ lib/ myplugin-B/ conf/ lib/* WDYT? Jean-Louis
Re: Call for Papers for ApacheCon Europe 2012 now open!
I will be off by Thursday evening so not sure to be able to push something until Thursday. JLouis 2012/7/21 Jacek Laskowski ja...@japila.pl On Fri, Jul 20, 2012 at 1:11 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: FYI We cannot afford to not submit a TomEE talk IMO Indeed! It also aligns well with my checking out the recent changes around OSGification of OpenEJB with KarafEE. That's something that drives me towards thinking about ApacheCON. Let's think about it for the coming weeks. The date is on August, the 3rd. Time for some fun! 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: do we drop our openejb-spring module?
With the full support of CDI in OpenEJB/TomEE the question is relevant. Dunno, if there is a lot of people using it. Don't have a clear opinion on it. If it's really limited or buggy, maybe we can move it to sandbox. If someone asks for that integration again, we can maybe have a look. Jean-Louis 2012/7/20 Romain Manni-Bucau rmannibu...@gmail.com Do we move openejb-spring from utils to sandbox? in standalone it works but is quite limited compared to what we can do with CDI. moreover it doesn't work with TomEE (and to make it working is quite a complicated work for a poor gain IMO) wdyt? - Romain
Fwd: Call for Papers for ApacheCon Europe 2012 now open!
FYI We cannot afford to not submit a TomEE talk IMO JLouis -- Forwarded message -- From: Nick Burch nick.bu...@alfresco.com Date: 2012/7/19 Subject: Call for Papers for ApacheCon Europe 2012 now open! To: committ...@apache.org Hi All We're pleased to announce that the Call for Papers for ApacheCon Europe 2012 is finally open! (For those who don't already know, ApacheCon Europe will be taking place between the 5th and the 9th of November this year, in Sinsheim, Germany.) If you'd like to submit a talk proposal, please visit the conference website at http://www.apachecon.eu/ and sign up for a new account. Once you've signed up, use your dashboard to enter your speaker bio, then submit your talk proposal(s). There's more information on the CFP page on the conference website. We welcome talk proposals from all projects, from right across the bredth of projects at the foundation! To make things easier for talk selection and scheduling, we'd ask that you tag your proposal with the track that it most closely fits within. The details of the tracks, and what projects they expect to cover, are available at http://www.apachecon.eu/**tracks/http://www.apachecon.eu/tracks/ . (If your project/group of projects was intending to submit a track, and missed the deadline, then please get in touch with us on apachecon-disc...@apache.org straight away, so we can work out if it's possible to squeeze you in...) The CFP will close on Friday 3rd August, so you've a little over weeks to send in your talk proposal. Don't put it off! We'll look forward to seeing some great ones shortly! Thanks Nick (On behalf of the Conferences committee)
Re: Call for Papers for ApacheCon Europe 2012 now open!
That's by far more difficult in English but with a significant amount of time to prepare, it's definitely something i'd like to. JLouis 2012/7/20 Romain Manni-Bucau rmannibu...@gmail.com does it mean you are volonteer to do it? :p - Romain 2012/7/20 Jean-Louis MONTEIRO jeano...@gmail.com FYI We cannot afford to not submit a TomEE talk IMO JLouis -- Forwarded message -- From: Nick Burch nick.bu...@alfresco.com Date: 2012/7/19 Subject: Call for Papers for ApacheCon Europe 2012 now open! To: committ...@apache.org Hi All We're pleased to announce that the Call for Papers for ApacheCon Europe 2012 is finally open! (For those who don't already know, ApacheCon Europe will be taking place between the 5th and the 9th of November this year, in Sinsheim, Germany.) If you'd like to submit a talk proposal, please visit the conference website at http://www.apachecon.eu/ and sign up for a new account. Once you've signed up, use your dashboard to enter your speaker bio, then submit your talk proposal(s). There's more information on the CFP page on the conference website. We welcome talk proposals from all projects, from right across the bredth of projects at the foundation! To make things easier for talk selection and scheduling, we'd ask that you tag your proposal with the track that it most closely fits within. The details of the tracks, and what projects they expect to cover, are available at http://www.apachecon.eu/**tracks/http://www.apachecon.eu/tracks/ . (If your project/group of projects was intending to submit a track, and missed the deadline, then please get in touch with us on apachecon-disc...@apache.org straight away, so we can work out if it's possible to squeeze you in...) The CFP will close on Friday 3rd August, so you've a little over weeks to send in your talk proposal. Don't put it off! We'll look forward to seeing some great ones shortly! Thanks Nick (On behalf of the Conferences committee)
Re: Call for Papers for ApacheCon Europe 2012 now open!
:D 2012/7/20 Mohammad Nour El-Din nour.moham...@gmail.com On Fri, Jul 20, 2012 at 1:32 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: does it mean you are volonteer to do it? :p Good idea and also good idea :D - Romain 2012/7/20 Jean-Louis MONTEIRO jeano...@gmail.com FYI We cannot afford to not submit a TomEE talk IMO JLouis -- Forwarded message -- From: Nick Burch nick.bu...@alfresco.com Date: 2012/7/19 Subject: Call for Papers for ApacheCon Europe 2012 now open! To: committ...@apache.org Hi All We're pleased to announce that the Call for Papers for ApacheCon Europe 2012 is finally open! (For those who don't already know, ApacheCon Europe will be taking place between the 5th and the 9th of November this year, in Sinsheim, Germany.) If you'd like to submit a talk proposal, please visit the conference website at http://www.apachecon.eu/ and sign up for a new account. Once you've signed up, use your dashboard to enter your speaker bio, then submit your talk proposal(s). There's more information on the CFP page on the conference website. We welcome talk proposals from all projects, from right across the bredth of projects at the foundation! To make things easier for talk selection and scheduling, we'd ask that you tag your proposal with the track that it most closely fits within. The details of the tracks, and what projects they expect to cover, are available at http://www.apachecon.eu/**tracks/http://www.apachecon.eu/tracks/ . (If your project/group of projects was intending to submit a track, and missed the deadline, then please get in touch with us on apachecon-disc...@apache.org straight away, so we can work out if it's possible to squeeze you in...) The CFP will close on Friday 3rd August, so you've a little over weeks to send in your talk proposal. Don't put it off! We'll look forward to seeing some great ones shortly! Thanks Nick (On behalf of the Conferences committee) -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
