Re: [DISCUSS] Release Geronimo Server 2.1.4 RC1
If you can create a stand-alone junit testcase that recreates the problem, then you can open a issue against OpenJPA 1.2.1 in their JIRA - https://issues.apache.org/jira/browse/OPENJPA Given this level passed the Geronimo JEE5 TCK runs and the OpenJPA team's own internal testing, I would be against holding up the Geronimo 2.1.4 release for another OpenJPA release, as we need to get this release out ASAP for some other included fixes. -Donald Jay D. McHugh wrote: Hey again all, I think that this may caused by my rather extreme entity relationships and the use of OpenJPA's proprietary @ElementJoinColumn annotation. I have the following relationship structure: project - projectDetail (project 1-M projectDetail using @EJC) - component (projectDetail 1-1 component) - componentAttribute (component 1-M componentAttribute using @EJC) - attribute (componentAttribute 1-1 attribute) - compAttribValue (componentAttribute 1-1 compAttribValue) - componentClass (component 1-1 componentClass) - classAttrib (componentClass 1-M classAttrib using @EJC) - attribute (classAttrib 1- attribute) And I am basically trying to clone a project entity. I have debugging code that says it is creating and attaching all of the necessary details (which it is) containing the appropriate components (which it is not). I am only getting the first projectDetail persisted to the database fully. All subsequent are not getting their components created. I will try to create a test that has a similarly complicated entity relationship but uses only JPA standard links. If that works - how should we handle it? If the assembly passes TCK, and the problem is only related to the use of an OpenJPA proprietary annotation, should we just issue a note that the use of that annotation may cause problems? Jay Joe Bohn wrote: Hi Jay, Yes, please do let us know. I'm nearly done generating a new set of images and will start the vote again shortly. However, as the previous comments indicate, the images themselves are not functionally different than what you are using ... just adding in a missing license header and removing some unnecessary text in the README.txt file. Thanks, Joe Jay D. McHugh wrote: Hey all, I know that this vote is cancelled, but I tried my real app on 2.1.4 RC1 and some JPA entities are not working the way they used to on 2.1.3. I am trying to figure out if I have been taking advantage of a bug that has since been corrected - or if a problem snuck into JPA. I will let you all know as soon as I figure out which is the case. Jay Joe Bohn wrote: Message created for any discussion of the pending Geronimo 2.1.4 RC1 currently up for vote. Thanks, Joe
Re: [DISCUSS] Release Geronimo Server 2.1.4 RC1
On Mar 26, 2009, at 7:23 PM, Jay D. McHugh wrote: snip I will try to create a test that has a similarly complicated entity relationship but uses only JPA standard links. Sounds good. If that works - how should we handle it? If the assembly passes TCK, and the problem is only related to the use of an OpenJPA proprietary annotation, should we just issue a note that the use of that annotation may cause problems? Given where we're at with the release, I think that's the right thing to do. Let us know how your test-case creation goes. --kevan
Re: [DISCUSS] Release Geronimo Server 2.1.4 RC1
Thanks Jay for continuing to test the release and dig into this issue. My comments are inline with Donalds. I would recommend pursuing the specifics more with the OpenJPA team. For Geronimo 2.1.4 I think we need to ship this as is (assuming tck continues to pass) and possibly pull a new OpenJPA into a 2.1.5 release. Joe Jay D. McHugh wrote: Hey again all, I think that this may caused by my rather extreme entity relationships and the use of OpenJPA's proprietary @ElementJoinColumn annotation. I have the following relationship structure: project - projectDetail (project 1-M projectDetail using @EJC) - component (projectDetail 1-1 component) - componentAttribute (component 1-M componentAttribute using @EJC) - attribute (componentAttribute 1-1 attribute) - compAttribValue (componentAttribute 1-1 compAttribValue) - componentClass (component 1-1 componentClass) - classAttrib (componentClass 1-M classAttrib using @EJC) - attribute (classAttrib 1- attribute) And I am basically trying to clone a project entity. I have debugging code that says it is creating and attaching all of the necessary details (which it is) containing the appropriate components (which it is not). I am only getting the first projectDetail persisted to the database fully. All subsequent are not getting their components created. I will try to create a test that has a similarly complicated entity relationship but uses only JPA standard links. If that works - how should we handle it? If the assembly passes TCK, and the problem is only related to the use of an OpenJPA proprietary annotation, should we just issue a note that the use of that annotation may cause problems? Jay Joe Bohn wrote: Hi Jay, Yes, please do let us know. I'm nearly done generating a new set of images and will start the vote again shortly. However, as the previous comments indicate, the images themselves are not functionally different than what you are using ... just adding in a missing license header and removing some unnecessary text in the README.txt file. Thanks, Joe Jay D. McHugh wrote: Hey all, I know that this vote is cancelled, but I tried my real app on 2.1.4 RC1 and some JPA entities are not working the way they used to on 2.1.3. I am trying to figure out if I have been taking advantage of a bug that has since been corrected - or if a problem snuck into JPA. I will let you all know as soon as I figure out which is the case. Jay Joe Bohn wrote: Message created for any discussion of the pending Geronimo 2.1.4 RC1 currently up for vote. Thanks, Joe
Re: [VOTE] Release Geronimo Server 2.1.4 RC2
+1 --kevan On Mar 26, 2009, at 6:20 PM, Joe Bohn wrote: All, I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for your review and vote. The only differences from rc1 are: - addition of a missing license header in plugins/console/console- filter/src/main/resources/XSRF.js - removal of an extraneous (TBD) in README.txt The source for rc2 is Rev758842 from the following svn branch: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/ When the release vote is approved, I will svn mv the code to: https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/ An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz OR http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10 server binary distributions to be released (framework, tomcat/ jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code archives for the release. These extra txt files were included so that they could be leveraged by GEP if necessary (they are also included in the assembly images). For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo Server 2.1.4 [ ] 0 No opinion [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale) The voting will be open for 72 hours or until sufficient input has been received and the tck results have been verified. Thanks, Joe
Re: [VOTE] Release Geronimo Server 2.1.4 RC2
my +1 Joe Joe Bohn wrote: All, I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for your review and vote. The only differences from rc1 are: - addition of a missing license header in plugins/console/console-filter/src/main/resources/XSRF.js - removal of an extraneous (TBD) in README.txt The source for rc2 is Rev758842 from the following svn branch: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/ When the release vote is approved, I will svn mv the code to: https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/ An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz OR http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10 server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code archives for the release. These extra txt files were included so that they could be leveraged by GEP if necessary (they are also included in the assembly images). For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo Server 2.1.4 [ ] 0 No opinion [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale) The voting will be open for 72 hours or until sufficient input has been received and the tck results have been verified. Thanks, Joe
Re: [DISCUSS] Release Geronimo Server 2.1.4 RC1
I was hoping that most people would be leaning that way. Jay Joe Bohn wrote: Thanks Jay for continuing to test the release and dig into this issue. My comments are inline with Donalds. I would recommend pursuing the specifics more with the OpenJPA team. For Geronimo 2.1.4 I think we need to ship this as is (assuming tck continues to pass) and possibly pull a new OpenJPA into a 2.1.5 release. Joe Jay D. McHugh wrote: Hey again all, I think that this may caused by my rather extreme entity relationships and the use of OpenJPA's proprietary @ElementJoinColumn annotation. I have the following relationship structure: project - projectDetail (project 1-M projectDetail using @EJC) - component (projectDetail 1-1 component) - componentAttribute (component 1-M componentAttribute using @EJC) - attribute (componentAttribute 1-1 attribute) - compAttribValue (componentAttribute 1-1 compAttribValue) - componentClass (component 1-1 componentClass) - classAttrib (componentClass 1-M classAttrib using @EJC) - attribute (classAttrib 1- attribute) And I am basically trying to clone a project entity. I have debugging code that says it is creating and attaching all of the necessary details (which it is) containing the appropriate components (which it is not). I am only getting the first projectDetail persisted to the database fully. All subsequent are not getting their components created. I will try to create a test that has a similarly complicated entity relationship but uses only JPA standard links. If that works - how should we handle it? If the assembly passes TCK, and the problem is only related to the use of an OpenJPA proprietary annotation, should we just issue a note that the use of that annotation may cause problems? Jay Joe Bohn wrote: Hi Jay, Yes, please do let us know. I'm nearly done generating a new set of images and will start the vote again shortly. However, as the previous comments indicate, the images themselves are not functionally different than what you are using ... just adding in a missing license header and removing some unnecessary text in the README.txt file. Thanks, Joe Jay D. McHugh wrote: Hey all, I know that this vote is cancelled, but I tried my real app on 2.1.4 RC1 and some JPA entities are not working the way they used to on 2.1.3. I am trying to figure out if I have been taking advantage of a bug that has since been corrected - or if a problem snuck into JPA. I will let you all know as soon as I figure out which is the case. Jay Joe Bohn wrote: Message created for any discussion of the pending Geronimo 2.1.4 RC1 currently up for vote. Thanks, Joe
Re: [VOTE] Release Geronimo Server 2.1.4 RC2
+1 Jay Joe Bohn wrote: All, I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for your review and vote. The only differences from rc1 are: - addition of a missing license header in plugins/console/console-filter/src/main/resources/XSRF.js - removal of an extraneous (TBD) in README.txt The source for rc2 is Rev758842 from the following svn branch: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/ When the release vote is approved, I will svn mv the code to: https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/ An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz OR http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10 server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code archives for the release. These extra txt files were included so that they could be leveraged by GEP if necessary (they are also included in the assembly images). For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo Server 2.1.4 [ ] 0 No opinion [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale) The voting will be open for 72 hours or until sufficient input has been received and the tck results have been verified. Thanks, Joe
Re: [VOTE] Release Geronimo Server 2.1.4 RC2
+1 Donald Joe Bohn wrote: All, I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for your review and vote. The only differences from rc1 are: - addition of a missing license header in plugins/console/console-filter/src/main/resources/XSRF.js - removal of an extraneous (TBD) in README.txt The source for rc2 is Rev758842 from the following svn branch: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/ When the release vote is approved, I will svn mv the code to: https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/ An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz OR http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10 server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code archives for the release. These extra txt files were included so that they could be leveraged by GEP if necessary (they are also included in the assembly images). For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo Server 2.1.4 [ ] 0 No opinion [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale) The voting will be open for 72 hours or until sufficient input has been received and the tck results have been verified. Thanks, Joe
Re: Deploying ear file with ldap realm - geronimo 2.1.x
I have done the below steps, application works with ldap realm. Can anyone confirm these steps are correct? 1. create ldap realm and deploy, goto admin console-repository-click deployed ldap realm to see the dependency to be added to geronimo plan file 2. Unpack ear file, goto META-INF directory, create geronimo-application.xml plan file 3. Add security-realm-namecorp-ldap/security-realm-name right below context-root/SuperSnoopWeb/context-root in geronimo-application.xml 4. Add security /security in geronimo-application.xml 5. Add security-role to META-INF/application.xml 6. Unpack war file, add security-constraint, login-config, security-role to web.xml, If ear has more than one war file, do the same. 7. Package war file(s) 8. package ear file 9. deploy ear file ./deploy.sh deploy /home/t6652bg/binaries/sample_apps/SuperSnoop/ear/SuperSnoop.ear /home/t6652bg/binaries/sample_apps/SuperSnoop/ear/META-INF/geronimo-application.xml Using GERONIMO_BASE: /global/WebSphereCE Using GERONIMO_HOME: /global/WebSphereCE Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: /opt/ibm/java2-i386-50/jre Username: system Password: *** Deployed SuperSnoop/SuperSnoopEAR/1.0/car `- SuperSnoopWeb.war @ /SuperSnoopWeb - govinda wrote: Thanks David. I'm able to deploy the ear file by adding dependency in geronimo-application.xml, how do I protect resource (/SuperSnoopWeb)? deployer does not accept security-constraint element in application.xml Dependency: sys:environment sys:moduleId sys:groupIdSuperSnoop/sys:groupId sys:artifactIdSuperSnoopEAR/sys:artifactId sys:version1.0/sys:version sys:typecar/sys:type /sys:moduleId dependencies dependency groupIdconsole.realm/groupId artifactIdcorp-ldap/artifactId version1.0/version typecar/type /dependency /dependencies /sys:environment djencks wrote: I don't see anything obviously wrong with your xml. Is there any more information with the error such as a stack trace or the name of the class that can't be loaded? thanks david jencks On Mar 25, 2009, at 10:05 PM, govinda wrote: I tried to deploy ear file that has single war file and I receive the following error, my geronimo-application.xml has ldap realm. I have server-wide ldap realm created, deployed war and tested ldap security, its working but I could not deploy ear file. Am I missing any security mapping? server001:/global/WebSphereCE/bin # ./deploy.sh deploy SuperSnoop.ear geronimo-application.xml Using GERONIMO_BASE: /global/WebSphereCE Using GERONIMO_HOME: /global/WebSphereCE Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: /opt/ibm/java2-i386-50/jre Username: system Password: *** Error: Operation failed: load of SuperSnoop/SuperSnoopEAR/1.0/car failed Error starting configuration gbean SuperSnoop/SuperSnoopEAR/1.0/car Configuration gbean failed to start SuperSnoop/SuperSnoopEAR/1.0/car reason: Class not loadable in classloader: [org.apache.geronimo.kernel.config.MultiParentClassLoader id=SuperSnoop/SuperSnoopEAR/1.0/car] geronimo-application.xml: ?xml version=1.0 encoding=UTF-8? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-2.0 xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2; application-name=SuperSnoop sys:environment sys:moduleId sys:groupIdSuperSnoop/sys:groupId sys:artifactIdSuperSnoopEAR/sys:artifactId sys:version1.0/sys:version sys:typecar/sys:type /sys:moduleId /sys:environment module webSuperSnoopWeb.war/web web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1; sys:environment sys:moduleId sys:groupIdSuperSnoop/sys:groupId sys:artifactIdSuperSnoopWEB/sys:artifactId sys:version1.0/sys:version sys:typewar/sys:type /sys:moduleId /sys:environment context-root/SuperSnoopWeb/context-root security-realm-namecorp-ldap/security-realm-name /web-app /module security default-principal realm-name=corp-ldap principal name=nobody class = org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal/ /default-principal role-mappings role role-name=admin realm realm-name=corp-ldap principal name=adminstrators class = org .apache.geronimo.security.realm.providers.GeronimoGroupPrincipal/ principal name=admin class = org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal/ /realm /role /role-mappings /security /application META-INF/application.xml: ?xml version=1.0 encoding=UTF-8? !DOCTYPE application PUBLIC -//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN http://java.sun.com/j2ee/dtds/application_1_2.dtd application
[jira] Updated: (GERONIMO-4410) Update JPA 2.0 spec component
[ https://issues.apache.org/jira/browse/GERONIMO-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Bauer updated GERONIMO-4410: --- Attachment: jsr317_20090313_update.patch Update JPA 2.0 spec component - Key: GERONIMO-4410 URL: https://issues.apache.org/jira/browse/GERONIMO-4410 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: specs Reporter: Jeremy Bauer Assignee: David Jencks Attachments: geronimo_jpa_2_spec_updates.patch, geronimo_jpa_2_spec_updates2.patch, geronimo_jpa_2_spec_updates2_nodoc.patch, geronimo_jpa_2_spec_updates3.patch, jpa2.0-update-1.0-patch.txt, jsr317_20090313_update.patch This task is to update the JPA 2.0 spec component (geronimo-jpa_2.0_spec) with code provided by the OpenJPA project as new JPA 2.0/JSR-317 public spec drafts are made available - through the final draft. Updates will be provided in the form of a patch. After the update is made a snapshot will be pushed out to the maven repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4410) Update JPA 2.0 spec component
[ https://issues.apache.org/jira/browse/GERONIMO-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Bauer updated GERONIMO-4410: --- Attachment: jsr317_20090313_update.patch A new version of the JSR-317 spec was published. Please update the jpa 2.0 spec tree with jsr317_20090313_update.patch and push a version 1.0.1-EA-SNAPSHOT jar to the repro. Thanks! Update JPA 2.0 spec component - Key: GERONIMO-4410 URL: https://issues.apache.org/jira/browse/GERONIMO-4410 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: specs Reporter: Jeremy Bauer Assignee: David Jencks Attachments: geronimo_jpa_2_spec_updates.patch, geronimo_jpa_2_spec_updates2.patch, geronimo_jpa_2_spec_updates2_nodoc.patch, geronimo_jpa_2_spec_updates3.patch, jpa2.0-update-1.0-patch.txt, jsr317_20090313_update.patch This task is to update the JPA 2.0 spec component (geronimo-jpa_2.0_spec) with code provided by the OpenJPA project as new JPA 2.0/JSR-317 public spec drafts are made available - through the final draft. Updates will be provided in the form of a patch. After the update is made a snapshot will be pushed out to the maven repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4410) Update JPA 2.0 spec component
[ https://issues.apache.org/jira/browse/GERONIMO-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Bauer updated GERONIMO-4410: --- Attachment: (was: jsr317_20090313_update.patch) Update JPA 2.0 spec component - Key: GERONIMO-4410 URL: https://issues.apache.org/jira/browse/GERONIMO-4410 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: specs Reporter: Jeremy Bauer Assignee: David Jencks Attachments: geronimo_jpa_2_spec_updates.patch, geronimo_jpa_2_spec_updates2.patch, geronimo_jpa_2_spec_updates2_nodoc.patch, geronimo_jpa_2_spec_updates3.patch, jpa2.0-update-1.0-patch.txt, jsr317_20090313_update.patch This task is to update the JPA 2.0 spec component (geronimo-jpa_2.0_spec) with code provided by the OpenJPA project as new JPA 2.0/JSR-317 public spec drafts are made available - through the final draft. Updates will be provided in the form of a patch. After the update is made a snapshot will be pushed out to the maven repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4410) Update JPA 2.0 spec component
[ https://issues.apache.org/jira/browse/GERONIMO-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-4410: -- Assignee: Donald Woods (was: David Jencks) Update JPA 2.0 spec component - Key: GERONIMO-4410 URL: https://issues.apache.org/jira/browse/GERONIMO-4410 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: specs Reporter: Jeremy Bauer Assignee: Donald Woods Attachments: geronimo_jpa_2_spec_updates.patch, geronimo_jpa_2_spec_updates2.patch, geronimo_jpa_2_spec_updates2_nodoc.patch, geronimo_jpa_2_spec_updates3.patch, jpa2.0-update-1.0-patch.txt, jsr317_20090313_update.patch This task is to update the JPA 2.0 spec component (geronimo-jpa_2.0_spec) with code provided by the OpenJPA project as new JPA 2.0/JSR-317 public spec drafts are made available - through the final draft. Updates will be provided in the form of a patch. After the update is made a snapshot will be pushed out to the maven repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Geronimo Server 2.1.4 RC2
+1 Joe Bohn wrote: All, I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for your review and vote. The only differences from rc1 are: - addition of a missing license header in plugins/console/console-filter/src/main/resources/XSRF.js - removal of an extraneous (TBD) in README.txt The source for rc2 is Rev758842 from the following svn branch: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/ When the release vote is approved, I will svn mv the code to: https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/ An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz OR http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10 server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code archives for the release. These extra txt files were included so that they could be leveraged by GEP if necessary (they are also included in the assembly images). For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo Server 2.1.4 [ ] 0 No opinion [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale) The voting will be open for 72 hours or until sufficient input has been received and the tck results have been verified. Thanks, Joe
Re: [VOTE] Release Geronimo Server 2.1.4 RC2
+1 and thanks Joe for putting this together! Jarek On Thu, Mar 26, 2009 at 6:20 PM, Joe Bohn joe.b...@earthlink.net wrote: All, I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for your review and vote. The only differences from rc1 are: - addition of a missing license header in plugins/console/console-filter/src/main/resources/XSRF.js - removal of an extraneous (TBD) in README.txt The source for rc2 is Rev758842 from the following svn branch: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/ When the release vote is approved, I will svn mv the code to: https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/ An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz OR http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10 server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code archives for the release. These extra txt files were included so that they could be leveraged by GEP if necessary (they are also included in the assembly images). For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo Server 2.1.4 [ ] 0 No opinion [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale) The voting will be open for 72 hours or until sufficient input has been received and the tck results have been verified. Thanks, Joe
geronimo-jpa_2.0_spec updated to match latest PFD
Jeremy provided a patch in GERONIMO-4410 which upgraded the - Apache Geronimo JSR-317 JPA 2.0 EARLY ACCESS Spec API to the Proposed Final Draft that was released yesterday. The updated artifacts use version=1.0-EA2-SNAPSHOT and have been published to the ASF snapshot repo. Jeremy is in the process of updating and testing the OpenJPA trunk code to use the new Spec APIs. Note: The PFD still includes the earlier legal requirements to label the artifacts as EARLY ACCESS and to include the following in the NOTICE file - This is an implementation of an early-draft specification developed under the Java Community Process (JCP) and is made available for testing and evaluation purposes only. The code is not compatible with any specification of the JCP. Which means we will not be able to release an official OpenJPA 2.0 Milestone build with this level of the spec either -Donald
Re: geronimo-jpa_2.0_spec updated to match latest PFD
On Mar 27, 2009, at 12:27 PM, Donald Woods wrote: Jeremy provided a patch in GERONIMO-4410 which upgraded the - Apache Geronimo JSR-317 JPA 2.0 EARLY ACCESS Spec API to the Proposed Final Draft that was released yesterday. The updated artifacts use version=1.0-EA2-SNAPSHOT and have been published to the ASF snapshot repo. Jeremy is in the process of updating and testing the OpenJPA trunk code to use the new Spec APIs. Note: The PFD still includes the earlier legal requirements to label the artifacts as EARLY ACCESS and to include the following in the NOTICE file - This is an implementation of an early-draft specification developed under the Java Community Process (JCP) and is made available for testing and evaluation purposes only. The code is not compatible with any specification of the JCP. Which means we will not be able to release an official OpenJPA 2.0 Milestone build with this level of the spec either Has there been any progress in getting this fixed in the Spec? Ok. Answered my own question. Looks like not... I'll send a note to jcp- open@ --kevan
Re: [DISCUSS] Release Geronimo Server 2.1.4 RC1
I tried to create a simplified test case. But it worked like a charm - So, I must have been taking advantage of a bug that has been corrected. I will try to sort out my entity relations to figure out what I am doing wrong. Jay Donald Woods wrote: If you can create a stand-alone junit testcase that recreates the problem, then you can open a issue against OpenJPA 1.2.1 in their JIRA - https://issues.apache.org/jira/browse/OPENJPA Given this level passed the Geronimo JEE5 TCK runs and the OpenJPA team's own internal testing, I would be against holding up the Geronimo 2.1.4 release for another OpenJPA release, as we need to get this release out ASAP for some other included fixes. -Donald Jay D. McHugh wrote: Hey again all, I think that this may caused by my rather extreme entity relationships and the use of OpenJPA's proprietary @ElementJoinColumn annotation. I have the following relationship structure: project - projectDetail (project 1-M projectDetail using @EJC) - component (projectDetail 1-1 component) - componentAttribute (component 1-M componentAttribute using @EJC) - attribute (componentAttribute 1-1 attribute) - compAttribValue (componentAttribute 1-1 compAttribValue) - componentClass (component 1-1 componentClass) - classAttrib (componentClass 1-M classAttrib using @EJC) - attribute (classAttrib 1- attribute) And I am basically trying to clone a project entity. I have debugging code that says it is creating and attaching all of the necessary details (which it is) containing the appropriate components (which it is not). I am only getting the first projectDetail persisted to the database fully. All subsequent are not getting their components created. I will try to create a test that has a similarly complicated entity relationship but uses only JPA standard links. If that works - how should we handle it? If the assembly passes TCK, and the problem is only related to the use of an OpenJPA proprietary annotation, should we just issue a note that the use of that annotation may cause problems? Jay Joe Bohn wrote: Hi Jay, Yes, please do let us know. I'm nearly done generating a new set of images and will start the vote again shortly. However, as the previous comments indicate, the images themselves are not functionally different than what you are using ... just adding in a missing license header and removing some unnecessary text in the README.txt file. Thanks, Joe Jay D. McHugh wrote: Hey all, I know that this vote is cancelled, but I tried my real app on 2.1.4 RC1 and some JPA entities are not working the way they used to on 2.1.3. I am trying to figure out if I have been taking advantage of a bug that has since been corrected - or if a problem snuck into JPA. I will let you all know as soon as I figure out which is the case. Jay Joe Bohn wrote: Message created for any discussion of the pending Geronimo 2.1.4 RC1 currently up for vote. Thanks, Joe
Re: [VOTE] Release Geronimo Server 2.1.4 RC2
+1 Joe Bohn wrote: All, I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for your review and vote. The only differences from rc1 are: - addition of a missing license header in plugins/console/console-filter/src/main/resources/XSRF.js - removal of an extraneous (TBD) in README.txt The source for rc2 is Rev758842 from the following svn branch: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/ When the release vote is approved, I will svn mv the code to: https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/ An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz OR http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10 server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code archives for the release. These extra txt files were included so that they could be leveraged by GEP if necessary (they are also included in the assembly images). For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo Server 2.1.4 [ ] 0 No opinion [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale) The voting will be open for 72 hours or until sufficient input has been received and the tck results have been verified. Thanks, Joe -- Thanks, Tim McConnell
[BUILD] trunk: Failed for Revision: 759406
Geronimo Revision: 759406 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090327/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090327
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 35 minutes 58 seconds
[INFO] Finished at: Fri Mar 27 21:40:02 EDT 2009
[INFO] Final Memory: 670M/1007M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090327/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:40.925
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:00:59.232)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.204)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.462)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.035)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:15.648)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:29.344)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:54.383)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:49.271)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:14.088)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:42.352)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.065)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:32.027)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:33.292)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:50.932)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.402)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.845)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.767)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.860)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:37.372) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.901)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test
[jira] Assigned: (XBEAN-122) Object cannot be removed from context in many circumstances
[ https://issues.apache.org/jira/browse/XBEAN-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned XBEAN-122: -- Assignee: Ivan Object cannot be removed from context in many circumstances --- Key: XBEAN-122 URL: https://issues.apache.org/jira/browse/XBEAN-122 Project: XBean Issue Type: Bug Components: naming Affects Versions: 3.5 Reporter: Jack Cai Assignee: Ivan Attachments: Geronimo-4549_0307.patch See https://issues.apache.org/jira/browse/GERONIMO-4549 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (XBEAN-122) Object cannot be removed from context in many circumstances
[ https://issues.apache.org/jira/browse/XBEAN-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689857#action_12689857 ] Jack Cai commented on XBEAN-122: Thanks Ivan for helping! Committing to the trunk is OK. Object cannot be removed from context in many circumstances --- Key: XBEAN-122 URL: https://issues.apache.org/jira/browse/XBEAN-122 Project: XBean Issue Type: Bug Components: naming Affects Versions: 3.5 Reporter: Jack Cai Assignee: Ivan Attachments: Geronimo-4549_0307.patch See https://issues.apache.org/jira/browse/GERONIMO-4549 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
