Re: [VOTE] Release Geronimo eclipse plugin 3.0.1
thanks and +1 2013/5/27 Forrest Xia forres...@gmail.com +1 myself On Mon, May 27, 2013 at 5:33 PM, Forrest Xia forres...@gmail.com wrote: Hi Devs, Please vote Geronimo eclipse plugin(GEP) 3.0.1 release. This is a release along with Geronimo server runtime release 3.0.1. For details, see http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.1.txt The GEP code up for vote is: https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-003/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.zip The GEP staging update site is: http://people.apache.org/builds/geronimo/eclipse/updates/ The release staging site is: https://repository.apache.org/content/repositories/orgapachegeronimo-003 The tag has created at: http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.1/ Vote will be at least open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo 3.0.1
Looks good, +1 2013/5/20 Yi Xiao xiaoyijhondeve...@gmail.com Great！ +1 On Fri, May 17, 2013 at 9:56 PM, Forrest Xia forres...@gmail.com wrote: Hi Devs, Please vote Geronimo 3.0.1 release with these major differences from the previous release: 1. JSF 2.1 support 2. JDBC 4 support 3. Some components upgrade, including Tomcat, JPA, Yoko, Tranql, ActiveMQ 4. Quite a few bugs fixes For details, see http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1/RELEASE_NOTES-3.0.1.txt The server code up for vote is: https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.zip The binary code up for vote is: Java EE 6 Full Profile Tomcat Assemblies: https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.zip Java EE 6 Web Profile Tomcat Assemblies: https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.zip Little-G Tomcat Assemblies: https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.zip *Staging repo is:* https://repository.apache.org/content/repositories/orgapachegeronimo-009/ *The tag has created at:* http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1 Java EE 6 TCKs all passed! Vote will be at least open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Thanks! Regards, Forrest -- Best regards! John Xiao -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo Tomcat fork 7.0.39.2 for a security fix
looks good to me, thanks forrest +1 2013/5/17 Forrest Xia forres...@gmail.com Hi, Please revote for the Geronimo Tomcat fork 7.0.39.2 release, which merges a tomcat security fix for CVE-2013-2071 The components up for vote are: https://repository.apache.org/content/repositories/orgapachegeronimo-008/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.39/7.0.39.2/tomcat-parent-7.0.39-7.0.39.2-source-release.zip Staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-008 tag is here: http://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.39.2 Vote open 72 hours [ ] +1 release this [ ] 0 don't care [ ] -1 don't release this (please explain) -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo Tomcat fork 7.0.39.1
+1, looks good to me. thanks Forrest! 2013/5/10 Forrest Xia forres...@gmail.com +1 myself with HowTo.txt license head fix On Thu, May 9, 2013 at 10:41 PM, Forrest Xia forres...@gmail.com wrote: Hi, Please revote for the Geronimo Tomcat 7.0.39.1 release, which is based on Tomcat 7.0.39 tag. The components up for vote are: https://repository.apache.org/content/repositories/orgapachegeronimo-029/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.39/7.0.39.1/tomcat-parent-7.0.39-7.0.39.1-source-release.zip Staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-029 tag is here: https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.39.1 Vote open 72 hours [ ] +1 release this [ ] 0 don't care [ ] -1 don't release this (please explain) -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo 3.0.0 (3rd Try)
+1, All looked good to me, great to see 3.0!! Thanks Forrest! -Rex 2012/7/6 Forrest Xia forres...@gmail.com On Thu, Jul 5, 2012 at 10:17 PM, Kevan Miller kevan.mil...@gmail.comwrote: On Jul 5, 2012, at 9:27 PM, Forrest Xia wrote: On Fri, Jul 6, 2012 at 6:05 AM, Kevan Miller kevan.mil...@gmail.com wrote: On Jul 5, 2012, at 2:23 PM, David Jencks wrote: I'm a little confused by the LICENSE and NOTICE in the source. I've been telling people for years that these should apply to what is actually in the source, however these appear to be the ones appropriate for the binary distros. For instance they point to files in the repository folder which only exists in the binary distro. That can be debated. And I've seen both styles used. I'm not sure which style I prefer. Separate source and binary license files may be more accurate, but they also may be misinterpreted. I do agree that license/notice in jar files should be source licenses… In any event, the current source LICENSE file clearly indicates what applies to source and binaries. A consumer of the source should be able to easily sort out what applies/doesn't apply… So, I'm fine with it as is… Kevan, your vote? Was waiting for build to finish. Given the US holidays, etc. I'd give this a few more days to gather additional votes… OK, that's fine to wait a couple days for this vote. --kevan -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Daytrader 3.0.0
All looks good. +1 2012/7/6 viola lu viola...@gmail.com +1 On Fri, Jul 6, 2012 at 3:41 PM, Forrest Xia forres...@gmail.com wrote: Don't forget this one, please! On Tue, Jul 3, 2012 at 7:23 PM, Forrest Xia forres...@gmail.com wrote: Hi Devs, Align with Geronimo 3.0.0 release, here is the daytrader 3.0.0 ready for vote. The source code up for vote is: https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/daytrader/daytrader-parent/3.0.0/daytrader-parent-3.0.0-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/daytrader/daytrader-parent/3.0.0/daytrader-parent-3.0.0-source-release.zip Staging repo is: https://repository.apache.org/content/repositories/orgapachegeronimo-016 The tag has created at: https://svn.apache.org/repos/asf/geronimo/daytrader/tags/daytrader-parent-3.0.0/ Vote will be at least open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest -- viola Apache Geronimo -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo Samples 3.0.0
Looks good to me. +1 2012/7/6 Forrest Xia forres...@gmail.com Don't forget this one, please! On Wed, Jul 4, 2012 at 12:25 AM, Forrest Xia forres...@gmail.com wrote: Hi Devs, Align with Geronimo 3.0.0 release, here is the Geronimo Samples 3.0.0 ready for vote. The source code up for vote is: https://repository.apache.org/content/repositories/orgapachegeronimo-024/org/apache/geronimo/samples/samples-parent/3.0.0/samples-parent-3.0.0-source-release.tar.gzhttps://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/daytrader/daytrader-parent/3.0.0/daytrader-parent-3.0.0-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-024/org/apache/geronimo/samples/samples-parent/3.0.0/samples-parent-3.0.0-source-release.zip https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/daytrader/daytrader-parent/3.0.0/daytrader-parent-3.0.0-source-release.tar.gz Staging repo is: https://repository.apache.org/content/repositories/orgapachegeronimo-024 The tag has created at: http://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0.0/ Vote will be at least open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: Review status of G 3.0.0 release goals
+1 to drop the jetty assembly. Looks like the community is not that keen to jetty tck. rex 2012/6/26 Forrest Xia forres...@gmail.com Any more thoughts on droping jetty assembly from 3.0.0 release? or I will go ahead to make the change and roll out 3.0.0 release... On Mon, Jun 25, 2012 at 12:41 PM, Shawn Jiang genspr...@gmail.com wrote: +1 to drop Jetty release from 3.0.0 release for now. On Mon, Jun 25, 2012 at 12:04 PM, Forrest Xia forres...@gmail.comwrote: Echo Jarek's response here in dev list again: So it looks like we have quite a bit of failures on Jetty. I guess we either have to drop it from the release (if we want to release soon) or try to fix it and delay the release. Thoughts? My thought is to drop jetty release for 3.0.0 and roll out tomcat assembly asap. Any more thoughts about 3.0.0 release?? On Sat, Jun 23, 2012 at 9:06 PM, Forrest Xia forres...@gmail.comwrote: On Sat, Jun 23, 2012 at 12:57 AM, Kevan Miller kevan.mil...@gmail.comwrote: On Jun 22, 2012, at 9:20 AM, Forrest Xia wrote: On Fri, Jun 22, 2012 at 8:36 AM, Forrest Xia forres...@gmail.com wrote: On Tue, Jun 19, 2012 at 10:42 AM, Forrest Xia forres...@gmail.com wrote: On Tue, Jun 19, 2012 at 9:47 AM, Jarek Gawor jga...@gmail.com wrote: How are things with Jetty? Some user emails gave me an impression that things don't look too good. If things with Jetty are looking bad then we should either consider dropping it from the release or delaying the release until we get it in shape. Some status consolidation here about Jetty assembly in 3.0 branch: 1. BV and DI tck all pass for jetty8-javaee6 assembly 2. JCDI and full profile execution just triggered, we will see some results after two days. JCDI tck against jetty8-javaee6 failed most of the cases. Jetty assembly results: Tests 37068 Passed23616 Failed13452 Forrest -- too much TCK information on a public list. TCK terms may be improving in the future. However, until then, we should not talk about test names, numbers of tests, etc. OK, got it, sorry for that. --kevan -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest -- Shawn -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Commented] (GERONIMO-6314) Add monitor role to protect the JMX access
[ https://issues.apache.org/jira/browse/GERONIMO-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290669#comment-13290669 ] Rex Wang commented on GERONIMO-6314: committed to 3.0-beta branch @ revision: 1347255 thanks Add monitor role to protect the JMX access Key: GERONIMO-6314 URL: https://issues.apache.org/jira/browse/GERONIMO-6314 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector, JVM-compatibility Affects Versions: 3.0-beta-1 Environment: linux,windows Reporter: Tina Li Assignee: Tina Li Fix For: 3.0-beta-2 Attachments: GERONIMO-6314_formatUpdated.patch Currently, only the admin user can connect to JMX and the admin user has read/write access to MBeans. Now find a method to let monitor role also can access JMX but only has read-only access. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6360) OBR portlet
[ https://issues.apache.org/jira/browse/GERONIMO-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13286395#comment-13286395 ] Rex Wang commented on GERONIMO-6360: commit the first drop to 3.0-beta branch @ rev 1344578. Gary will help implement the following functions, Thanks. OBR portlet --- Key: GERONIMO-6360 URL: https://issues.apache.org/jira/browse/GERONIMO-6360 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Provide a OBR portlet for managing repositories and browsing the contents. The portlet should support the following: 1) List repositories, add new repository, remove repository, and refresh repository. 2) View contents of the OBR 3) Optionally deploy / install bundles from OBR. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Geronimo bval-jsr303 bundle version 0.4_1 (3rd Try)
+1 thanks Forrest! 2012/5/16 Forrest Xia forres...@gmail.com This is a version upgrade release, from 0.3_incubating to 0.4, for bval bundled in Geronimo, raised via GERONIMO-6345, it's to fix the tck failures when upgrading BV TCK to 1.0.6.GA level, also fixed the legal issue. The artifacts up for vote are: https://repository.apache.org/content/repositories/orgapachegeronimo-095/org/apache/geronimo/bundles/bval-jsr303/0.4_1/bval-jsr303-0.4_1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-095/org/apache/geronimo/bundles/bval-jsr303/0.4_1/bval-jsr303-0.4_1-source-release.zip The tag is: http://svn.apache.org/repos/asf/geronimo/bundles/tags/bval-jsr303-0.4_1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release EL 2.2 spec version 1.0.3
+1 2012/4/24 Forrest Xia forres...@gmail.com This is a bug fix release to fix one issue reported in GERONIMO-6330https://issues.apache.org/jira/browse/GERONIMO-6330 . The components up for vote are: org/apache/geronimo/specs/geronimo-el_2.2_spec/1.0.3/geronimo-el_2.2_spec-1.0.3-source-release.zip org/apache/geronimo/specs/geronimo-el_2.2_spec/1.0.3/geronimo-el_2.2_spec-1.0.3-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachegeronimo-087 The source repo is: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_2.2_spec-1.0.3/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: Geronimo release cycle
+1 I prefer trunk to 4.0, and 3.0-beta branch to 3.0 branch. -Rex 2012/3/29 Jarek Gawor jga...@gmail.com I consider the changes made in trunk quite substantial so I think I would call trunk 4.x and call beta branch 3.x. Jarek On Wed, Mar 28, 2012 at 12:26 PM, Russell E Glaue rgl...@cait.org wrote: move current trunk to 3.1 and change current beta branch to 3.0. +1 As long as 3.0-beta-2 passes Java EE 1.6 tests and also provides no broken core/primary functionality we have 2.2, we should stamp it as 3.0. 3.1 can focus on the continuation of 3.x enhancements. -RG On 03/28/2012 06:46 AM, Forrest Xia wrote: On Wed, Mar 28, 2012 at 6:08 PM, Shawn Jiang genspr...@gmail.com mailto:genspr...@gmail.com wrote: 1.x J2EE 1.4 2.0 Java EE 1.5 2.1 Java EE 1.5 2.2 Java EE 1.5 3.0 Java EE 1.6 Considering the previous practice, we'd better to move current trunk to 3.1 and change current beta branch to 3.0. Sounds good. Any more idea? On Tue, Mar 27, 2012 at 11:48 PM, Forrest Xia forres...@gmail.com mailto:forres...@gmail.com wrote: Saw this query, have an idea about the current release roadmap. 1. Can we move the current incomplete trunk work to version 4 of geronimo? 2. Rename 3.0-beta branch as the formal 3.0 release? Any thoughts? Forrest -- Forwarded message -- From: *Arsen Abdrakhmanov* arsen.abdrakhma...@gmail.com mailto:arsen.abdrakhma...@gmail.com Date: Tue, Mar 27, 2012 at 7:20 PM Subject: Geronimo release cycle To: u...@geronimo.apache.org mailto:u...@geronimo.apache.org Dear Geronimo Team, Actually, I am the fan of geronimo for more than 5 years already. For the moment, I am promoting the usage of Geronimo as a platform for non-critical applications in our company (banking industry in KZ). According to our company's internal policy, only official releases of open-source software products can be used for internal applications. Currently, the release cycle for Geronimo is about an year or even longer, so it takes significant amount of time before we could use an updated version of software with bug fixes and enhancements. Taking that into account, can you give any information on your plans to accelerate the release cycle for new versions of Geronimo? I think, it would be very useful for the whole geronimo user community, if the releases were published at least semi-anually. Hope, it can also increase the popularity of Geronimo among other application servers. Best regards, Arsen Abdrakhmanov -- Thanks! Regards, Forrest -- Shawn -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: [Vote] Geronimo Eclipse Plugin (GEP) 2.1.8 RC1
+1, Thanks Yi Xiao and Forrest! 2012/1/6 Forrest Xia forres...@gmail.com Hi devs, With great help of Yi Xiao, I made a stage repo for GEP 2.1.8 release vote. So everyone, please help to review and vote on the release of Geronimo Eclipse Plugin (GEP) 2.1.8 RC1 from now on. GEP 2.1.8 supports Geronimo server 2.1.8 and Eclipse Indigo SR1(3.7.1). The source code zip is here: * https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.8/geronimo-eclipse-plugin-2.1.8-source-release.tar.gz * * https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.8/geronimo-eclipse-plugin-2.1.8-source-release.zip * The tag is here: http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-2.1.8 The deployable zip file is here: http://people.apache.org/builds/geronimo/eclipse/2.1.8/geronimo-eclipse-plugin-2.1.8-deployable.zip The update site zip file is here: http://people.apache.org/builds/geronimo/eclipse/2.1.8/geronimo-eclipse-plugin-2.1.8-updatesite.zip If you would like to review and/or comment on the release notes, you can find it here: http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-2.1.8.txt Create a Staging Site that can be used to test the update manager functions of Eclipse (Indigo and helios): http://people.apache.org/builds/geronimo/eclipse/updates/ The vote will be open for the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Resolved] (GERONIMO-5956) issues when deploy a standalone ejb web services
[ https://issues.apache.org/jira/browse/GERONIMO-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-5956. Resolution: Fixed Assignee: Rex Wang (was: Yi Xiao) thanks Xiao Yi for the patch to resolve #2. commit to 3.0-beta-1 branch at revision: 1230382 commit to trunk at revision: 1230384 issues when deploy a standalone ejb web services Key: GERONIMO-5956 URL: https://issues.apache.org/jira/browse/GERONIMO-5956 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: webservices Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 Attachments: HelloRex_EJB.jar, NCFWhenStandloneEjbWebServiceDeploy_5956.patch 1. the ejb base-dir is not add to the wsdl generator tool's class path, so the an CNF exception will be thrown. 2. after resovled #1, the ejb can be deployed successfully, but start failed with the following exceptions: Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration default/Hello_Hello_ejb/1-default/car failed to start due to the following reasons: The service J2EEApplication=null,j2eeType=EJBModule,name=default/Hello_Hello_ejb/1-default/car did not start because Creating application failed: D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar: Error building bean 'Hello'. Exception: class org.apache.openejb.OpenEJBException: Error while loading bean class com.abc.Hello for bean Hello_ejb.jar/Hello. Received message: Cannot locate the class com.abc.Hello from the codebase [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]: Error while loading bean class com.abc.Hello for bean Hello_ejb.jar/Hello. Received message: Cannot locate the class com.abc.Hello from the codebase [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar] org.apache.openejb.OpenEJBException: Creating application failed: D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar: Error building bean 'Hello'. Exception: class org.apache.openejb.OpenEJBException: Error while loading bean class com.abc.Hello for bean Hello_ejb.jar/Hello. Received message: Cannot locate the class com.abc.Hello from the codebase [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar]: Error while loading bean class com.abc.Hello for bean Hello_ejb.jar/Hello. Received message: Cannot locate the class com.abc.Hello from the codebase [D:\_g\_tck\geronimo-tck30\tck-testsuite\target\geronimo-tomcat-cts-3.0-SNAPSHOT\var\temp\geronimo-deployer7323628188918730994.tmpdir\Hello_ejb.jar] at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:784) at org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:457) at org.apache.geronimo.openejb.OpenEjbSystemGBean.createApplication(OpenEjbSystemGBean.java:438) at org.apache.geronimo.openejb.EjbModuleImpl.doStart(EjbModuleImpl.java:182) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:975) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:301) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105
Re: [ANNOUNCE] Apache Geronimo v2.1.8 is Released!
Thanks, Forrest! 2011/12/28 Forrest Xia forres...@gmail.com The Apache Geronimo project is pleased to announce the availability of Apache Geronimo v2.1.8. This release includes quite a few new features, improvements, as well as bug fixes. Please see the detail information in 2.1.8 release noteshttp://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.8/RELEASE_NOTES.txt . A couple highlights are: - Command Line utility to enable/disable Monitoring server and Stat query Snapshot thread for DefaultServer - Add SQLServer 2008 Tranql connector - Improve windows startup batch scripts to redirect stdout and stderr messages to GERONIMO_HOME/var/log/geronimo.out - Upgrade JAXB to 2.1.13, Tomcat to 6.0.35, OpenEJB to 3.0.4, etc. Visit the Downloads http://geronimo.apache.org/downloads.html page for details on downloading Apache Geronimo v2.1.8 server assemblies. A big THANK YOU to all that contributed to this release! Great work everyone! -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo 2.1.8 RC2
+1, rat:check, build passed for me! thanks 2011/12/21 Forrest Xia forres...@gmail.com Hi folks, A release candidate for Geronimo 2.1.8 has been created and staged. The tag has been created here: https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.8/ The staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-377/ The main artifacts up for vote are the source release archives: https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-377/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.zip A tck execution against 2.1.8 tag is ongoing, and will be finished around 16 hours later. I will update the status here. The vote will be open for 72 hours. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Resolved] (GERONIMO-6191) can not query the persistence unit gbean when ejb is in a war
[ https://issues.apache.org/jira/browse/GERONIMO-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6191. Resolution: Fixed can not query the persistence unit gbean when ejb is in a war - Key: GERONIMO-6191 URL: https://issues.apache.org/jira/browse/GERONIMO-6191 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 When deploy a war which contains persistence.xml and ejbs, the persistent unit builder add the following gbean data to the earcontext: default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war?J2EEApplication=null,PersistenceUnitModule=WEB-INF/classes/,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war,j2eeType=PersistenceUnit,name=test=org.apache.geronimo.gbean.GBeanData@d1a87 but in the EjbDeploymentBuilder's line 209, It uses a pattern as following to query the persistent unit gbean data: [?EJBModule=.,J2EEApplication=null,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318411456796/war,j2eeType=PersistenceUnit#org.apache.geronimo.persistence.PersistenceUnitGBean] We can see it contains a constraint EJBModule=., which cause the query return empty. That lead the DeploymentException(No default PersistenceUnit specified, and none located); This is because the ejb module and the war module share the same earcontext and the configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Geronimo 3 and karaf 3
2011/12/20 David Jencks david_jen...@yahoo.com
I've been spending a lot of time working to rebase geronimo on karaf 3 so
we can have a maintainable future and get stuff like osgi 4.3, up to date
aries components, and the experimental region support now in karaf.
After a lot of work I have everything except clustering building and after
turning off a couple problematic modules the tomcat-javaee6 server starts
and the web admin console appears to work at least a little bit. I'd like
a little vacation this year and would like to commit this work first so
that others can help with the loose ends if they like. I'll probably be
around to answer questions in any case.
The modules that don't start are:
activemq-broker-blueprint. The ${X + Y} stuff is not getting evaluated at
all. I don't know if this is an xbean-blueprint problem or an aries
blueprint problem or a side effect of running in geronimo.
As a result activemq-ra and tomcat-console-activemq can't be started.
Hi David, neither xbean-blueprint nor aries-blueprint can correctly do such
evaluation. So for 3.0-beta-1 release, I provided an interim fix of
Aries-727 and release our aries-blueprint in external folder:
http://svn.apache.org/repos/asf/geronimo/external/tags/blueprint-0.3.0.1/
However, we should not use this approach for trunk. I had refactored the
codes in Aries-727 based on the discussion in Aries mailing list. The new
approach has been applied to Aries trunk.
The current approach is as following:
1, depends on following
org.apache.aries.blueprint.core-0.4.1-SNAPSHOT
org.apache.aries.blueprint.jexl.evaluator-0.1.1-SNAPSHOT (
http://svn.apache.org/repos/asf/aries/trunk/blueprint/blueprint-jexl-evaluator/
)
2. use the new namespace blueprint-ext 1.2.0
xmlns:ext=http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.2.0;
3. use the ext:property-placeholder with the new attribute *evaluator=jexl
* to do evaluation
ext:property-placeholder placeholder-prefix=$[
placeholder-suffix=] ignore-missing-locations=true
system-properties=override *evaluator=jexl*
ext:default-properties
ext:property name=name value=value /
ext:property name=a value=Hello /
ext:property name=b value=FooBar /
/ext:default-properties
ext:locationfile:///url/ext:location
/ext:property-placeholder
bean id=bar class=org.apache.aries.blueprint.sample.Bar
property name=value value=$[a+b]
...
basically, this will make the blueprint bundle reference a
PropertyEvaluator service with the property
org.apache.aries.blueprint.ext.evaluator.name=jexl to do the evaluate.
Hope this helps, and I can help fix this issue after your commit.
Merry Christmas and happy new year!
-Rex
client-deployer. I think this is a pretty simple gbean name problem but I
haven't looked into it.
Here are some of the changes:
-- assemble the server using a combination of karaf assembly from features
and kars and geronimo assembly from geronimo plugins. We now use the same
base karaf assembly stuff as the normal default full karaf assembly (except
I might have left out the spring feature repository).
-- basic geronimo components such as the kernel, configuration manager,
dependency manager, deployer, and service config builder are set up as osgi
declarative services so they start without any geronimo configuration.
They are generally configured through config admin as appropriate. Most
of these also have gbean wrappers so they can be accessed through gbean
references.
-- geronimo is started from a DS component, EmbeddedDaemon.
-- I think I'm using the karaf remote jmx security rather than ours. The
capabilities are similar but not identical.
Some other things that are not working yet:
-- The (gogo) geronimo console commands that work through remote gbean
proxies don't work AFAIK. Probably one way to fix this would be to expose
some more of the DS components using gbean wrappers, but I haven't looked
into this yet.
-- the app client (as well as the client-deployer) is not working yet at
all. We may be able to use command line args to tell the EmbeddedDaemon
it's an app client, or possibly not. We may be able to use a karaf
instance to supply different ConfigAdmin settings to e.g. the local
attribute manager to convince it it's an app client. Similarly the
separate console-like things presumably won't work either.
-- the EditableConfigurationManager needs to be replaced by a separate
component that edits the configuration it gets from the normal
configuration manager. I think this affects some part of the admin console.
I'f there's no strong opposition I'd like to commit this tomorrow.
Many thanks
david jencks
--
Lei Wang (Rex)
rwonly AT apache.org
Re: [VOTE] Release Geronimo 2.1.8
build pass, rat:check looks fine. +1 2011/12/19 Forrest Xia forres...@gmail.com Hi folks, A release candidate for Geronimo 2.1.8 has been created and staged. The tag has been created here: https://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.8/ The staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-367/ The main artifacts up for vote are the source release archives: https://repository.apache.org/content/repositories/orgapachegeronimo-367/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-367/org/apache/geronimo/geronimo/2.1.8/geronimo-2.1.8-source-release.zip A tck execution against 2.1.8 tag is ongoing, and will be finished around 16 hours later. I will update the status here. The vote will be open for 72 hours. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Thanks! Regards, Forrest -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo Tomcat 6.0.35.1
build pass, rat:check looks fine to me. +1 2011/12/20 viola lu viola...@gmail.com +1 On Sun, Dec 18, 2011 at 8:29 PM, Forrest Xia forres...@gmail.com wrote: Did rat:check, server build with this tomcat release, and all tck passed! Myself +1 On Sun, Dec 18, 2011 at 8:17 PM, Forrest Xia forres...@gmail.com wrote: Please vote for the Geronimo Tomcat 6.0.35.1 release, which is based on Tomcat 6.0.35 tag, and will be used in Geronimo 2.1.8 release. The components up for vote are: https://repository.apache.org/content/repositories/orgapachegeronimo-355/org/apache/geronimo/ext/tomcat/tomcat-parent-6.0.35/6.0.35.1/tomcat-parent-6.0.35-6.0.35.1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-355/org/apache/geronimo/ext/tomcat/tomcat-parent-6.0.35/6.0.35.1/tomcat-parent-6.0.35-6.0.35.1-source-release.zip Staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-014 https://repository.apache.org/content/repositories/orgapachegeronimo-355/ https://repository.apache.org/content/repositories/orgapachegeronimo-014 tag is here: https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.35.1/ Vote open 72 hours [ ] +1 release this [ ] 0 don't care [ ] -1 don't release this (please explain) -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest -- viola Apache Geronimo -- Lei Wang (Rex) rwonly AT apache.org
Re: [Proposition] - Collaboration between Karaf - Geronimo
So, in a word, IIUC, you are suggesting leverage the karaf features more in geronimo? Actually, there was some similar discussions in geronimo mailling list before. And David Jencks did a lot of investigation about this. Please see his post as following: http://mail-archives.apache.org/mod_mbox/geronimo-dev/201103.mbox/%3cf9aa388e-8050-4055-8719-5cd14b512...@yahoo.com%3E There really would be a lot of works to do to replace the current geronimo plugins mechanism with karaf features. And sure, I'd like to see geronimo to be more OSGi-friendly in future. However, TCK would be the main issue to do such fundamental refactor. That will involve a great many resources to make the server comply with it. -Rex 2011/12/15 Charles Moulliard cmoulli...@gmail.com Hi, Within mailing list of Karaf, we have started a discussion about the idea to have a KarafEE release. This idea is similar to the reflection that OpenEJB team has had with TomEE but using Tomcat as Java Application Server. As Geronimo uses Karaf as their kernel (which is not the case for Glassfish, JBoss, Eclipse Virgo, ...) that makes a lot of sense that we continue to promote karaf as platform not only for Integration Server like ServiceMix but also for J2EE platform. Since EJB3 spec and CDI, we see more and more projects interested to have/use an EJB container on Karaf and use it as an alternative to Spring (Dynamic Module/Blueprint). Developing a server, certify it, cost a lot. As we we do not want to re-invent the wheel and due to number of resources available, we prefer to capitalize on the work/efforts done. This is why we come to you to discuss the idea about collaborating together to improve existing geronimo-karaf platform to address points mentioned in this thread ( http://karaf.922171.n3.nabble.com/Proposition-Apache-KarafEE-td3585332.html ) to be able to provide a KarafEE or Geronimo distro but using features mechanism of Karaf to deploy OpenEJB, OpenJPA, new Karaf web console, ... What do you think about that ? Regards, Charles Moulliard Apache Committer Blog : http://cmoulliard.blogspot.com Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard Skype: cmoulliard -- Forwarded message -- From: James Strachan ja...@fusesource.com Date: Thu, Dec 15, 2011 at 9:54 AM Subject: Re: [Proposition] - Apache KarafEE To: d...@karaf.apache.org Given Geronimo is already based on Karaf and focussed on EE; am not sure why re-implementing Geronimo inside Karaf is a good idea - wouldn't it be better to just work with the Geronimo community to fix the issues you've raised (which seems to be about having more Karaf-like approaches available inside Geronimo and fixing up the web consoles - neither seem that big a deal to me to require forking a community project?). Am sure the Geronimo folks would be happy to take contributions to enable more of Karaf's features in an EE context etc. Certifying against EE is a massive amount of work; there has to be a really really good reason (and a ton of volunteers with a massive amount of free time who've got nothing better to do) to justify duplicating that effort. Given how modular OSGi Karaf are; am not sure why any of these goals can't be solved inside Geronimo (e.g. take Geronimo uninstall its console, install Karaf's console - no need to fork a community for that?). On 14 December 2011 12:40, Charles Moulliard cmoulli...@gmail.com wrote: Hi, As you probably knows, I work with OpenEJB community since a couple of weeks to be able to deploy OpenEJB 4.0.0-SNAPSHOT on Apache Karaf. The OpenEJB container can already been deployed and EJBs jars registered. Work should be done around OpenEJB to be able to easily scan (like we do for deploy directory in Karaf) new or updated EJB jars file and add karaf command. When this new brick will be ready, everything will be in place to propose/provide an Apache KarafEE (EE = Enterprise Edition) release packaging OpenEJB, OpenJPA, Aries JPA, Aries JNDI, Pax Web, Aries Transaction Manager. The first question/remark that I will receive from the communauty will be : Great/Brillant idea but Apache Geronimo is already there and use Apache Karaf. So why developing a new server : There a lot of good reasons why we should do that and study my suggestion carefully but some arguments could be : (1) concurrence in this area is always good comparing to what we have in J2EE world, JBoss, TomEE, Glassfish. J2EE are de facto servers used in major and many Java projects. OSGI is not yet recognized as a robust and simple solution to be used due to lack of tooling, complexity to package and create bundles. So having a new OSGI true J2EE server could help to spread the world, (2) The packaging and deployment approach of Apache Geronimo is a bit different from Karaf and some of the Karaf features are not enable (e.g :
Re: [Announcement] Geronimo SamplesDaytrader 3.0-beta-1 is released now!
Thanks, viola! 2011/12/16 viola lu viola...@gmail.com Hi All, As the subject, this is a release accompany with Geronimo Server 3.0-beta-1, which includes these samples which now works on the server: 1. Java EE 5 samples 2. Java EE 6 samples - converter-javaee6/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/converter-javaee6/ - cviewer-javaee6/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/cviewer-javaee6/ - ejbtimer-javaee6/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/ejbtimer-javaee6/ - fileupload-javaee6/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/fileupload-javaee6/ - jarresource-javaee6/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/jarresource-javaee6/ - jpa20demo-javaee6/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/jpa20demo-javaee6/ - singletonejb-javaee6/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/singletonejb-javaee6/ - webfragment-javaee6/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/webfragment-javaee6/ 3. OSGi samples - helloworld-eba/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/osgi/helloworld-eba/ - showmethemoney/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/osgi/showmethemoney/ - wab-sample/https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/osgi/wab-sample/ 4. Daytrader You can access them samples: http://geronimo.apache.org/plugins/samples-3.0-beta-1/ or https://repository.apache.org/content/groups/public/org/apache/geronimo/samples/ -- viola Apache Geronimo -- Lei Wang (Rex) rwonly AT apache.org
Re: [ANNOUNCE] Welcome Trygve Hardersen as a new Geronimo committer
Congrats and welcome onboard! 2011/12/9 Kevan Miller kevan.mil...@gmail.com Everyone, In recognition of his contributions to the Geronimo project, the Geronimo PMC recently invited Trygve Hardersen to become a committer on our project. We are pleased to announce that he has accepted our invitation. Please join us in congratulating Trygve. Welcome! --kevan -- Lei Wang (Rex) rwonly AT apache.org
Re: [Vote] Release Geronimo Samples Daytrader 3.0-beta-1 RC4
Viola, you posted a rat report only for the root 4 files. Here is mine. Anyway, looks good to me. +1 * Summary --- Notes: 11 Binaries: 9 Archives: 0 Standards: 790 Apache Licensed: 788 Generated Documents: 0 JavaDocs are generated and so license header is optional Generated files do not required license headers 2 Unknown Licenses *** Archives (+ indicates readable, $ unreadable): * Files with AL headers will be marked L Binary files (which do not require AL headers) will be marked B Compressed archives will be marked A Notices, licenses etc will be marked N ALbuildutil/pom.xml N buildutil/README.txt AL buildutil/src/main/java/org/apache/geronimo/samples/buildutil/Txt2Html.java ALgeronimo-samples-archetype/pom.xml AL geronimo-samples-archetype/src/main/resources/archetype-resources/pom.xml -Rex 2011/12/6 viola lu viola...@gmail.com Here is my +1 mvn clean install on suse 10 sp2 mvn rat:check, no license problem run osgi samples. Summary --- Notes: 2 Binaries: 0 Archives: 0 Standards: 2 Apache Licensed: 2 Generated Documents: 0 JavaDocs are generated and so license header is optional Generated files do not required license headers 0 Unknown Licenses *** Archives (+ indicates readable, $ unreadable): * Files with AL headers will be marked L Binary files (which do not require AL headers) will be marked B Compressed archives will be marked A Notices, licenses etc will be marked N N LICENSE N NOTICE ALpom.xml ALsrc/site/site.xml * Printing headers for files without AL header... On Fri, Nov 25, 2011 at 7:02 PM, viola lu viola...@gmail.com wrote: Hi Devs, A forth release candidate for Geronimo Sample Daytrader 3.0-beta-1 has been created and staged coz of previous failure release candidate. The tags have been created here: https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1 https://svn.apache.org/repos/asf/geronimo/daytrader/tags/daytrader-3.0-beta-1/ The staging repos is here: https://repository.apache.org/content/repositories/orgapachegeronimo-210/ (Daytrader) *https://repository.apache.org/content/repositories/orgapachegeronimo-247 * (Sample) The main artifacts up for vote are the source release archives: *https://repository.apache.org/content/repositories/orgapachegeronimo-247 ** /org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.tar.gzhttps://repository.apache.org/content/repositories/orgapachegeronimo-231/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.tar.gz * *https://repository.apache.org/content/repositories/orgapachegeronimo-247 ** /org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.ziphttps://repository.apache.org/content/repositories/orgapachegeronimo-231/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.zip * https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.zip Here is sample update - Append Java EE 6 and OSGi samples Remove empty java file https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee6/singletonejb-javaee6/singletonejb-javaee6-war/src/main/java/org/apache/geronimo/samples/javaee6/singletonejb/sessionBeans/ Remove useless dependency files https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1/samples/javaee5/DataCDInfo/DataCDInfo-JTA-jetty/src/main/ The vote will be open for the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- viola Apache Geronimo -- viola Apache Geronimo -- Lei Wang (Rex) rwonly AT apache.org
Re: [ANNOUNCE] Geronimo Eclipse Plugin 3.0-beta-1 release
Congrats, and thanks Janet! -Rex 2011/12/6 han hongfang hanhongf...@gmail.com Hi, Apache Geronimo project is pleased to announce the available of Apache Geronimo Eclipse Plugin v3.0-beta-1. It supports Geronimo 3.0-beta-1 server and Eclipse 3.7 (Indigo). Visit the links to GEP 3.0-beta-1 release notes. http://www.apache.org/dist/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0-beta-1.txt The new version have been available through eclipse update site now. http://www.apache.org/dist/geronimo/eclipse/updates/ For manual installation, GEP 3.0-beta-1 can be downloaded from http://apache.org/dist/geronimo/eclipse/3.0-beta-1/ THANK YOU all that contributed to this release! -- Best regards, Han Hong Fang (Janet) hanhongfang AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: [Vote] Release Geronimo Samples Daytrader 3.0-beta-1 RC3
I think they should not be the blocker issue of the release. However, we do need clean them after release. 2011/11/24 Ivan xhh...@gmail.com While running rat:check, I could see some dependencies.xml and MANIFEST.MF file have no AL license, and there are some unwanted files like treelist.txt/dependencies.add.xml files. Also, there is an empty Java file \samples\javaee6\singletonejb-javaee6\singletonejb-javaee6-war\src\main\java\org\apache\geronimo\samples\javaee6\singletonejb\sessionBeans\StatefulCalculator.java, not sure whether this is a problem. 2011/11/24 Forrest Xia forres...@gmail.com +1 On Tue, Nov 22, 2011 at 7:52 PM, viola lu viola...@gmail.com wrote: Hi Devs, A release candidate for Geronimo Sample Daytrader 3.0-beta-1 has been created and staged. The tags have been created here: https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1 https://svn.apache.org/repos/asf/geronimo/daytrader/tags/daytrader-3.0-beta-1/ The staging repos is here: https://repository.apache.org/content/repositories/orgapachegeronimo-210/ (Daytrader) https://repository.apache.org/service/local/repositories/orgapachegeronimo-231(Sample) The main artifacts up for vote are the source release archives: * https://repository.apache.org/content/repositories/orgapachegeronimo-231/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.tar.gz * * https://repository.apache.org/content/repositories/orgapachegeronimo-231/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.zip * https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.zip The vote will be open for the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- viola Apache Geronimo -- Thanks! Regards, Forrest -- Ivan -- Lei Wang (Rex) rwonly AT apache.org
Re: [Vote] Release Geronimo Samples Daytrader 3.0-beta-1 RC3
all look good to me, +1 -Rex 2011/11/22 viola lu viola...@gmail.com Hi Devs, A release candidate for Geronimo Sample Daytrader 3.0-beta-1 has been created and staged. The tags have been created here: https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-beta-1 https://svn.apache.org/repos/asf/geronimo/daytrader/tags/daytrader-3.0-beta-1/ The staging repos is here: https://repository.apache.org/content/repositories/orgapachegeronimo-210/ (Daytrader) https://repository.apache.org/service/local/repositories/orgapachegeronimo-231(Sample) The main artifacts up for vote are the source release archives: * https://repository.apache.org/content/repositories/orgapachegeronimo-231/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.tar.gz * * https://repository.apache.org/content/repositories/orgapachegeronimo-231/org/apache/geronimo/samples/samples-parent/3.0-beta-1/samples-parent-3.0-beta-1-source-release.zip * https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-210/org/apache/geronimo/daytrader/daytrader-parent/3.0-beta-1/daytrader-parent-3.0-beta-1-source-release.zip The vote will be open for the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- viola Apache Geronimo -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Accept code donation from HypoBytes LTD
+1 !! 2011/11/23 Kevan Miller kevan.mil...@gmail.com As you have seen in recent Jira updates and dev list discussions HypoBytes and Trygve Hardersen have offered to contribute Geronimo 2.2 and GShell dependency updates and associated code updates to the Geronimo project. A CCLA has been submitted for the changes. As part of the IP Clearance process, we need to hold a vote to accept these changes. The two patch files to be considered are attached to https://issues.apache.org/jira/browse/GERONIMO-6217 Specifically, the code updates are available here: https://issues.apache.org/jira/secure/attachment/12504761/geronimo-2.2-1188546-clean.patch(MD5: bae04ca7df1b7351fa8ea18dd72f82b6) and https://issues.apache.org/jira/secure/attachment/12504760/gshell-alpha-1-606434-clean.patch(MD5: f5d8762e9531a3e615f8caac22ea650e) Once we have accepted the software contribution, there is an IP clearance vote needed on the Incubator mailing list. I don't think we necessarily need to discuss the technical details of this contribution, here. If you have comments, it's probably best to start a discussion thread. Ultimately, the technical specifics of the contributions will be best discussed as we are (or preparing to) commit the code. With this vote, we should review the contributions for any irregularities or legal concerns and record that the Geronimo project accepts these code contributions. [ ] +1 Accept the code contributions from HypoBytes [ ] 0 no opinion [ ] -1 Do not accept the code contributions (please explain why) --kevan -- Lei Wang (Rex) rwonly AT apache.org
[ANNOUNCEMENT] Apache Geronimo v3.0-beta-1 Released!
The Apache Geronimo project is very glad to announce the release of Apache Geronimo v3.0-beta-1 server. It is the first open source solution other than RI that implements both the Java EE 6.0 Full profile and Web profile specifications. This release has passed 100% of SUN's Java Enterprise Edition 6.0 Full Profile and Web Profile Certification Test Suites, and includes a great many new features, improvements, bug fixes. Further more, Geronimo v3.0-beta-1 has transformed its kernel based on OSGi technology, so it natively supports OSGi programming model and new technologies in the OSGi enterprise marketplace, including: - OSGi Blueprint Bundle - OSGi Web Application Bundle (WAB) - Enterprise Bundle Application (EBA). Please see the detail information in the release notes: http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0-beta-1/RELEASE_NOTES-3.0-beta-1.txt A couple highlights are: Support SUN's Java Enterprise Edition 6.0 Full Profile specification: - Servlet 3.0 - JSP 2.2 - JSTL 1.2 - JSF 2.0 - EL 2.2 - EJB 3.1 - JPA 2.0 - JTA 1.1 - JTS 1.0 - JDBC 3.0 - JNDI 1.2 - JMS 1.1 - JMX 1.2 - JACC 1.4 - JASS 1.0 - JASPIC 1.0 - JAX-WS 2.2 - JAX-RPC 1.1 - JAX-RS - JAXR 1.0 - JAXB 2.2 - JAXP 1.3 - SAAJ 1.3 - Java Mail 1.4 - DI 1.0 - Bean Validation 1.0 - Common Annotations 1.0 - CDI and DI 1.0 - Debugging support for other languages 1.0 - Managed Beans 1.0 - Interceptors 1.1. For details about Full Profile specifications, please visit Java EE specifications website. Support OSGi Core Specification v4.3 and part of Enterprise Specification v4.2, including: - Configuration Admin Service Specification - Blueprint Container Specification - Web Applications Specification - JNDI Services Specification - JPA service Specification - JMX Management Model Specification. For details about OSGi specifications, please visit OSGi Alliance website. You can download the source jar and binary assemblies from http://geronimo.apache.org/apache-geronimo-v30-beta-1-release.html The geronimo-tomcat7-javaee6-3.0-beta-1 assembly has passed the Java Enterprise Edition 6.0 Full Profile Certification Test Suite. And the geronimo-tomcat7-javaee6-web-3.0-beta-1 assembly has passed Java Enterprise Edition 6.0 Web Profile Certification Test Suite. Thanks very much to various ASF partner projects that we include, e.g. Apache Tomcat, OpenJPA, OpenEJB, ActiveMQ, MyFaces, OpenWebBeans, Axis2, Aries etc. And also a big THANK YOU to all committers and contributors for this release! Great work everyone! Rex Wang, Apache Geronimo Project 2011-11-15
[RESULT][VOTE] Release Geronimo 3.0-beta-1 (2nd attempt)
+1 from myself. Result: The Vote for Release Geronimo 3.0-beta-1 (2nd attempt) got +1 from the following people: Kevan Miller, Shawn Jiang, Viola Lu, Han Hong Fang, Zhi Xie, Forrest Xia, Ivan, David Jencks, Yi Xiao, Chi Run Hua, and me. And 6 of above are PMC members. There is no +0 or -1. So the vote passed! Thanks everyone for the review! I will announce the release soon. -Rex 2011/11/7 Rex Wang rwo...@gmail.com Hi Devs, Let's review and vote for 3.0-beta-1 RC2. Geronimo 3.0-beta-1 supports Java Enterprise Edition 6.0 Full Profile specification, and also add the support for OSGi programming model. In RC2, Kevan added the dojo license, and Shawn provided a fix for the EJB TCK problem. Thanks! The components up for vote is: https://repository.apache.org/content/repositories/orgapachegeronimo-164/org/apache/geronimo/geronimo/3.0-beta-1/geronimo-3.0-beta-1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-164/org/apache/geronimo/geronimo/3.0-beta-1/geronimo-3.0-beta-1-source-release.zip Staging repo is: https://repository.apache.org/content/repositories/orgapachegeronimo-164 The tag has created at: http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0-beta-1/ We need wait the latest TCK results against the tag again. Thanks Forrest for helping run the TCK! Vote will be at least open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
[VOTE] Release Geronimo 3.0-beta-1 (2nd attempt)
Hi Devs, Let's review and vote for 3.0-beta-1 RC2. Geronimo 3.0-beta-1 supports Java Enterprise Edition 6.0 Full Profile specification, and also add the support for OSGi programming model. In RC2, Kevan added the dojo license, and Shawn provided a fix for the EJB TCK problem. Thanks! The components up for vote is: https://repository.apache.org/content/repositories/orgapachegeronimo-164/org/apache/geronimo/geronimo/3.0-beta-1/geronimo-3.0-beta-1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-164/org/apache/geronimo/geronimo/3.0-beta-1/geronimo-3.0-beta-1-source-release.zip Staging repo is: https://repository.apache.org/content/repositories/orgapachegeronimo-164 The tag has created at: http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0-beta-1/ We need wait the latest TCK results against the tag again. Thanks Forrest for helping run the TCK! Vote will be at least open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Lei Wang (Rex) rwonly AT apache.org
Re: classloading hot swap support
Yes, it is good improvement. However, I have run the release:prepare for a while... So the fixes won't go into 3.0-beta-1... -Rex 2011/11/7 Kevan Miller kevan.mil...@gmail.com Jarek made a couple of nice updates for hot swap support on server and devtools trunk (rc: 1195665 and 1195653). Would be kind of nice to see these in the beta release, but certainly not necessary… Also, IIUC, Jarek's changes only apply to OSGi applications (not Java EE WAR/EAR apps). Adding hot-swap support for general Java EE apps would be great to have. If anybody has some time/interest, would be a great thing to work on… --kevan -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo 3.0-beta-1 (1st attempt)
OK. Will drop 3.0-beta-1 RC1. -Rex 2011/11/2 Kevan Miller kevan.mil...@gmail.com Dojo files were added to our source, but no updates were made to LICENSE files. I've added AFL 2.1 to license files on trunk. Note, it looks like updates from beta had not yet been merged back into trunk. The license update is required, IMO. So, here's my -1 until my update is merged into the beta branch and included in the release. I'm running a build, now... Assuming build/tests look good -- everything else looked good. --kevan On Mon, Oct 31, 2011 at 9:45 AM, Rex Wang rwo...@gmail.com wrote: Hi Devs, Finally, I managed to get a 3.0-beta-1 release candidate up for your review and vote. Geronimo 3.0-beta-1 supports Java Enterprise Edition 6.0 Full Profile specification, and also add the support for OSGi programming model. The components up for vote is: https://repository.apache.org/content/repositories/orgapachegeronimo-123/org/apache/geronimo/geronimo/3.0-beta-1/geronimo-3.0-beta-1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-123/org/apache/geronimo/geronimo/3.0-beta-1/geronimo-3.0-beta-1-source-release.zip Staging repo is: https://repository.apache.org/content/repositories/orgapachegeronimo-123 The tag has created at: http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0-beta-1/ We are still waiting the latest TCK results against the tag. Vote will be at least open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
[VOTE] Release Geronimo 3.0-beta-1 (1st attempt)
Hi Devs, Finally, I managed to get a 3.0-beta-1 release candidate up for your review and vote. Geronimo 3.0-beta-1 supports Java Enterprise Edition 6.0 Full Profile specification, and also add the support for OSGi programming model. The components up for vote is: https://repository.apache.org/content/repositories/orgapachegeronimo-123/org/apache/geronimo/geronimo/3.0-beta-1/geronimo-3.0-beta-1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-123/org/apache/geronimo/geronimo/3.0-beta-1/geronimo-3.0-beta-1-source-release.zip Staging repo is: https://repository.apache.org/content/repositories/orgapachegeronimo-123 The tag has created at: http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0-beta-1/ We are still waiting the latest TCK results against the tag. Vote will be at least open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Lei Wang (Rex) rwonly AT apache.org
Re: Geronimo 3.0-beta Release Status
Hi Devs All the things for 3.0-beta-1 are ready. However, there is a power outage in my office in Friday night and the whole weekend. So I have to delay performing the release to next Monday. -Rex 2011/10/5 Kevan Miller kevan.mil...@gmail.com On Sep 28, 2011, at 11:13 PM, Rex Wang wrote: 2011/9/29 Forrest Xia forres...@gmail.com Rex, Seems we want to wait a little bit longer(for openejb 4.0.0 release) to branch the current trunk out to 3.0-beta in branches, that properly happens around first half of October, right? Yes, The only dependency - OpenEJB 4.0.0 has not started release yet. We have to wait.. OK. OpenEJB 4.0-beta has been released. So, we're not waiting on OpenEJB any longer... Hope we can start our final release prep, soon... --kevan -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Resolved] (GERONIMO-6205) karaf features.core need a org.apache.karaf.features.cfg in etc
[ https://issues.apache.org/jira/browse/GERONIMO-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6205. Resolution: Fixed karaf features.core need a org.apache.karaf.features.cfg in etc --- Key: GERONIMO-6205 URL: https://issues.apache.org/jira/browse/GERONIMO-6205 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 karaf.features.core need a org.apache.karaf.features.cfg in etc otherwise, the following exception will occur: geronimo 2011-10-26 21:46:42,250 WARN [FeaturesServiceImpl] Unable to add features repository at startup java.lang.IllegalArgumentException: URI is not absolute at java.net.URI.toURL(URI.java:1080) at org.apache.karaf.features.internal.FeatureValidationUtil.validate(FeatureValidationUtil.java:46) at org.apache.karaf.features.internal.FeaturesServiceImpl.validateRepository(FeaturesServiceImpl.java:199) at org.apache.karaf.features.internal.FeaturesServiceImpl.internalAddRepository(FeaturesServiceImpl.java:210) at org.apache.karaf.features.internal.FeaturesServiceImpl.start(FeaturesServiceImpl.java:918) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:226) at org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:824) at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:636) at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:724) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219) at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147) at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:6 at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:331) at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:227) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) 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:619) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6205) karaf features.core need a org.apache.karaf.features.cfg in etc
karaf features.core need a org.apache.karaf.features.cfg in etc --- Key: GERONIMO-6205 URL: https://issues.apache.org/jira/browse/GERONIMO-6205 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: commands Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 karaf.features.core need a org.apache.karaf.features.cfg in etc otherwise, the following exception will occur: geronimo 2011-10-26 21:46:42,250 WARN [FeaturesServiceImpl] Unable to add features repository at startup java.lang.IllegalArgumentException: URI is not absolute at java.net.URI.toURL(URI.java:1080) at org.apache.karaf.features.internal.FeatureValidationUtil.validate(FeatureValidationUtil.java:46) at org.apache.karaf.features.internal.FeaturesServiceImpl.validateRepository(FeaturesServiceImpl.java:199) at org.apache.karaf.features.internal.FeaturesServiceImpl.internalAddRepository(FeaturesServiceImpl.java:210) at org.apache.karaf.features.internal.FeaturesServiceImpl.start(FeaturesServiceImpl.java:918) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:226) at org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:824) at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:636) at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:724) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219) at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147) at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:6 at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:331) at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:227) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) 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:619) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6205) karaf features.core need a org.apache.karaf.features.cfg in etc
[ https://issues.apache.org/jira/browse/GERONIMO-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13135985#comment-13135985 ] Rex Wang commented on GERONIMO-6205: commit a quick fix in trunk at revision: 1189218 in 3.0-beta-1 branch At revision: 1189219 -Rex karaf features.core need a org.apache.karaf.features.cfg in etc --- Key: GERONIMO-6205 URL: https://issues.apache.org/jira/browse/GERONIMO-6205 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 karaf.features.core need a org.apache.karaf.features.cfg in etc otherwise, the following exception will occur: geronimo 2011-10-26 21:46:42,250 WARN [FeaturesServiceImpl] Unable to add features repository at startup java.lang.IllegalArgumentException: URI is not absolute at java.net.URI.toURL(URI.java:1080) at org.apache.karaf.features.internal.FeatureValidationUtil.validate(FeatureValidationUtil.java:46) at org.apache.karaf.features.internal.FeaturesServiceImpl.validateRepository(FeaturesServiceImpl.java:199) at org.apache.karaf.features.internal.FeaturesServiceImpl.internalAddRepository(FeaturesServiceImpl.java:210) at org.apache.karaf.features.internal.FeaturesServiceImpl.start(FeaturesServiceImpl.java:918) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:226) at org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:824) at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:636) at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:724) at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64) at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219) at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147) at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:6 at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:331) at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:227) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) 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:619) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r1189303 - in /geronimo/server/branches/3.0-beta-1: RELEASE_NOTES-3.0-beta-1.txt framework/configs/karaf-framework/src/main/distribution/text/RELEASE_NOTES-3.0-beta-1.txt
cool! thanks Forrest. 2011/10/27 xiam...@apache.org Author: xiaming Date: Wed Oct 26 16:44:07 2011 New Revision: 1189303 URL: http://svn.apache.org/viewvc?rev=1189303view=rev Log: After double checking the TCK results of web profile assembly, the tomcat-web assembly passed all tck of web profile required, so add them back to release note to indicate the correct status of Geronimo 3.0-beta-1 release. Modified: geronimo/server/branches/3.0-beta-1/RELEASE_NOTES-3.0-beta-1.txt geronimo/server/branches/3.0-beta-1/framework/configs/karaf-framework/src/main/distribution/text/RELEASE_NOTES-3.0-beta-1.txt Modified: geronimo/server/branches/3.0-beta-1/RELEASE_NOTES-3.0-beta-1.txt URL: http://svn.apache.org/viewvc/geronimo/server/branches/3.0-beta-1/RELEASE_NOTES-3.0-beta-1.txt?rev=1189303r1=1189302r2=1189303view=diff == --- geronimo/server/branches/3.0-beta-1/RELEASE_NOTES-3.0-beta-1.txt (original) +++ geronimo/server/branches/3.0-beta-1/RELEASE_NOTES-3.0-beta-1.txt Wed Oct 26 16:44:07 2011 @@ -46,11 +46,12 @@ The available distributions are as follo Certified distributions: - Apache Geronimo server using Tomcat as the Web container and Axis2 as the Web Services engine. (Java EE 6 Full Profile Certificated) +- Apache Geronimo server assembly using Tomcat as the Web container. (Java EE 6 + Web Profile Certified) Non-Certified distributions: - Apache Geronimo server using Jetty as the Web container and CXF as the Web Services engine. -- Apache Geronimo server assembly using Tomcat as the Web container. - Apache Geronimo server assembly using Jetty as the Web container. - A minimal Geronimo server (Little-G) assembly using the Jetty web-container. - A minimal Geronimo server (Little-G) assembly using the Tomcat web-container. Modified: geronimo/server/branches/3.0-beta-1/framework/configs/karaf-framework/src/main/distribution/text/RELEASE_NOTES-3.0-beta-1.txt URL: http://svn.apache.org/viewvc/geronimo/server/branches/3.0-beta-1/framework/configs/karaf-framework/src/main/distribution/text/RELEASE_NOTES-3.0-beta-1.txt?rev=1189303r1=1189302r2=1189303view=diff == --- geronimo/server/branches/3.0-beta-1/framework/configs/karaf-framework/src/main/distribution/text/RELEASE_NOTES-3.0-beta-1.txt (original) +++ geronimo/server/branches/3.0-beta-1/framework/configs/karaf-framework/src/main/distribution/text/RELEASE_NOTES-3.0-beta-1.txt Wed Oct 26 16:44:07 2011 @@ -46,11 +46,12 @@ The available distributions are as follo Certified distributions: - Apache Geronimo server using Tomcat as the Web container and Axis2 as the Web Services engine. (Java EE 6 Full Profile Certificated) - +- Apache Geronimo server assembly using Tomcat as the Web container. (Java EE 6 + Web Profile Certified) + Non-Certified distributions: - Apache Geronimo server using Jetty as the Web container and CXF as the Web Services engine. -- Apache Geronimo server assembly using Tomcat as the Web container. - Apache Geronimo server assembly using Jetty as the Web container. - A minimal Geronimo server (Little-G) assembly using the Jetty web-container. - A minimal Geronimo server (Little-G) assembly using the Tomcat web-container. -- Lei Wang (Rex) rwonly AT apache.org
Re: Review LICENSE and NOTICE of Geronimo 3.0-beta-1
OK, Thank you, Kevan! I will start the rest of processes soon. -Rex 2011/10/25 Kevan Miller kevan.mil...@gmail.com On Oct 24, 2011, at 10:05 PM, Kevan Miller wrote: On Oct 24, 2011, at 1:10 AM, Rex Wang wrote: Hi Kevan, Have you reviewed my latest changes? If pass, I will start release process asap. Thanks Rex. I made a few changes. They'll need to be propagated to the license/notice for binaries… So that I'm clear -- everything looks good to me… --kevan -- Lei Wang (Rex) rwonly AT apache.org
Re: Review LICENSE and NOTICE of Geronimo 3.0-beta-1
Hi Kevan, Have you reviewed my latest changes? If pass, I will start release process asap. -Rex 2011/10/21 Rex Wang rwo...@gmail.com HI Kevan, I just commit the fix based on your comments. Thanks! For #1, Do you mean the one in framework\configs\karaf-framework\src\main\distribution\text ? I noticed that, and will copy them to there when the LICENSE is ok. 2011/10/21 Kevan Miller kevan.mil...@gmail.com Thanks Rex! A couple of points: 1) source LICENSE and the LICENSE file included in generated binaries (e.g. ) are not in sync. If I recall correctly, there are 2) there are artifacts that are missing from the source LICENSE. E.g.: * repository/com/sun/xml/bind/jaxb-xjc/2.2.3-1/jaxb-xjc-2.2.3-1.jar * repository/org/apache/wink/wink-common/1.1.3-incubating/wink-common-1.1.3-incubating.jar That's just from some random searches. There needs to be some concerted effort to identify all artifacts and insure they are listed. 3) W3C license for soap_encoding.xsd should refer to our source, not jar: The artifacts under the following folder are also covered by the above W3C license: soap_encoding_1_1.xsd in ./repository/org/apache/geronimo/modules/geronimo-webservices-builder/ Above should refer to plugins/webservices/geronimo-webservices-builder/src/main/resources/META-INF/schema/soap_encoding_1_1.xsd, I think. Not the jar. Looks like you didn't create this problem, but now something to fix... ;-) 4) I see that you've changed from listing explicit artifacts (e.g. repository/com/sun/xml/bind/jaxb-xjc/2.2.3-1/jaxb-xjc-2.2.3-1.jar) to folders/directories (e.g. repository/com/sun/xml/bind/jaxb-xjc/). I probably prefer the explicit names, but I don't know anything wrong with listing the directory/folder. Although it could lead to some imprecision... Using directory/folder names makes things simpler in subsequent releases (as version numbers change, etc) -- as long as we're inspecting for license/notice changes... If anyone is suitably motivated, an automated tool to help generate this information would certainly be very much appreciated by Geronimo and ASF community. The RAT incubator project would be a good home for this. I haven't been following the community. So, perhaps there has been some development there... 5) This is a change to the way we've handled dual licensed artifacts in the past -- we don't need to include both licenses in the LICENSE file and select one. We can simply the make our choice and only include the relevant LICENSE (e.g. for CDDL/GPL artifacts, we only need include the CDDL license -- no mention of GPL in license/notice files is needed). If I can get some time, I'll try and make these updates... --kevan On Oct 19, 2011, at 10:07 AM, Rex Wang wrote: Hi Devs, I just updated the LICENSE and NOTICE file of 3.0-beta-1 at revision: 1186228. Could anyone help reivew them so that we can avoid some issues in vote? regards, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Updated] (GERONIMO-5484) Create a document for JavaEE 6 sample application - EJBTimer
[ https://issues.apache.org/jira/browse/GERONIMO-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-5484: --- Issue Type: Task (was: Wish) Create a document for JavaEE 6 sample application - EJBTimer - Key: GERONIMO-5484 URL: https://issues.apache.org/jira/browse/GERONIMO-5484 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 3.0 The document should be as followed: # Application overview # Application content # Application implementation # Get the source code # Build the application # Deploy the application # Test the application -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Review LICENSE and NOTICE of Geronimo 3.0-beta-1
Thanks Kevan, At revision: 1186636, I prepared the RELEASE_NOTES and README for 3.0-beta-1, please review. -Rex 2011/10/20 Kevan Miller kevan.mil...@gmail.com Thanks Rex. I'll have a look. README and RELEASE_NOTES will need to be brought up to date... --kevan On Oct 19, 2011, at 10:07 AM, Rex Wang wrote: Hi Devs, I just updated the LICENSE and NOTICE file of 3.0-beta-1 at revision: 1186228. Could anyone help reivew them so that we can avoid some issues in vote? regards, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: Review LICENSE and NOTICE of Geronimo 3.0-beta-1
HI Kevan, I just commit the fix based on your comments. Thanks! For #1, Do you mean the one in framework\configs\karaf-framework\src\main\distribution\text ? I noticed that, and will copy them to there when the LICENSE is ok. 2011/10/21 Kevan Miller kevan.mil...@gmail.com Thanks Rex! A couple of points: 1) source LICENSE and the LICENSE file included in generated binaries (e.g. ) are not in sync. If I recall correctly, there are 2) there are artifacts that are missing from the source LICENSE. E.g.: * repository/com/sun/xml/bind/jaxb-xjc/2.2.3-1/jaxb-xjc-2.2.3-1.jar * repository/org/apache/wink/wink-common/1.1.3-incubating/wink-common-1.1.3-incubating.jar That's just from some random searches. There needs to be some concerted effort to identify all artifacts and insure they are listed. 3) W3C license for soap_encoding.xsd should refer to our source, not jar: The artifacts under the following folder are also covered by the above W3C license: soap_encoding_1_1.xsd in ./repository/org/apache/geronimo/modules/geronimo-webservices-builder/ Above should refer to plugins/webservices/geronimo-webservices-builder/src/main/resources/META-INF/schema/soap_encoding_1_1.xsd, I think. Not the jar. Looks like you didn't create this problem, but now something to fix... ;-) 4) I see that you've changed from listing explicit artifacts (e.g. repository/com/sun/xml/bind/jaxb-xjc/2.2.3-1/jaxb-xjc-2.2.3-1.jar) to folders/directories (e.g. repository/com/sun/xml/bind/jaxb-xjc/). I probably prefer the explicit names, but I don't know anything wrong with listing the directory/folder. Although it could lead to some imprecision... Using directory/folder names makes things simpler in subsequent releases (as version numbers change, etc) -- as long as we're inspecting for license/notice changes... If anyone is suitably motivated, an automated tool to help generate this information would certainly be very much appreciated by Geronimo and ASF community. The RAT incubator project would be a good home for this. I haven't been following the community. So, perhaps there has been some development there... 5) This is a change to the way we've handled dual licensed artifacts in the past -- we don't need to include both licenses in the LICENSE file and select one. We can simply the make our choice and only include the relevant LICENSE (e.g. for CDDL/GPL artifacts, we only need include the CDDL license -- no mention of GPL in license/notice files is needed). If I can get some time, I'll try and make these updates... --kevan On Oct 19, 2011, at 10:07 AM, Rex Wang wrote: Hi Devs, I just updated the LICENSE and NOTICE file of 3.0-beta-1 at revision: 1186228. Could anyone help reivew them so that we can avoid some issues in vote? regards, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Apache Geronimo Bundle commons-httpclient 3.1_1
+1 2011/10/15 Ivan xhh...@gmail.com Hi, let's vote for commons-httpclient 3.1_1 The reason for this vote is to include a fix for configurable header options. The components for voting : https://repository.apache.org/content/repositories/orgapachegeronimo-070/org/apache/geronimo/bundles/commons-httpclient/3.1_1/commons-httpclient-3.1_1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-070/org/apache/geronimo/bundles/commons-httpclient/3.1_1/commons-httpclient-3.1_1-source-release.zip The stage repository : https://repository.apache.org/content/repositories/orgapachegeronimo-070 The source tag : https://svn.apache.org/repos/asf/geronimo/bundles/tags/commons-httpclient-3.1_1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Ivan -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Updated] (GERONIMO-5939) Support OBR resolution during bundle install
[ https://issues.apache.org/jira/browse/GERONIMO-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-5939: --- Fix Version/s: 3.0 Support OBR resolution during bundle install Key: GERONIMO-5939 URL: https://issues.apache.org/jira/browse/GERONIMO-5939 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0-M1 Reporter: Jarek Gawor Assignee: Rex Wang Fix For: 3.0 Attachments: GERONIMO-5939-core.patch, GERONIMO_5939_core_modify.patch, GERONIMO_5939_core_modify2.patch, GeronimoOBR_5939.patch When installing an individual bundle (via the admin console, command line or shell) provide an option to perform OBR resolution to install the dependent bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6066) OpenEJB 4.0.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/GERONIMO-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6066. Resolution: Fixed OpenEJB 4.0.0-SNAPSHOT -- Key: GERONIMO-6066 URL: https://issues.apache.org/jira/browse/GERONIMO-6066 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: David Blevins Fix For: 3.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6066) OpenEJB 4.0.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/GERONIMO-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-6066. -- close it OpenEJB 4.0.0-SNAPSHOT -- Key: GERONIMO-6066 URL: https://issues.apache.org/jira/browse/GERONIMO-6066 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: David Blevins Fix For: 3.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6070) Axis2 1.6.1_1-SNAPSHOT
[ https://issues.apache.org/jira/browse/GERONIMO-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6070. Resolution: Fixed Axis2 1.6.1_1-SNAPSHOT -- Key: GERONIMO-6070 URL: https://issues.apache.org/jira/browse/GERONIMO-6070 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: David Blevins Assignee: Rex Wang Fix For: 3.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6070) Axis2 1.6.1_1-SNAPSHOT
[ https://issues.apache.org/jira/browse/GERONIMO-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-6070. -- Axis2 1.6.1_1-SNAPSHOT -- Key: GERONIMO-6070 URL: https://issues.apache.org/jira/browse/GERONIMO-6070 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: David Blevins Assignee: Rex Wang Fix For: 3.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6061) Geronimo trunk SNAPSHOT dependencies for 3.0-beta-1
[ https://issues.apache.org/jira/browse/GERONIMO-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6061. Resolution: Fixed All has been released Geronimo trunk SNAPSHOT dependencies for 3.0-beta-1 --- Key: GERONIMO-6061 URL: https://issues.apache.org/jira/browse/GERONIMO-6061 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: David Blevins Assignee: Rex Wang Fix For: 3.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6061) Geronimo trunk SNAPSHOT dependencies for 3.0-beta-1
[ https://issues.apache.org/jira/browse/GERONIMO-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-6061: --- Summary: Geronimo trunk SNAPSHOT dependencies for 3.0-beta-1 (was: Geronimo 3.0 trunk SNAPSHOT dependencies) Geronimo trunk SNAPSHOT dependencies for 3.0-beta-1 --- Key: GERONIMO-6061 URL: https://issues.apache.org/jira/browse/GERONIMO-6061 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: David Blevins Assignee: Rex Wang Fix For: 3.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6061) Geronimo trunk SNAPSHOT dependencies for 3.0-beta-1
[ https://issues.apache.org/jira/browse/GERONIMO-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-6061. -- Geronimo trunk SNAPSHOT dependencies for 3.0-beta-1 --- Key: GERONIMO-6061 URL: https://issues.apache.org/jira/browse/GERONIMO-6061 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Reporter: David Blevins Assignee: Rex Wang Fix For: 3.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6059) New look and feel of Geronimo 3.0 admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6059. Resolution: Fixed New look and feel of Geronimo 3.0 admin console --- Key: GERONIMO-6059 URL: https://issues.apache.org/jira/browse/GERONIMO-6059 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 Attachments: Geronimo-3.0-New-UI-Proposal-advanced-navigator.png, Geronimo-3.0-New-UI-Proposal-basic-navigator.png, Step-1-detail-improvements.PNG, Step-1-login-page.PNG, Step-1-welcome-page.PNG, Step-2-New-UI-Console-welcome.PNG, Step-2-New-UI-Geronimo-welcome.PNG, Step-2-New-UI-Login.PNG, Step-2-New-UI-Portlets.PNG, old-cosole-full-opened-navigation-tree.png Geronimo 3.0 is milestone release that contains a lot of new features. So I think it's time to change the UI design of admin console to provide user a brand new look and feel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6059) New look and feel of Geronimo 3.0 admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-6059. -- No more development. close this jira. New look and feel of Geronimo 3.0 admin console --- Key: GERONIMO-6059 URL: https://issues.apache.org/jira/browse/GERONIMO-6059 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 Attachments: Geronimo-3.0-New-UI-Proposal-advanced-navigator.png, Geronimo-3.0-New-UI-Proposal-basic-navigator.png, Step-1-detail-improvements.PNG, Step-1-login-page.PNG, Step-1-welcome-page.PNG, Step-2-New-UI-Console-welcome.PNG, Step-2-New-UI-Geronimo-welcome.PNG, Step-2-New-UI-Login.PNG, Step-2-New-UI-Portlets.PNG, old-cosole-full-opened-navigation-tree.png Geronimo 3.0 is milestone release that contains a lot of new features. So I think it's time to change the UI design of admin console to provide user a brand new look and feel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Review LICENSE and NOTICE of Geronimo 3.0-beta-1
** Hi Devs, I just updated the LICENSE and NOTICE file of 3.0-beta-1 at revision: 1186228. Could anyone help reivew them so that we can avoid some issues in vote? regards, -- Lei Wang (Rex) rwonly AT apache.org
Re: 3.0-beta build failure?
I have a hudson in my local machine to do nightly build, and the latest build in last night dont have problems.. 2011/10/20 Kevan Miller kevan.mil...@gmail.com Trying to verify license information, but I'm running into a build failure. Anyone else having problems? --- T E S T S --- Running org.apache.geronimo.axis.builder.WSDLMapTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.303 sec Running org.apache.geronimo.axis.builder.ServiceReferenceTest Tests run: 4, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 1.38 sec FAILURE! Results : Tests in error: testBuildOperationInfo(org.apache.geronimo.axis.builder.ServiceReferenceTest) testBuildFullServiceProxy(org.apache.geronimo.axis.builder.ServiceReferenceTest) testBuildBookQuoteProxy(org.apache.geronimo.axis.builder.ServiceReferenceTest) ... From plugins/axis/geronimo-axis-builder/target/surefire-reports/org.apache.geronimo.axis.builder.ServiceReferenceTest.txt: Tests run: 4, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 1.379 sec FAILURE! testBuildOperationInfo(org.apache.geronimo.axis.builder.ServiceReferenceTest) Time elapsed: 0.262 sec ERROR! java.lang.ExceptionInInitializerError at org.apache.axis.constants.Enum.clinit(Enum.java:35) at org.apache.geronimo.axis.builder.ServiceReferenceTest.buildOperationInfoForMockOperation(ServiceReferenceTest.java:252) at org.apache.geronimo.axis.builder.ServiceReferenceTest.testBuildOperationInfo(ServiceReferenceTest.java:162) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:79) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.InstantiationException (Caused by java.lang.InstantiationException) at org.apache.commons.logging.LogFactory.createFactory(LogFactory.java:1276) at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:1065) at java.security.AccessController.doPrivileged(Native Method) at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:1062) at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:612) at org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:44) at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:40) at org.apache.axis.components.logger.LogFactory.clinit(LogFactory.java:32) ... 26 more Caused by: java.lang.InstantiationException at sun.reflect.InstantiationExceptionConstructorAccessorImpl.newInstance(InstantiationExceptionConstructorAccessorImpl.java:30) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.apache.commons.logging.LogFactory.createFactory(LogFactory.java:1160) ... 34 more testBuildFullServiceProxy(org.apache.geronimo.axis.builder.ServiceReferenceTest) Time elapsed: 0.567 sec ERROR! java.lang.NoClassDefFoundError:
Could we remove openejb-feature-3.0-SNAPSHOT-features.xml?
I found a karaf feature definition openejb-feature-3.0-SNAPSHOT-features.xml in plugins\openejb\openejb\src\main\filtered-resources\repository\org\apache\geronimo\features\openejb-feature\3.0-SNAPSHOT. Do we need this in current geronimo runtime? If not, I want to remove it because there is a hard-coded SNAPSHOT in the path.. -- Lei Wang (Rex) rwonly AT apache.org
Re: svn commit: r1184867 - in /geronimo/server/branches/3.0-beta: framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/ framework/buildsupport/geronimo-plugin-arch
OK. However hope we won't need beta-2 :-) -Rex 2011/10/17 Shawn Jiang genspr...@gmail.com Should we name this release to 3.0-beta-1 just like what openejb did for 4.0-beta-1 ? thoughts ? -- Forwarded message -- From: rwo...@apache.org Date: Mon, Oct 17, 2011 at 12:54 AM Subject: svn commit: r1184867 - in /geronimo/server/branches/3.0-beta: framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/ framework/buildsupport/geronimo-plugin-archetype/src/main/resources/archetype-resources/ plugins/re... To: s...@geronimo.apache.org Author: rwonly Date: Sun Oct 16 16:54:36 2011 New Revision: 1184867 URL: http://svn.apache.org/viewvc?rev=1184867view=rev Log: update dep:version3.0-SNAPSHOT/dep:version and geronimoVersion3.0-SNAPSHOT/geronimoVersion to 3.0-beta-SNAPSHOT in all xml files Modified: geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.sample.xml geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.xml geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-plugin-archetype/src/main/resources/archetype-resources/pom.sample.xml geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-plugin-archetype/src/main/resources/archetype-resources/pom.xml geronimo/server/branches/3.0-beta/plugins/remote-deploy/geronimo-remote-deploy/src/main/webapp/WEB-INF/geronimo-web.xml geronimo/server/branches/3.0-beta/plugins/welcome/geronimo-welcome/src/main/webapp/WEB-INF/geronimo-web.xml geronimo/server/branches/3.0-beta/plugins/welcome/welcome-jetty-server/pom.sample.xml geronimo/server/branches/3.0-beta/plugins/welcome/welcome-jetty-server/pom.xml geronimo/server/branches/3.0-beta/plugins/welcome/welcome-tomcat-server/pom.sample.xml geronimo/server/branches/3.0-beta/plugins/welcome/welcome-tomcat-server/pom.xml Modified: geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.sample.xml URL: http://svn.apache.org/viewvc/geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.sample.xml?rev=1184867r1=1184866r2=1184867view=diff == --- geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.sample.xml (original) +++ geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.sample.xml Sun Oct 16 16:54:36 2011 @@ -24,7 +24,7 @@ properties !-- This may be helpful in selecting the desired geronimo version -- -geronimoVersion3.0-SNAPSHOT/geronimoVersion +geronimoVersion3.0-beta-SNAPSHOT/geronimoVersion /properties Modified: geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.xml URL: http://svn.apache.org/viewvc/geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.xml?rev=1184867r1=1184866r2=1184867view=diff == --- geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.xml (original) +++ geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-assembly-archetype/src/main/resources/archetype-resources/pom.xml Sun Oct 16 16:54:36 2011 @@ -24,7 +24,7 @@ properties !-- This may be helpful in selecting the desired geronimo version -- -geronimoVersion3.0-SNAPSHOT/geronimoVersion +geronimoVersion3.0-beta-SNAPSHOT/geronimoVersion /properties Modified: geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-plugin-archetype/src/main/resources/archetype-resources/pom.sample.xml URL: http://svn.apache.org/viewvc/geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-plugin-archetype/src/main/resources/archetype-resources/pom.sample.xml?rev=1184867r1=1184866r2=1184867view=diff == --- geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-plugin-archetype/src/main/resources/archetype-resources/pom.sample.xml (original) +++ geronimo/server/branches/3.0-beta/framework/buildsupport/geronimo-plugin-archetype/src/main/resources/archetype-resources/pom.sample.xml Sun Oct 16 16:54:36 2011 @@ -24,7 +24,7 @@ properties !-- This may be helpful in selecting the desired geronimo version -- -geronimoVersion3.0-SNAPSHOT/geronimoVersion +
remove the 2 eba assemblies?
We don't build the 2 eba assemblies for a while. !-- modulegeronimo-jetty8-eba/module -- !-- modulegeronimo-tomcat7-eba/module -- How about remove them? -- Lei Wang (Rex) rwonly AT apache.org
Re: JCDI failure issues
+1
2011/10/13 Ivan xhh...@gmail.com
Move this thread to dev list since JCDI TCK is in public.
-- Forwarded message --
From: Ivan xhh...@gmail.com
Date: 2011/10/13
Subject: Re: 3.0 Web Profile Standalone - 3.0 Web Profile JCDI Runtest
Results
To: Geronimo Certification Effort geronimo-...@geronimo.apache.org
I just went though some parts of PersistenceUnit scope, and think that the
codes there should be refract a bit.
a. the PURefBuilder first use the current configuration to search the
matched GBean, then it will use another method in the Configuration to
search the parents. That looks fine, while the query condition seems not
re-created in the next query.
b. For the EJB in WAR, it now shared the same configuration with the
wrapped war package, so while creating the query condition, the values from
EJBModule names are included, and Rex pointed it out that is why the
reference is not found.
I am thinking we could use the logic below to search the PU, thoughts ?
do
{
create query condition based on the current module
search PU in the configuration linked to current module
module = module.getParent();
} while (module !=null)
2011/10/12 Rex Wang rwo...@gmail.com
sorry typo
not EjbDeploymentBuilder's line 209,
it is PersistenceRefBuilder's line 209...
-Rex
2011/10/12 Rex Wang rwo...@gmail.com
The latest progress:
1. For the testInjectionIntoWebServiceEndpoint test, Ivan reminder me
that might be caused by the java home is pointed to a jre. After change to
jdk, the test passed in my local machine.
2. So, all the rest failures are the persistence ones.
The test deploy a war which contains persistence.xml and ejbs.
So, the persistent unit builder add the following gbean data to the
earcontext:
default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war?J2EEApplication=null,PersistenceUnitModule=WEB-INF/classes/,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war,j2eeType=PersistenceUnit,name=test=org.apache.geronimo.gbean.GBeanData@d1a87
but in the EjbDeploymentBuilder's line 209,
It uses a pattern as following to query the persistent unit gbean data:
[?*EJBModule=.*
,J2EEApplication=null,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318411456796/war,j2eeType=PersistenceUnit#org.apache.geronimo.persistence.PersistenceUnitGBean]
We can see it contains a constraint *EJBModule=.*, which cause the
query return empty. That lead the DeploymentException(No default
PersistenceUnit specified, and none located);
The root cause is located, any insights how to correct it?
-Rex
2011/10/12 Rex Wang rwo...@gmail.com
Some initial investigations:
There are 8 failures in AHP.
6 of them are deployment failures, and 2 of them are assertion errors.
In my local machine, only the 6 deployment failures can be reproduced.
They are:
- testInjectionIntoWebServiceEndpoint
- testBeanTypesAndBindingTypesOfPersistenceContext
- testInjectionOfPersistenceContext
- testInjectionOfPersistenceUnit
- testPassivationOfPersistenceContext
- testPassivationOfPersistenceUnit
And the last five tests deploy
org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest.war
, which can be reproduce when I deploy the war in console. I am still
digging into the root cause.
But the first test, testInjectionIntoWebServiceEndpoint, deploys
org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest.war,
which I can deploy successfully in console. The exception stack is:
[org.apache.geronimo.testharness.GeronimoConnector] : Deploying
org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest.war
Deployer operation failed: Unable to generate the wsdl file using wsgen.
org.apache.geronimo.common.DeploymentException: Unable to generate the
wsdl file using wsgen.
at
org.apache.geronimo.jaxws.sun.tools.WsdlGenerator.generateWsdl(WsdlGenerator.java:182)
at
org.apache.geronimo.jaxws.sun.tools.SunWsdlGenerator.generateWsdl(SunWsdlGenerator.java:34)
at
org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.java:153)
at
org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSServiceBuilder.java:321)
at
org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:637)
at
org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174)
at
org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:763)
at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255
[jira] [Created] (GERONIMO-6190) Improve the summary list in the web console login page
Improve the summary list in the web console login page -- Key: GERONIMO-6190 URL: https://issues.apache.org/jira/browse/GERONIMO-6190 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Reporter: Rex Wang Fix For: 3.0 please see the screenshot in attachment. Now we support more feature/programming model in geronimo 3.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6190) Improve the summary list in the web console login page
[ https://issues.apache.org/jira/browse/GERONIMO-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-6190: --- Attachment: login-page.PNG Improve the summary list in the web console login page -- Key: GERONIMO-6190 URL: https://issues.apache.org/jira/browse/GERONIMO-6190 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Rex Wang Fix For: 3.0 Attachments: login-page.PNG please see the screenshot in attachment. Now we support more feature/programming model in geronimo 3.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6191) can not query the persistence unit gbean when ejb is in a war
can not query the persistence unit gbean when ejb is in a war - Key: GERONIMO-6191 URL: https://issues.apache.org/jira/browse/GERONIMO-6191 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: persistence Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 When deploy a war which contains persistence.xml and ejbs, the persistent unit builder add the following gbean data to the earcontext: default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war?J2EEApplication=null,PersistenceUnitModule=WEB-INF/classes/,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war,j2eeType=PersistenceUnit,name=test=org.apache.geronimo.gbean.GBeanData@d1a87 but in the EjbDeploymentBuilder's line 209, It uses a pattern as following to query the persistent unit gbean data: [?EJBModule=.,J2EEApplication=null,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318411456796/war,j2eeType=PersistenceUnit#org.apache.geronimo.persistence.PersistenceUnitGBean] We can see it contains a constraint EJBModule=., which cause the query return empty. That lead the DeploymentException(No default PersistenceUnit specified, and none located); This is because the ejb module and the war module share the same earcontext and the configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: JCDI failure issues
I commit a fix based on Ivan's suggestion at revision: 1182804
Let's wait the next tck results.
-Rex
2011/10/13 Rex Wang rwo...@gmail.com
+1
2011/10/13 Ivan xhh...@gmail.com
Move this thread to dev list since JCDI TCK is in public.
-- Forwarded message --
From: Ivan xhh...@gmail.com
Date: 2011/10/13
Subject: Re: 3.0 Web Profile Standalone - 3.0 Web Profile JCDI Runtest
Results
To: Geronimo Certification Effort geronimo-...@geronimo.apache.org
I just went though some parts of PersistenceUnit scope, and think that the
codes there should be refract a bit.
a. the PURefBuilder first use the current configuration to search the
matched GBean, then it will use another method in the Configuration to
search the parents. That looks fine, while the query condition seems not
re-created in the next query.
b. For the EJB in WAR, it now shared the same configuration with the
wrapped war package, so while creating the query condition, the values from
EJBModule names are included, and Rex pointed it out that is why the
reference is not found.
I am thinking we could use the logic below to search the PU, thoughts ?
do
{
create query condition based on the current module
search PU in the configuration linked to current module
module = module.getParent();
} while (module !=null)
2011/10/12 Rex Wang rwo...@gmail.com
sorry typo
not EjbDeploymentBuilder's line 209,
it is PersistenceRefBuilder's line 209...
-Rex
2011/10/12 Rex Wang rwo...@gmail.com
The latest progress:
1. For the testInjectionIntoWebServiceEndpoint test, Ivan reminder me
that might be caused by the java home is pointed to a jre. After change to
jdk, the test passed in my local machine.
2. So, all the rest failures are the persistence ones.
The test deploy a war which contains persistence.xml and ejbs.
So, the persistent unit builder add the following gbean data to the
earcontext:
default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war?J2EEApplication=null,PersistenceUnitModule=WEB-INF/classes/,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war,j2eeType=PersistenceUnit,name=test=org.apache.geronimo.gbean.GBeanData@d1a87
but in the EjbDeploymentBuilder's line 209,
It uses a pattern as following to query the persistent unit gbean data:
[?*EJBModule=.*
,J2EEApplication=null,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318411456796/war,j2eeType=PersistenceUnit#org.apache.geronimo.persistence.PersistenceUnitGBean]
We can see it contains a constraint *EJBModule=.*, which cause the
query return empty. That lead the DeploymentException(No default
PersistenceUnit specified, and none located);
The root cause is located, any insights how to correct it?
-Rex
2011/10/12 Rex Wang rwo...@gmail.com
Some initial investigations:
There are 8 failures in AHP.
6 of them are deployment failures, and 2 of them are assertion errors.
In my local machine, only the 6 deployment failures can be reproduced.
They are:
- testInjectionIntoWebServiceEndpoint
- testBeanTypesAndBindingTypesOfPersistenceContext
- testInjectionOfPersistenceContext
- testInjectionOfPersistenceUnit
- testPassivationOfPersistenceContext
- testPassivationOfPersistenceUnit
And the last five tests deploy
org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest.war
, which can be reproduce when I deploy the war in console. I am still
digging into the root cause.
But the first test, testInjectionIntoWebServiceEndpoint, deploys
org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest.war,
which I can deploy successfully in console. The exception stack is:
[org.apache.geronimo.testharness.GeronimoConnector] : Deploying
org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest.war
Deployer operation failed: Unable to generate the wsdl file using
wsgen.
org.apache.geronimo.common.DeploymentException: Unable to generate the
wsdl file using wsgen.
at
org.apache.geronimo.jaxws.sun.tools.WsdlGenerator.generateWsdl(WsdlGenerator.java:182)
at
org.apache.geronimo.jaxws.sun.tools.SunWsdlGenerator.generateWsdl(SunWsdlGenerator.java:34)
at
org.apache.geronimo.axis2.builder.Axis2Builder.initialize(Axis2Builder.java:153)
at
org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.configurePOJO(JAXWSServiceBuilder.java:321)
at
org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:637)
at
org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174
[jira] [Commented] (GERONIMO-6191) can not query the persistence unit gbean when ejb is in a war
[ https://issues.apache.org/jira/browse/GERONIMO-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13126525#comment-13126525 ] Rex Wang commented on GERONIMO-6191: commit the fix at revision: 1182804 can not query the persistence unit gbean when ejb is in a war - Key: GERONIMO-6191 URL: https://issues.apache.org/jira/browse/GERONIMO-6191 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: persistence Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 When deploy a war which contains persistence.xml and ejbs, the persistent unit builder add the following gbean data to the earcontext: default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war?J2EEApplication=null,PersistenceUnitModule=WEB-INF/classes/,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318412097703/war,j2eeType=PersistenceUnit,name=test=org.apache.geronimo.gbean.GBeanData@d1a87 but in the EjbDeploymentBuilder's line 209, It uses a pattern as following to query the persistent unit gbean data: [?EJBModule=.,J2EEApplication=null,WebModule=default/org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest/1318411456796/war,j2eeType=PersistenceUnit#org.apache.geronimo.persistence.PersistenceUnitGBean] We can see it contains a constraint EJBModule=., which cause the query return empty. That lead the DeploymentException(No default PersistenceUnit specified, and none located); This is because the ejb module and the war module share the same earcontext and the configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Geronimo Forked Aries Blueprint 0.3.0.1 (1st try)
Vote passed with the following +1s from:
Shawn Jiang,
Ivan,
Forrest Xia,
viola,
and me.
There is no -1 or +0, I will release Geronimo Forked Aries Blueprint 0.3.0.1
soon.
thanks
-Rex
2011/9/26 Rex Wang rwo...@gmail.com
Hi devs,
Please vote for Geronimo Forked Aries Blueprint 0.3.0.1
This release bases on Apache Aries Blueprint 0.3 tag, and includes the
fix of ARIES-727 support syntax : ${a+b} in blueprint
The components up for vote is:
https://repository.apache.org/content/repositories/orgapachegeronimo-102/org/apache/geronimo/ext/aries/blueprint/blueprint/0.3.0.1/blueprint-0.3.0.1-source-release.zip
Staging repo is:
https://repository.apache.org/content/repositories/orgapachegeronimo-102
The tag has created at:
http://svn.apache.org/repos/asf/geronimo/external/tags/blueprint-0.3.0.1/
Vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
--
Lei Wang (Rex)
rwonly AT apache.org
--
Lei Wang (Rex)
rwonly AT apache.org
Re: svn commit: r1179831 - in /geronimo/server/trunk: framework/modules/geronimo-pax-logging/pom.xml framework/modules/geronimo-pax-logging/src/main/java/org/ops4j/ pom.xml
Hi Jarek,
This added a new SNAPSHOT dependency to trunk. Will pax-logging release
soon? Otherwise I have to revert this change so that I can start 3.0-beta
release. After 3.0-beta is branched, will re-apply this.
-Rex
2011/10/7 ga...@apache.org
Author: gawor
Date: Thu Oct 6 20:30:16 2011
New Revision: 1179831
URL: http://svn.apache.org/viewvc?rev=1179831view=rev
Log:
GERONIMO-6184: Updated PAX Logging to pick upi latest changes and fixes
Removed:
geronimo/server/trunk/framework/modules/geronimo-pax-logging/src/main/java/org/ops4j/
Modified:
geronimo/server/trunk/framework/modules/geronimo-pax-logging/pom.xml
geronimo/server/trunk/pom.xml
Modified:
geronimo/server/trunk/framework/modules/geronimo-pax-logging/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-pax-logging/pom.xml?rev=1179831r1=1179830r2=1179831view=diff
==
--- geronimo/server/trunk/framework/modules/geronimo-pax-logging/pom.xml
(original)
+++ geronimo/server/trunk/framework/modules/geronimo-pax-logging/pom.xml
Thu Oct 6 20:30:16 2011
@@ -63,50 +63,26 @@
Embed-Dependencypax-logging-service;inline=true/Embed-Dependency
Import-Package
-com.ibm.uvm.tools;resolution:=optional,
-com.sun.jdmk.comm;resolution:=optional,
-javax.jmdns;resolution:=optional,
-javax.jms;resolution:=optional,
-javax.mail;resolution:=optional,
-javax.mail.internet;resolution:=optional,
-javax.management;resolution:=optional,
-javax.naming;resolution:=optional,
-javax.swing;resolution:=optional,
-javax.swing.border;resolution:=optional,
-javax.swing.event;resolution:=optional,
-javax.swing.table;resolution:=optional,
-javax.swing.text;resolution:=optional,
-javax.swing.tree;resolution:=optional,
-
org.osgi.service.event;resolution:=optional;version=[1.0.0,2.0.0),
+com.*;resolution:=optional,
+javax.xml.*,
+javax.*;resolution:=optional,
-javax.xml.parsers,
-
org.apache.avalon.framework.logger;version=4.3.0,
-org.apache.commons.logging;version=1.1.0,
-org.apache.juli.logging;version=1.0.0,
org.knopflerfish.service.log;provider=paxlogging;version=[1.1.0,2.0.0),
org.ops4j.pax.logging;version=[0.9.5,2.0.0),
-org.ops4j.pax.logging.avalon;version=1.5.0,
-org.ops4j.pax.logging.slf4j;version=1.5.0,
-
org.ops4j.pax.logging.spi;provider=paxlogging;version=1.5.0,
org.osgi.framework;version=[1.0.0,2.0.0),
org.osgi.service.cm;version=[1.0.0,2.0.0),
+
org.osgi.service.event;version=[1.0.0,2.0.0);resolution:=optional,
org.osgi.service.log;version=[1.3.0,2.0.0),
org.osgi.util.tracker;version=[1.3.0,2.0.0),
-org.slf4j;version=1.5.0,
-org.w3c.dom,
-org.xml.sax,
-org.xml.sax.helpers,
+
*
/Import-Package
+
Export-Package
org.apache.geronimo.logging,
org.ops4j.pax.logging.spi;provider=paxlogging;version=${pax.logging.version}
/Export-Package
Bundle-Activatororg.apache.geronimo.logging.impl.LoggingServiceActivator/Bundle-Activator
-Include-Resource
- {maven-resources},
-
org/ops4j/pax/logging/service/internal/JdkHandler.class=target/classes/org/ops4j/pax/logging/service/internal/JdkHandler.class
-/Include-Resource
/instructions
/configuration
/plugin
Modified: geronimo/server/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=1179831r1=1179830r2=1179831view=diff
==
--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Thu Oct 6 20:30:16 2011
@@ -85,7 +85,7 @@
jaxbImplVersion2.2.3-1_1/jaxbImplVersion
monitoringConsoleVersion${project.version}/monitoringConsoleVersion
-pax.logging.version1.6.1/pax.logging.version
+pax.logging.version1.6.4-SNAPSHOT/pax.logging.version
[jira] [Resolved] (GERONIMO-4668) Parse XML error after deploying a EJB security jar
[ https://issues.apache.org/jira/browse/GERONIMO-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4668. Resolution: Duplicate Fix Version/s: 2.1.8 Parse XML error after deploying a EJB security jar -- Key: GERONIMO-4668 URL: https://issues.apache.org/jira/browse/GERONIMO-4668 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.6, 2.1.7, 2.2, 2.2.1 Environment: OS:suse 10 Sp2 64bit Reporter: viola.lu Fix For: 2.1.8 Attachments: EJBSecurity.zip, openejb-jar.xml 1.Copy attached dw_groups and dw_user files to $server_home/var/security 2.Deploy attached security realm plan xml to server 3.Deploy attached ejb run as jar to server, parse error popsup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6176) upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec
[ https://issues.apache.org/jira/browse/GERONIMO-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6176. Resolution: Fixed upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec - Key: GERONIMO-6176 URL: https://issues.apache.org/jira/browse/GERONIMO-6176 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Affects Versions: 2.1.7 Reporter: Rex Wang Assignee: Rex Wang Fix For: 2.1.8 upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-4861) Deployment Plan XML Parsing - Not add generated namespace names to closing tags
[
https://issues.apache.org/jira/browse/GERONIMO-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang resolved GERONIMO-4861.
Resolution: Fixed
Fix Version/s: 2.1.8
Shawn upgraded jaxb to 2.1.13, so this issue should be resolved.
Deployment Plan XML Parsing - Not add generated namespace names to closing
tags
---
Key: GERONIMO-4861
URL: https://issues.apache.org/jira/browse/GERONIMO-4861
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: OpenEJB
Affects Versions: 2.1.6, 2.1.7, 2.2, 2.2.1
Reporter: Quintin Beukes
Priority: Minor
Fix For: 2.1.8
When creating a deployment plan and using more than one namespace, but not
implicitly specifying the namespaces in all elements, the namespace names are
added to the temporary XML file. Though it doesn't add them correctly. I
included my original openejb-jar.xml, the error I get through deploy.sh, and
the generated XML file (which I reformatted to make it more readable).
You will notice the problem are in the last 2 closing tags of the ns7 (ie.
security-2.0) namespace. The ns7 namespace prefix wasn't added to them, and
this generates the validator error.
{code:xml|title=original-openejb-jar.xml}
?xml version=1.0 encoding=UTF-8?
openejb-jar xmlns=http://openejb.apache.org/xml/ns/openejb-jar-2.2;
xmlns:naming=http://geronimo.apache.org/xml/ns/naming-1.2;
xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0;
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
dep:environment
dep:moduleId
dep:groupIdkms/dep:groupId
dep:artifactIdKMSPlatform-ejb/dep:artifactId
dep:version1.0/dep:version
dep:typejar/dep:type
/dep:moduleId
dep:dependencies
dep:dependency
dep:groupIdconsole.dbpool/dep:groupId
dep:artifactIdjdbc_kmsPool/dep:artifactId
dep:version1.0/dep:version
dep:typerar/dep:type
/dep:dependency
dep:dependency
dep:groupIdconsole.realm/dep:groupId
dep:artifactIdKMSRealm/dep:artifactId
dep:version1.0/dep:version
dep:typecar/dep:type
/dep:dependency
dep:dependency
dep:groupIdorg.springframework/dep:groupId
dep:artifactIdspring-core/dep:artifactId
dep:version2.5.6/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdorg.springframework/dep:groupId
dep:artifactIdspring-beans/dep:artifactId
dep:version2.5.6/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdorg.springframework/dep:groupId
dep:artifactIdspring-context/dep:artifactId
dep:version2.5.6/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdorg.slf4j/dep:groupId
dep:artifactIdslf4j-api/dep:artifactId
dep:version1.5.5/dep:version
dep:typejar/dep:type
/dep:dependency
!-- hibernate follows --
dep:dependency
dep:groupIdhibernate/dep:groupId
dep:artifactIdcore/dep:artifactId
dep:version3.3/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdhibernate/dep:groupId
dep:artifactIdannotations/dep:artifactId
dep:version3.4/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdhibernate/dep:groupId
dep:artifactIdantlr/dep:artifactId
dep:version2.7.6/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdhibernate/dep:groupId
dep:artifactIdcommons-annotations/dep:artifactId
dep:version3.4/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdhibernate/dep:groupId
dep:artifactIdcommons-collections/dep:artifactId
dep:version3.1/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdhibernate/dep:groupId
dep:artifactIddom4j/dep:artifactId
dep:version1.6.1/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdhibernate/dep:groupId
dep:artifactIdentitymanager/dep:artifactId
dep:version3.4/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
dep:groupIdhibernate/dep:groupId
dep:artifactIdjavassist/dep:artifactId
dep:version3.9.0.GA/dep:version
dep:typejar/dep:type
/dep:dependency
dep:dependency
Re: Geronimo 3.0-beta Release Status
2011/9/29 Forrest Xia forres...@gmail.com Rex, Seems we want to wait a little bit longer(for openejb 4.0.0 release) to branch the current trunk out to 3.0-beta in branches, that properly happens around first half of October, right? Yes, The only dependency - OpenEJB 4.0.0 has not started release yet. We have to wait.. -Rex Frank, I think 3.0-beta will be the apache one aligned with CE 3.0. Forrest On Mon, Sep 26, 2011 at 8:22 PM, pif frank.pien...@googlemail.com wrote: How does the Geronimo 3.0-beta relate todays IBM annoucement? http://www-01.ibm.com/support/docview.wss?uid=swg21515968 WASCE v3.0.0.0 is now available It provides the following new features and enhancements and is certified for Java EE 6 Profile: 1) Based on Apache Geronimo 3.0 and other open source projects https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14686485 the change-list makes it clear http://publib.boulder.ibm.com/wasce/changes/3000/CHANGES.txt Apache Geronimo Server 3.0-r1163516 Apache Tomcat 7.0.19.1 Apache OpenEJB 4.0.0-r1160123 Apache OpenJPA 2.1.1 Apache MyFaces 2.0.8 Apache karaf 2.2.1 Apache aries 0.2.1 Apache openwebbeans 1.1.1-r1160102 Apache axis2 1.6.1-r1149666 equinox 3.7.1.R37x_v20110808_1106 tranql 1.7 Will there be an offical Apacher pendant? Thanks Frank -- View this message in context: http://apache-geronimo.328035.n3.nabble.com/Geronimo-3-0-beta-Release-Status-tp3280463p3369065.html Sent from the Development mailing list archive at Nabble.com. -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Created] (GERONIMO-6176) upgrade jaxb to 2.1.13 and use geronimio jaxb 2.1 spec
upgrade jaxb to 2.1.13 and use geronimio jaxb 2.1 spec -- Key: GERONIMO-6176 URL: https://issues.apache.org/jira/browse/GERONIMO-6176 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: specs Affects Versions: 2.1.7 Reporter: Rex Wang Assignee: Rex Wang Fix For: 2.1.8 upgrade jaxb to 2.1.13 and use geronimio jaxb 2.1 spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6176) upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec
[ https://issues.apache.org/jira/browse/GERONIMO-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-6176: --- Summary: upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec (was: upgrade jaxb to 2.1.13 and use geronimio jaxb 2.1 spec) upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec - Key: GERONIMO-6176 URL: https://issues.apache.org/jira/browse/GERONIMO-6176 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Affects Versions: 2.1.7 Reporter: Rex Wang Assignee: Rex Wang Fix For: 2.1.8 upgrade jaxb to 2.1.13 and use geronimio jaxb 2.1 spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6176) upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec
[ https://issues.apache.org/jira/browse/GERONIMO-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-6176: --- Description: upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec (was: upgrade jaxb to 2.1.13 and use geronimio jaxb 2.1 spec) upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec - Key: GERONIMO-6176 URL: https://issues.apache.org/jira/browse/GERONIMO-6176 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Affects Versions: 2.1.7 Reporter: Rex Wang Assignee: Rex Wang Fix For: 2.1.8 upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6176) upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec
[ https://issues.apache.org/jira/browse/GERONIMO-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13115303#comment-13115303 ] Rex Wang commented on GERONIMO-6176: Shawn committed the fix in rev 1159269 rev 1164330 upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec - Key: GERONIMO-6176 URL: https://issues.apache.org/jira/browse/GERONIMO-6176 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Affects Versions: 2.1.7 Reporter: Rex Wang Assignee: Rex Wang Fix For: 2.1.8 upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6176) upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec
[ https://issues.apache.org/jira/browse/GERONIMO-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13115304#comment-13115304 ] Rex Wang commented on GERONIMO-6176: exclude jaxb-api from jaxb-impl dependency in rev 1176231 upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec - Key: GERONIMO-6176 URL: https://issues.apache.org/jira/browse/GERONIMO-6176 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Affects Versions: 2.1.7 Reporter: Rex Wang Assignee: Rex Wang Fix For: 2.1.8 upgrade jaxb to 2.1.13 and use geronimo jaxb 2.1 spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release MyFaces bundle 2.0.9_1
build, rat:check, license/notice looks good to me. +1 -Rex 2011/9/23 Ivan xhh...@gmail.com Hi, let's vote for MyFaces 2.0.9_1, The reason for this vote is to include the patch in this JIRA : https://issues.apache.org/jira/browse/MYFACES-3309 The components for voting : https://repository.apache.org/content/repositories/orgapachegeronimo-090/org/apache/geronimo/bundles/myfaces-bundle/2.0.9_1/myfaces-bundle-2.0.9_1-source-release.zip https://repository.apache.org/content/repositories/orgapachegeronimo-090/org/apache/geronimo/bundles/myfaces-bundle/2.0.9_1/myfaces-bundle-2.0.9_1-source-release.tar.gz The stage repository : https://repository.apache.org/content/repositories/orgapachegeronimo-090 The source tag : https://svn.apache.org/repos/asf/geronimo/bundles/tags/myfaces-bundle-2.0.9_1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Ivan -- Lei Wang (Rex) rwonly AT apache.org
[VOTE] Release Geronimo Forked Aries Blueprint 0.3.0.1 (1st try)
Hi devs,
Please vote for Geronimo Forked Aries Blueprint 0.3.0.1
This release bases on Apache Aries Blueprint 0.3 tag, and includes the
fix of ARIES-727 support syntax : ${a+b} in blueprint
The components up for vote is:
https://repository.apache.org/content/repositories/orgapachegeronimo-102/org/apache/geronimo/ext/aries/blueprint/blueprint/0.3.0.1/blueprint-0.3.0.1-source-release.zip
Staging repo is:
https://repository.apache.org/content/repositories/orgapachegeronimo-102
The tag has created at:
http://svn.apache.org/repos/asf/geronimo/external/tags/blueprint-0.3.0.1/
Vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
--
Lei Wang (Rex)
rwonly AT apache.org
Re: [VOTE] Release Geronimo Forked Aries Blueprint 0.3.0.1 (1st try)
my own +1
2011/9/26 Rex Wang rwo...@gmail.com
Hi devs,
Please vote for Geronimo Forked Aries Blueprint 0.3.0.1
This release bases on Apache Aries Blueprint 0.3 tag, and includes the
fix of ARIES-727 support syntax : ${a+b} in blueprint
The components up for vote is:
https://repository.apache.org/content/repositories/orgapachegeronimo-102/org/apache/geronimo/ext/aries/blueprint/blueprint/0.3.0.1/blueprint-0.3.0.1-source-release.zip
Staging repo is:
https://repository.apache.org/content/repositories/orgapachegeronimo-102
The tag has created at:
http://svn.apache.org/repos/asf/geronimo/external/tags/blueprint-0.3.0.1/
Vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
--
Lei Wang (Rex)
rwonly AT apache.org
--
Lei Wang (Rex)
rwonly AT apache.org
[RESULT] [VOTE] Release Aries application-0.2.2 (1st attempt)
Vote result: The vote for Aries application-0.2.2 release passed with the following +1s from PMC members: Jarek Gawor, Jeremy Hughes, Kevan Miller There is no +0 or -1, Thanks for the review. I will promote it soon. BTW, I sorry not note this, what's DISCLAIMER do you mean? regards, -Rex 2011/9/21 Rex Wang rwo...@gmail.com Hi Devs, Aries application 0.2.2 is a bug-fix release which includes the fix for: ARIES-521: handles zip files without directory entries ARIES-635: Move the resource bundle to the right directory ARIES-638: Logging improvements for AriesApplicationManagerImpl ARIES-667: OBRAriesResolver can return bundle information for bundles with higher version than expected ARIES-689: Application OBR resolution fails for optional imports ARIES-734: Back port improvements made to resolution error messages in OBR application resolver The source up for vote is: https://repository.apache.org/content/repositories/orgapachearies-083/org/apache/aries/application/application/0.2.2/application-0.2.2-source-release.zip from the staging repository at: https://repository.apache.org/content/repositories/orgapachearies-083/ The tag is: http://svn.apache.org/repos/asf/aries/tags/application-0.2.2/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: cross posting
Ok.. I will use fw next time. 2011/9/22 Kevan Miller kevan.mil...@gmail.com On Sep 22, 2011, at 4:29 AM, Rex Wang wrote: Hi PMC members, please help review and vote ! :-) There's been a lot of cross-posting (multiple mailing lists on a single email), recently. Personally, that means emails get filed in strange places by my mailer. I now have an Aries vote thread getting filed in my Geronimo folder. Parts of an email thread end up in multiple folders. Many times people will Reply instead of Reply All. I'd prefer to see relevant emails forwarded to geronimo dev, instead of cross-posted... Anybody else feel that way? --kevan -- Lei Wang (Rex) rwonly AT apache.org
Re: Geronimo 3.0-beta Release Status
We are in good shape now! In the past one month, we get the following snapshot dependencies released: - xbean 3.8 - txmanager 3.1.1 - yoko 1.3 - woodstox 4.1.2_1 - bval-jsr303 0.3_1 - Tomcat 7.0.19.2 - axis2/axis2-saaj 1.6.1_1 - myfaces 2.0.9_1 - openwebbeans 1.1.1 - aries.application 0.2.2 - aries.util 0.2.1-SNAPSHOT And the rest dependencies are: - Openejb 4.0.0, OpenEJB has discussed it. Hope it can release in next week! - aries.blueprint 0.3.0.1, I forked this in geornimo ext. Will start release soon! After the above two release, I will branch 3.0-beta, and start 3.0-beta release if TCK looks good.(Currently, there are some ejb failures, I suppose they are some intermittent errors like before?..) Well done, ALL! Let's keep moving! thanks, -Rex 2011/8/25 Rex Wang rwo...@gmail.com I just closed most of the Jiras opened by Rick. We still have 100+ opened jiras... Devs, please continue clean your Jiras! -Rex 2011/8/24 Shawn Jiang genspr...@gmail.com Thanks, Rex ! tck is in good shape now. I think Most of the JIRAs opened by Rick to track the Java EE 6 spec impl could be closed now. On Wed, Aug 24, 2011 at 5:11 PM, Rex Wang rwo...@gmail.com wrote: Hi devs, I created a page in our wiki to record Geronimo 3.0-beta Release Status: https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+3.0-beta+Release+Status Now, we have a lot of OLD Jiras opened, which has been fixed or won't fix, so could you please clean your Jira status? You could see the all the un-resolved jiras in the #3.1 of the above page. thanks, -- Lei Wang (Rex) rwonly AT apache.org -- Shawn -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Commented] (GERONIMO-5987) The ActiveMQ working directory and port are not referenced correctly - multiple instances not possible
[
https://issues.apache.org/jira/browse/GERONIMO-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113236#comment-13113236
]
Rex Wang commented on GERONIMO-5987:
At revision: 1174568, I update server to use our fork aries
blueprint(0.3.0.1-SNAPSHOT) in ext, with the patch in ARIES-727.
At revision: 1174575, I commit the fix to set the activemq port and offset in
config-substitutions.properties.
You could try it again in latest build.
-Rex
The ActiveMQ working directory and port are not referenced correctly -
multiple instances not possible
--
Key: GERONIMO-5987
URL: https://issues.apache.org/jira/browse/GERONIMO-5987
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: ActiveMQ
Affects Versions: 3.0-M1, 3.0
Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4
(Tikanga)
Reporter: Russell E Glaue
Assignee: Rex Wang
Labels: geronimo
Attachments: GERONIMO-5987-detail.patch, GERONIMO-5987-new.patch,
GERONIMO-5987.patch
I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT,
geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97
ActiveMQ is configured to run as org.apache.geronimo.home.dir/var/activemq
and port 61616, and does not cooperate with multi-server configurations, nor
does it use the PortOffset. This is the use of the
org.apache.geronimo.server.name option and PortOffset in
var/config/config-substitutions.properties. (see:
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html)
First, Problem with working directory
When wanting to run more than a single server instance, the ActiveMQ startup
will block waiting for the lock file $GERONIMO_HOME/var/activemq/lock to
become available.
Obviously this causes any server instance started after the first server
instance is started to block during startup while waiting for the lock file
to become available.
Second, Problem with PortOffset
When configuring the PortOffset in
var/config/config-substitutions.properties, all Geroniomo components expect
and attempt to connect to ActiveMQ at the port {ActiveMQ + PortOffset}.
However, regardless of what you set the PortOffset to be, the ActiveMQ
service only ever binds to port 61616, the default configured port (or
whatever you have the port set as for this service).
Steps to repeat working directory problem:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
3. update the PortOffset parameter in
gserver1/var/config/config-substitutions.properties for the gserver1 instance.
4. Start the default instance and gserver1 instance:
-- bin/startup
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
5. `tail -f gserver1/var/logs/geronimo.log` and you will see this as the last
line that outputs:
2011-05-31 16:26:39,609 WARN [AMQPersistenceAdapter] Waiting to Lock the
Store var/activemq
The server waits here indefinitely.
6. Shutdown the default instance and you will see the gserver1 instance
continue on in the startup procedures. (of course you will see errors due to
the PortOffset problem)
* If I first start the gserver1 instance by itself (before starting the
default instance), the directory org.apache.geronimo.home.dir/var/activemq
is created and populated. Instead it should be
org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq
that is created and populated.
* Probably the patch should be to reference the ActiveMQ working directory as
org.apache.geronimo.server.dir/var/activemq
Steps to repeat PortOffset problem:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
3. update the PortOffset parameter in
gserver1/var/config/config-substitutions.properties in the instance
4. Start the server instance:
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
This is the two error messages you receive when configuring PortOffset to 100
(for example). The second error message, regarding XAResource, repeats:
-
2011-06-01 16:26:49,883 ERROR [MCFConnectionInterceptor] Error occurred
creating
ManagedConnection for handle: nullManagedConnectionInfo:
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@1c211b3. mc:
null]
javax.resource.ResourceException: Could not create connection
Re: [VOTE] Release Geronimo Customized Tomcat 6.0.33.1
The vote is for https://repository.apache.org/content/repositories/orgapachegeronimo-082/org/apache/geronimo/ext/tomcat/tomcat-parent-6.0.33/6.0.33.1/tomcat-parent-6.0.33-6.0.33.1-source-release.zip https://repository.apache.org/content/repositories/orgapachegeronimo-082/org/apache/geronimo/ext/tomcat/tomcat-parent-6.0.33/6.0.33.1/tomcat-parent-6.0.33-6.0.33.1-source-release.tar.gz build, rat:check, notice/license looks good to me. +1 -Rex 2011/9/21 Shenghao Fang michael1224.f...@gmail.com Please vote for Geronimo Customized Tomcat 6.0.33.1. The codes are based on Apache Tomcat 6.0.33 tag, and include the following extra changes: a. GERONIMO-3451 Restricted listeners property file not found error logged during Tomcat server startup b. GERONIMO-4685 Build our own tomcat c. Merged security fixes for CVE-2011-3190 from Tomcat 6.0.x trunk Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-082/ Source repo: https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.33.1/ -- Michael -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Aries application-0.2.2 (1st attempt)
Hi PMC members, please help review and vote ! :-) 2011/9/21 Rex Wang rwo...@gmail.com Hi Devs, Aries application 0.2.2 is a bug-fix release which includes the fix for: ARIES-521: handles zip files without directory entries ARIES-635: Move the resource bundle to the right directory ARIES-638: Logging improvements for AriesApplicationManagerImpl ARIES-667: OBRAriesResolver can return bundle information for bundles with higher version than expected ARIES-689: Application OBR resolution fails for optional imports ARIES-734: Back port improvements made to resolution error messages in OBR application resolver The source up for vote is: https://repository.apache.org/content/repositories/orgapachearies-083/org/apache/aries/application/application/0.2.2/application-0.2.2-source-release.zip from the staging repository at: https://repository.apache.org/content/repositories/orgapachearies-083/ The tag is: http://svn.apache.org/repos/asf/aries/tags/application-0.2.2/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Resolved] (GERONIMO-5975) Please give me Steps and Patch to Upgrade to Tomcat 6.0.29 from 5.5.20 in Apache Ofbiz
[ https://issues.apache.org/jira/browse/GERONIMO-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-5975. Resolution: Not A Problem Please give me Steps and Patch to Upgrade to Tomcat 6.0.29 from 5.5.20 in Apache Ofbiz -- Key: GERONIMO-5975 URL: https://issues.apache.org/jira/browse/GERONIMO-5975 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.1.6, 2.2 Environment: Windows 2008 Standard Edition Server Reporter: Daniel Xzuberance Assignee: Rex Wang Priority: Blocker Fix For: 2.2.1, 2.1.7 Please give me Steps and Patch to Upgrade to Tomcat 6.0.29 from 5.5.20 in Apache Ofbiz. I am having urgent PCI compliance faliures due to an old/vulnerable TOMCAT version and i am unable to see clear and concise steps to upgrade. My site is www.xzuberance.com and please note i am a NOVICE to Apache Ofbiz. I can also be reahced via email at xzubera...@gmail.com. Please HELP ASAP. Thanks -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
pull aries blueprint 0.3 tag to ext and ship as 0.3.0.1?
Hi Devs, I plan to pull aries blueprint 0.3 tag to ext and apply the patch in Aries-727, and then ship it as 0.3.0.1. Blueprint 0.3.x is developing in aries trunk, and has a great of many other snapshot dependencies. Seems we do not have enough time to wait blueprint trunk to release, so I will release our fork in ext to catch up the steps of Geronimo 3.0-beta release. If no objection, will do it soon. regards, -- Lei Wang (Rex) rwonly AT apache.org
[VOTE] Release Aries application-0.2.2 (1st attempt)
Hi Devs, Aries application 0.2.2 is a bug-fix release which includes the fix for: ARIES-521: handles zip files without directory entries ARIES-635: Move the resource bundle to the right directory ARIES-638: Logging improvements for AriesApplicationManagerImpl ARIES-667: OBRAriesResolver can return bundle information for bundles with higher version than expected ARIES-689: Application OBR resolution fails for optional imports ARIES-734: Back port improvements made to resolution error messages in OBR application resolver The source up for vote is: https://repository.apache.org/content/repositories/orgapachearies-083/org/apache/aries/application/application/0.2.2/application-0.2.2-source-release.zip from the staging repository at: https://repository.apache.org/content/repositories/orgapachearies-083/ The tag is: http://svn.apache.org/repos/asf/aries/tags/application-0.2.2/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks, -- Lei Wang (Rex) rwonly AT apache.org
Re: Geronimo directory structure permissions
If we want to continue maintain such complexity in 3.0? Hard drive is pretty cheap nowadays. And I think currently the part that looks a little bit wasting space is karaf copy the artifacts from repository to cache when start.. -Rex 2011/9/21 Forrest Xia forres...@gmail.com This idea is like the multiple instances feature we had in 2.1 branch, but not supported in trunk now. Geronimo 2.1.x support copying var folder to add more instances with a same installation, but G trunk code does not support that feature now. Do we have a user scenario to mandate that feature for 3.x? Regards, Forrest On Wed, Sep 21, 2011 at 1:55 AM, Jarek Gawor jga...@gmail.com wrote: Hi, In Geronimo binary install which directories do we consider read-only vs. write/read? The idea is that the read-only directories could be shared among multiple installations to save some space and reduce maintenance. Here's what I identified so far: read-only: - bin - jsr88 - schema - lib read/write: - deploy - hotbundles - etc - var The repository/ directory is a little weird because parts of it could be considered read-only and some write. I wonder if maybe we should have separate repository directories one for Geronimo bundles and another one for applications. Thanks, Jarek -- Lei Wang (Rex) rwonly AT apache.org
Re: $GERONIMO_HOME/repository as a Maven repository
2011/9/21 Yi Xiao xiaoyijhondeve...@gmail.com It sounds good. I have a idea, as the $GERONIMO_HOME/repository is a OSGi bundle repository(OBR) now, Whether we can use obr.xml which contains all the meta data of dependencies to convert the OBR to maven repository? No, obr.xml don't have enough metadate to generate pom files. -Rex On Wed, Sep 21, 2011 at 1:14 AM, Jarek Gawor jga...@gmail.com wrote: Hi, I'm curious about using $GERONIMO_HOME/repository as remote Maven repository. We are not very religious (or at least we haven't been in the past) about publishing snapshots of Geronimo (and other related) code. So if somebody wants to build their own code against the same exact versions of the dependencies as their Geronimo binary (snapshot) uses that can be very difficult. So what about using $GERONIMO_HOME/repository directly as a Maven repository? Would that work (if we put the pom files in the repository/ dir? Especially for snapshot dependencies? Thanks, Jarek -- Best regards! John Xiao -- Lei Wang (Rex) rwonly AT apache.org
Re: $GERONIMO_HOME/repository as a Maven repository
If user wants to use the snapshot artifacts in geronimo repo, could just copy them to override the artifacts in his local maven repo work? If this is not enough, I think set a hudson server in his local machine to build geronimo every night to get the latest maven repo is the right thing to do. Setting geronimo repo as the maven repo would contaminate the our artifacts when user build his project, which might bring some difficulties to identify the causes when help user analysis his problems. We definitely hope user always has a clean server when he gets problems. Anyway, as Forrest said, once there is a newer snapshot in public repo, maven would first try download the latest one, unless user uses the -o option. -Rex 2011/9/21 Jarek Gawor jga...@gmail.com Hi, I'm curious about using $GERONIMO_HOME/repository as remote Maven repository. We are not very religious (or at least we haven't been in the past) about publishing snapshots of Geronimo (and other related) code. So if somebody wants to build their own code against the same exact versions of the dependencies as their Geronimo binary (snapshot) uses that can be very difficult. So what about using $GERONIMO_HOME/repository directly as a Maven repository? Would that work (if we put the pom files in the repository/ dir? Especially for snapshot dependencies? Thanks, Jarek -- Lei Wang (Rex) rwonly AT apache.org
[RESULT] [VOTE] Release org.apache.aries.util-0.2.1 (1st attempt)
Vote passed with +1s from the following PMC members: Jarek Gawor, Kevan Miller, Guillaume Nodet, Jeremy Hughes, David Jencks, Alasdair Nottingham There is no -1 or +0 I will release org.apache.aries.util-0.2.1 soon. Thanks all for the review and vote!! -Rex 2011/9/15 Rex Wang rwo...@gmail.com Hi Devs, org.apache.aries.util-0.2.1 is a dependency to release Aries application 0.2.2. This is a bug-fix release which includes the fix for: ARIES-667: OBRAriesResolver can return bundle information for bundles with higher version than expected The components up for vote are: https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachearies-062 The tag is: http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-0.2.1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release org.apache.aries.util-0.2.1 (1st attempt)
Again, Could anyone review the vote? -Rex 2011/9/16 Rex Wang rwo...@gmail.com Hi PMC members, could you please help review and vote? -Rex 2011/9/15 Rex Wang rwo...@gmail.com rat:check, and build pass. myself +1 -Rex 2011/9/15 Rex Wang rwo...@gmail.com Hi Devs, org.apache.aries.util-0.2.1 is a dependency to release Aries application 0.2.2. This is a bug-fix release which includes the fix for: ARIES-667: OBRAriesResolver can return bundle information for bundles with higher version than expected The components up for vote are: https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachearies-062 The tag is: http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-0.2.1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release org.apache.aries.util-0.2.1 (1st attempt)
Hi PMC members, could you please help review and vote? -Rex 2011/9/15 Rex Wang rwo...@gmail.com rat:check, and build pass. myself +1 -Rex 2011/9/15 Rex Wang rwo...@gmail.com Hi Devs, org.apache.aries.util-0.2.1 is a dependency to release Aries application 0.2.2. This is a bug-fix release which includes the fix for: ARIES-667: OBRAriesResolver can return bundle information for bundles with higher version than expected The components up for vote are: https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachearies-062 The tag is: http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-0.2.1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
[VOTE] Release org.apache.aries.util-0.2.1 (1st attempt)
Hi Devs, org.apache.aries.util-0.2.1 is a dependency to release Aries application 0.2.2. This is a bug-fix release which includes the fix for: ARIES-667: OBRAriesResolver can return bundle information for bundles with higher version than expected The components up for vote are: https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachearies-062 The tag is: http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-0.2.1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks, -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release org.apache.aries.util-0.2.1 (1st attempt)
rat:check, and build pass. myself +1 -Rex 2011/9/15 Rex Wang rwo...@gmail.com Hi Devs, org.apache.aries.util-0.2.1 is a dependency to release Aries application 0.2.2. This is a bug-fix release which includes the fix for: ARIES-667: OBRAriesResolver can return bundle information for bundles with higher version than expected The components up for vote are: https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-062/org/apache/aries/org.apache.aries.util/0.2.1/org.apache.aries.util-0.2.1-source-release.tar.gz from the staging repository at: https://repository.apache.org/content/repositories/orgapachearies-062 The tag is: http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-0.2.1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks, -- Lei Wang (Rex) rwonly AT apache.org -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release axis2 and axis2-saaj bundle
rat:check and build pass, license/notice looks good to me. +1 -Rex 2011/9/13 Ivan xhh...@gmail.com The components up for vote are: https://repository.apache.org/content/repositories/orgapachegeronimo-056/org/apache/geronimo/bundles/axis2/1.6.1_1/axis2-1.6.1_1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-056/org/apache/geronimo/bundles/axis2/1.6.1_1/axis2-1.6.1_1-source-release.zip https://repository.apache.org/content/repositories/orgapachegeronimo-056/org/apache/geronimo/bundles/axis2-saaj/1.6.1_1/axis2-saaj-1.6.1_1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-056/org/apache/geronimo/bundles/axis2-saaj/1.6.1_1/axis2-saaj-1.6.1_1-source-release.zip from the staging repository at: https://repository.apache.org/content/repositories/orgapachegeronimo-056 The tag is: https://svn.apache.org/repos/asf/geronimo/bundles/tags/axis2-1.6.1_1/ https://svn.apache.org/repos/asf/geronimo/bundles/tags/axis2-saaj-1.6.1_1/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Ivan -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Closed] (GERONIMO-5221) Add naming support for Validator and ValidatorFactory.
[ https://issues.apache.org/jira/browse/GERONIMO-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5221. -- Resolution: Fixed Fix Version/s: 3.0 I think this has been fixed, so close it. Add naming support for Validator and ValidatorFactory. --- Key: GERONIMO-5221 URL: https://issues.apache.org/jira/browse/GERONIMO-5221 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: javaee6, naming Reporter: Rick McGuire Assignee: David Jencks Fix For: 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
