[jira] Updated: (GERONIMO-5516) Add isAdvanced properties to AdminConsoleExtensionGBean
[ https://issues.apache.org/jira/browse/GERONIMO-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] janel Zhang updated GERONIMO-5516: -- Attachment: geronimo-pluto-3.0.patch console-portal-driver-3.0.patch advance.jpg The patches apply to geronimo 3.0,and they create basic and advanced console. > Add isAdvanced properties to AdminConsoleExtensionGBean > --- > > Key: GERONIMO-5516 > URL: https://issues.apache.org/jira/browse/GERONIMO-5516 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2.2, 3.0 >Reporter: Chi Runhua >Assignee: Chi Runhua >Priority: Minor > Attachments: advance.jpg, basic.jpg, console-portal-driver-3.0.patch, > console-portal-driver.patch, console-tomcat.patch, geronimo-pluto-3.0.patch, > geronimo-pluto.patch > > > Add a boolean property for AdminConsoleExtensionGBean and in this way, we can > control whether the portlet should be displayed on Admin Console or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5516) Add isAdvanced properties to AdminConsoleExtensionGBean
[ https://issues.apache.org/jira/browse/GERONIMO-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] janel Zhang updated GERONIMO-5516: -- Attachment: basic.jpg > Add isAdvanced properties to AdminConsoleExtensionGBean > --- > > Key: GERONIMO-5516 > URL: https://issues.apache.org/jira/browse/GERONIMO-5516 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2.2, 3.0 >Reporter: Chi Runhua >Assignee: Chi Runhua >Priority: Minor > Attachments: advance.jpg, basic.jpg, console-portal-driver-3.0.patch, > console-portal-driver.patch, console-tomcat.patch, geronimo-pluto-3.0.patch, > geronimo-pluto.patch > > > Add a boolean property for AdminConsoleExtensionGBean and in this way, we can > control whether the portlet should be displayed on Admin Console or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5058) Move the term "j2ee" to "javaee" refered by plugin names and package names
[ https://issues.apache.org/jira/browse/GERONIMO-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903228#action_12903228 ] Rex Wang commented on GERONIMO-5058: OK, got it. > Move the term "j2ee" to "javaee" refered by plugin names and package names > -- > > Key: GERONIMO-5058 > URL: https://issues.apache.org/jira/browse/GERONIMO-5058 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 3.0 > > > 1. Following are planned to modify: > (1) framework configs: > trunk\framework\configs\j2ee-system\ > trunk\framework\configs\j2ee-security\ > trunk\framework\configs\geronimo-gbean-deployer\src\it\j2ee-system-it1\ > trunk\framework\configs\geronimo-gbean-deployer\src\it\j2ee-system-it2\ > (2) plugins: > trunk\plugins\j2ee\ > trunk\plugins\j2ee\j2ee-server\ > trunk\plugins\j2ee\j2ee-deployer\ > trunk\plugins\j2ee\geronimo-j2ee-schema\ > trunk\plugins\j2ee\geronimo-j2ee-builder\ > trunk\plugins\j2ee\geronimo-j2ee-builder\src\main\java\org\apache\geronimo\j2ee\ > trunk\plugins\j2ee\geronimo-j2ee-builder\src\test\java\org\apache\geronimo\j2ee\ > trunk\plugins\j2ee\geronimo-j2ee\ > trunk\plugins\j2ee\geronimo-j2ee\src\main\java\org\apache\geronimo\j2ee\ > trunk\plugins\j2ee\geronimo-j2ee\src\test\java\org\apache\geronimo\j2ee\ > --- > 2. Keep as is: > trunk\plugins\corba\j2ee-corba-yoko\ > trunk\plugins\webservices\geronimo-webservices-builder\src\test\resources\webservices-j2ee14.xml > --- > 3. jsr77 stuffs, keep as is: > trunk\plugins\j2ee\geronimo-j2ee\src\main\java\org\apache\geronimo\j2ee\j2eeobjectnames\ > trunk\plugins\j2ee\geronimo-j2ee\src\test\java\org\apache\geronimo\j2ee\j2eeobjectnames\ > trunk\framework\modules\geronimo-management\src\main\java\org\apache\geronimo\management\J2EE*.java > trunk\framework\modules\geronimo-management\src\main\java\org\apache\geronimo\management\geronimo\J2EE*.java > trunk\plugins\j2ee\geronimo-j2ee\src\main\java\org\apache\geronimo\j2ee\j2eeobjectnames\J2ee*.java > trunk\plugins\j2ee\geronimo-j2ee\src\main\java\org\apache\geronimo\j2ee\management\impl\J2EE*Impl.java > --- > 4. Schemas, keep as is: > trunk\plugins\j2ee\geronimo-j2ee-schema\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\j2ee\geronimo-j2ee-builder\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\j2ee\geronimo-web-2.5-builder\src\test\resources\j2ee_1_4schema\ > trunk\plugins\j2ee\geronimo-web-2.5-builder\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\j2ee\geronimo-web-2.5-builder\src\test\resources\j2ee_1_2dtd\ > trunk\plugins\openejb\geronimo-openejb-builder\src\test\resources\j2ee_1_4schema\ > trunk\plugins\openejb\geronimo-openejb-builder\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\openejb\geronimo-openejb-builder\src\test\resources\j2ee_1_2dtd\ > trunk\plugins\client\geronimo-client-builder\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\connector-1_6\geronimo-connector-builder-1_6\src\test\resources\j2ee_1_3dtd\ > > 5. j2ee 1.3 & 1.4 stuffs, keep as is: > trunk\testsupport\test-deployment-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.4\test-war-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.4\test-rar-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.4\test-ejb-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.4\test-ear-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.3\ > trunk\testsupport\test-deployment-j2ee_1.3\test-war-j2ee_1.3\ > trunk\testsupport\test-deployment-j2ee_1.3\test-rar-j2ee_1.3\ > trunk\testsupport\test-deployment-j2ee_1.3\test-ejb-j2ee_1.3\ > trunk\testsupport\test-deployment-j2ee_1.3\test-ear-j2ee_1.3\ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 989993
Geronimo Revision: 989993 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/build-2100.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 41 minutes 53 seconds [INFO] Finished at: Thu Aug 26 21:47:13 EDT 2010 [INFO] Final Memory: 485M/1002M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/logs-2100-tomcat/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.012 sec <<< FAILURE! -- Running TestSuite Tests run: 9, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 53.714 sec <<< FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.699 sec <<< FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/logs-2100-jetty/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.507 sec <<< FAILURE! Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.082 sec <<< FAILURE! -- Running TestSuite Tests run: 9, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 50.073 sec <<< FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/samples-2100.log Build status: OK
Re: packaging datasource tests... where does jsesun25 come from?
Wrong list, David... --kevan On Aug 26, 2010, at 8:52 PM, David Jencks wrote: > I'm wondering what I'm missing... > > On my machine the > com/sun/ts/tests/ejb30/lite/packaging/war/datasource/singleton are all > failing because the datasource annotations refer to a jsesun25 server. Has > someone figured out what to do about this? > > thanks > david jencks >
[jira] Updated: (GERONIMO-5227) Add ValidatorFactory to servlet context for JSF usage.
[ https://issues.apache.org/jira/browse/GERONIMO-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy updated GERONIMO-5227: -- Attachment: GERONIMO-5227-jetty.patch GERONIMO-5227-jetty.patch: Set the "javax.faces.validator.beanValidator.ValidatorFactory" attribute in ServletContext for Jetty. > Add ValidatorFactory to servlet context for JSF usage. > --- > > Key: GERONIMO-5227 > URL: https://issues.apache.org/jira/browse/GERONIMO-5227 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, naming >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > Attachments: GERONIMO-5227-jetty.patch, GERONIMO-5227-tomcat.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
packaging datasource tests... where does jsesun25 come from?
I'm wondering what I'm missing... On my machine the com/sun/ts/tests/ejb30/lite/packaging/war/datasource/singleton are all failing because the datasource annotations refer to a jsesun25 server. Has someone figured out what to do about this? thanks david jencks
[jira] Closed: (GERONIMO-5555) The version of the application when deploying an EBA is set incorrectly
[ https://issues.apache.org/jira/browse/GERONIMO-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn closed GERONIMO-. -- > The version of the application when deploying an EBA is set incorrectly > --- > > Key: GERONIMO- > URL: https://issues.apache.org/jira/browse/GERONIMO- > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0-M1 >Reporter: Joe Bohn >Assignee: Joe Bohn >Priority: Minor > Fix For: 3.0 > > > When deploying an EBA into Apache Geronimo the version set for the > application is pulled from the Application Metadata but it appears that it is > constructing the version incorrectly. For example, in the following > deployment the application version is set to 0.2.2-incubating rather than > 0.2.0-incubating: > b...@tetra:~/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT>./bin/deploy > -u system -p manager deploy > ~/vote-aries-rc3/source-archives/samples-0.2-incubating/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.2-incubating.eba > > Using GERONIMO_HOME: > /Users/bohn/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT > Using GERONIMO_TMPDIR: var/temp > Using JRE_HOME: > /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home > Deployed > application/org.apache.aries.samples.blog.jpa.eba/0.2.2-incubating/eba -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5556) Geronimo admin console seems to be missing the System Modules portlet page
[
https://issues.apache.org/jira/browse/GERONIMO-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn closed GERONIMO-5556.
--
Regression: [Regression]
> Geronimo admin console seems to be missing the System Modules portlet page
> --
>
> Key: GERONIMO-5556
> URL: https://issues.apache.org/jira/browse/GERONIMO-5556
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 3.0
>Reporter: Joe Bohn
>Assignee: Joe Bohn
> Fix For: 3.0
>
>
> I happened to notice that with the latest trunk image the System Modules
> portlet page is missing. I suspect that this was the result of some recent
> change reorganizing the navigation panel. It seems that currently the
> "Plugins" page and the "System Modules" page are attempting to occupy the
> same slot and so the last one processed ("Plugins" in this case) wins. I'll
> update the plan and find an unoccupied slot for System Modules. We might
> want to reconsider this processing where basically any plugin installed later
> can trump and earlier entry in the admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5555) The version of the application when deploying an EBA is set incorrectly
[ https://issues.apache.org/jira/browse/GERONIMO-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-. Resolution: Fixed > The version of the application when deploying an EBA is set incorrectly > --- > > Key: GERONIMO- > URL: https://issues.apache.org/jira/browse/GERONIMO- > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0-M1 >Reporter: Joe Bohn >Assignee: Joe Bohn >Priority: Minor > Fix For: 3.0 > > > When deploying an EBA into Apache Geronimo the version set for the > application is pulled from the Application Metadata but it appears that it is > constructing the version incorrectly. For example, in the following > deployment the application version is set to 0.2.2-incubating rather than > 0.2.0-incubating: > b...@tetra:~/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT>./bin/deploy > -u system -p manager deploy > ~/vote-aries-rc3/source-archives/samples-0.2-incubating/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.2-incubating.eba > > Using GERONIMO_HOME: > /Users/bohn/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT > Using GERONIMO_TMPDIR: var/temp > Using JRE_HOME: > /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home > Deployed > application/org.apache.aries.samples.blog.jpa.eba/0.2.2-incubating/eba -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5556) Geronimo admin console seems to be missing the System Modules portlet page
[
https://issues.apache.org/jira/browse/GERONIMO-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn resolved GERONIMO-5556.
Fix Version/s: 3.0
Resolution: Fixed
> Geronimo admin console seems to be missing the System Modules portlet page
> --
>
> Key: GERONIMO-5556
> URL: https://issues.apache.org/jira/browse/GERONIMO-5556
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 3.0
>Reporter: Joe Bohn
>Assignee: Joe Bohn
> Fix For: 3.0
>
>
> I happened to notice that with the latest trunk image the System Modules
> portlet page is missing. I suspect that this was the result of some recent
> change reorganizing the navigation panel. It seems that currently the
> "Plugins" page and the "System Modules" page are attempting to occupy the
> same slot and so the last one processed ("Plugins" in this case) wins. I'll
> update the plan and find an unoccupied slot for System Modules. We might
> want to reconsider this processing where basically any plugin installed later
> can trump and earlier entry in the admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 989879
Geronimo Revision: 989879 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 40 minutes 39 seconds [INFO] Finished at: Thu Aug 26 15:45:57 EDT 2010 [INFO] Final Memory: 434M/1013M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/logs-1500-tomcat/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.104 sec <<< FAILURE! -- Running TestSuite Tests run: 9, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 53.988 sec <<< FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.769 sec <<< FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/logs-1500-jetty/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.125 sec <<< FAILURE! Running TestSuite Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.018 sec <<< FAILURE! -- Running TestSuite Tests run: 9, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 49.913 sec <<< FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/samples-1500.log Build status: OK
[jira] Updated: (GERONIMO-5227) Add ValidatorFactory to servlet context for JSF usage.
[ https://issues.apache.org/jira/browse/GERONIMO-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy updated GERONIMO-5227: -- Attachment: GERONIMO-5227-tomcat.patch GERONIMO-5227-tomcat.patch: Set the "javax.faces.validator.beanValidator.ValidatorFactory" attribute in ServletContext for Tomcat. > Add ValidatorFactory to servlet context for JSF usage. > --- > > Key: GERONIMO-5227 > URL: https://issues.apache.org/jira/browse/GERONIMO-5227 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, naming >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > Attachments: GERONIMO-5227-tomcat.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903050#action_12903050 ] Jarek Gawor commented on GERONIMO-5553: --- Aries JPA code only kicks in if a war file is deployed as a wab, i.e. deployed as part of eba or installed via osgi:install webbundle:// command. I assume in this case the war file is deployed as a regular java ee application. So no need to worry about Aries JPA code. > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang >Assignee: Rick McGuire > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Retrieving the ValidatorFactory JNDI entry for a module context.
Ah... the solution seems to be much simpler get rid of the "java:" in
the lookup!!
On Thu, Aug 26, 2010 at 8:56 PM, Rick McGuire wrote:
> I'm trying to implement the bean validation feature described in section
> EE.6.27 of the Java EE 6 specification. This requires that the web
> container set a property named
> "javax.faces.validator.beanValidator.ValidatorFactory" in the
> ServletContext. I know where this should be set, but I'm having problems
> getting access to the ValidatorFactory instance that I need to satisfy this
> requirement.
>
> For example, I've tried adding the following code to TomcatContainer to set
> this property:
>
>// now set the module context ValidatorFactory in a context
> property.
>try {
>javax.naming.Context ctx =contextInfo.getJndiContext();
>Object validatorFactory
> =ctx.lookup("java:comp/ValidatorFactory");
>
>
> context.getServletContext().setAttribute("javax.faces.validator.beanValidator.ValidatorFactory",validatorFactory);
>}catch (NamingException e) {
> // ignore. We just don't set the property if it's not
> available.
>}
>
>
> This results in a NamingException, which probably means that
> contextInfo.getJndiContext() is not the correct place to retrieve this or
> the context has not yet been set up correctly. I've also tried using an
> InitialContext to do the lookup with the same result. I had a similar
> problem with Jetty where I tried using
>
>try {
>javax.naming.Context ctx
> =integrationContext.getComponentContext();
>Object validatorFactory
> =ctx.lookup("java:comp/ValidatorFactory");
>
> to lookup the factory. How should I be obtaining this value when setting
> up the container?
>
> I have a similar issue with passing the ValidatorFactory when setting up
> the JPA provider. The call to createContainerEntityManagerFactory() is made
> in constructor of the PersistenceUnitGBean. In that context, how should the
> lookup for the ValidatorFactory instance for the module be performed?
>
> Rick
>
--
Vamsi
[jira] Created: (GERONIMO-5556) Geronimo admin console seems to be missing the System Modules portlet page
Geronimo admin console seems to be missing the System Modules portlet page
--
Key: GERONIMO-5556
URL: https://issues.apache.org/jira/browse/GERONIMO-5556
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 3.0
Reporter: Joe Bohn
I happened to notice that with the latest trunk image the System Modules
portlet page is missing. I suspect that this was the result of some recent
change reorganizing the navigation panel. It seems that currently the
"Plugins" page and the "System Modules" page are attempting to occupy the same
slot and so the last one processed ("Plugins" in this case) wins. I'll update
the plan and find an unoccupied slot for System Modules. We might want to
reconsider this processing where basically any plugin installed later can trump
and earlier entry in the admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5556) Geronimo admin console seems to be missing the System Modules portlet page
[
https://issues.apache.org/jira/browse/GERONIMO-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn reassigned GERONIMO-5556:
--
Assignee: Joe Bohn
> Geronimo admin console seems to be missing the System Modules portlet page
> --
>
> Key: GERONIMO-5556
> URL: https://issues.apache.org/jira/browse/GERONIMO-5556
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 3.0
>Reporter: Joe Bohn
>Assignee: Joe Bohn
>
> I happened to notice that with the latest trunk image the System Modules
> portlet page is missing. I suspect that this was the result of some recent
> change reorganizing the navigation panel. It seems that currently the
> "Plugins" page and the "System Modules" page are attempting to occupy the
> same slot and so the last one processed ("Plugins" in this case) wins. I'll
> update the plan and find an unoccupied slot for System Modules. We might
> want to reconsider this processing where basically any plugin installed later
> can trump and earlier entry in the admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (YOKO-430) Nothing can be downloaded
[ https://issues.apache.org/jira/browse/YOKO-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kühne resolved YOKO-430. - Resolution: Fixed Fixed download link, this resolves the original problem. > Nothing can be downloaded > - > > Key: YOKO-430 > URL: https://issues.apache.org/jira/browse/YOKO-430 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: Web Site >Reporter: Elad >Assignee: Lars Kühne >Priority: Critical > > Going to the download page: https://cwiki.apache.org/YOKO/download.html and > clicking any of the links leads to an error message such as "The requested > URL > /dist/incubator/yoko/1.0-incubator-M2/yoko-distribution-1.0-incubating-M2-runtime-bin.zip > was not found on this server." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903008#action_12903008 ] Jarek Gawor commented on GERONIMO-5553: --- OpenJPA agent gets registered with TransformerAgent via PersistenceUnitGBean$PersistenceUnitInfoImpl.addTransformer(). That method should be called by OpenJPA and it was the last time I looked at the code... > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang >Assignee: Rick McGuire > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903006#action_12903006 ] Kevan Miller commented on GERONIMO-5553: jpa.jar didn't contain any classes. Instead, MANIFEST.MF pointed to lib/geronimo-transformer-2.1.6.jar So, I believe same basic structure is used in 2.x and 3.0. The OpenJPA javaagent still needs to get registered with the TransformerAgent. That may not be working properly in 3.0. Or there's some more fundamental issue... > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang >Assignee: Rick McGuire > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-5553: -- Assignee: Rick McGuire (was: Donald Woods) Both of these are registering transformers - openjpa2/geronimo-aries-jpa/src/main/java/org/apache/geronimo/aries/jpa/GeronimoPersistenceUnitInfo.java openjpa2/geronimo-persistence-jpa20/src/main/java/org/apache/geronimo/persistence/PersistenceUnitGBean.java So, are all WAR files being turned into WAB files and run as OSGi bundles in 3.0? If so, then using JPA in WAR files is going to require Aries and the geronimo-aries-jpa code, which knows about bundle context, while the normal geronimo-persistence-jpa20 code has no knowledge of bundles and how to access their classloaders??? > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang >Assignee: Rick McGuire > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (YOKO-430) Nothing can be downloaded
[ https://issues.apache.org/jira/browse/YOKO-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903002#action_12903002 ] Lars Kühne commented on YOKO-430: - Will update the page to point to maven.org for now. > Nothing can be downloaded > - > > Key: YOKO-430 > URL: https://issues.apache.org/jira/browse/YOKO-430 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: Web Site >Reporter: Elad >Assignee: Lars Kühne >Priority: Critical > > Going to the download page: https://cwiki.apache.org/YOKO/download.html and > clicking any of the links leads to an error message such as "The requested > URL > /dist/incubator/yoko/1.0-incubator-M2/yoko-distribution-1.0-incubating-M2-runtime-bin.zip > was not found on this server." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Retrieving the ValidatorFactory JNDI entry for a module context.
Hi Rick,
Isn't "javax.faces.validator.beanValidator.ValidatorFactory" attribute
required in the ServletContext only when the web app is using JSF? Then the
place where this attribute can be added is in MyFacesModuleBuilderExtension
using a RuntimeCustomizer (similar to JasperServletContextCustomizer that
adds "org.apache.tomcat.InstanceManager" attribute to ServletContext). By
the time the customize() method is called, the ValidatorFactory is available
in the jndiContext at "comp/ValidatorFactory". I will create a patch for
this for you to review.
On Thu, Aug 26, 2010 at 8:56 PM, Rick McGuire wrote:
> I'm trying to implement the bean validation feature described in section
> EE.6.27 of the Java EE 6 specification. This requires that the web
> container set a property named
> "javax.faces.validator.beanValidator.ValidatorFactory" in the
> ServletContext. I know where this should be set, but I'm having problems
> getting access to the ValidatorFactory instance that I need to satisfy this
> requirement.
>
> For example, I've tried adding the following code to TomcatContainer to set
> this property:
>
>// now set the module context ValidatorFactory in a context
> property.
>try {
>javax.naming.Context ctx =contextInfo.getJndiContext();
>Object validatorFactory
> =ctx.lookup("java:comp/ValidatorFactory");
>
>
> context.getServletContext().setAttribute("javax.faces.validator.beanValidator.ValidatorFactory",validatorFactory);
>}catch (NamingException e) {
> // ignore. We just don't set the property if it's not
> available.
>}
>
>
> This results in a NamingException, which probably means that
> contextInfo.getJndiContext() is not the correct place to retrieve this or
> the context has not yet been set up correctly. I've also tried using an
> InitialContext to do the lookup with the same result. I had a similar
> problem with Jetty where I tried using
>
>try {
>javax.naming.Context ctx
> =integrationContext.getComponentContext();
>Object validatorFactory
> =ctx.lookup("java:comp/ValidatorFactory");
>
> to lookup the factory. How should I be obtaining this value when setting
> up the container?
>
> I have a similar issue with passing the ValidatorFactory when setting up
> the JPA provider. The call to createContainerEntityManagerFactory() is made
> in constructor of the PersistenceUnitGBean. In that context, how should the
> lookup for the ValidatorFactory instance for the module be performed?
>
> Rick
>
--
Vamsi
[jira] Assigned: (YOKO-430) Nothing can be downloaded
[ https://issues.apache.org/jira/browse/YOKO-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Kühne reassigned YOKO-430: --- Assignee: Lars Kühne > Nothing can be downloaded > - > > Key: YOKO-430 > URL: https://issues.apache.org/jira/browse/YOKO-430 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: Web Site >Reporter: Elad >Assignee: Lars Kühne >Priority: Critical > > Going to the download page: https://cwiki.apache.org/YOKO/download.html and > clicking any of the links leads to an error message such as "The requested > URL > /dist/incubator/yoko/1.0-incubator-M2/yoko-distribution-1.0-incubating-M2-runtime-bin.zip > was not found on this server." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903001#action_12903001 ] Donald Woods commented on GERONIMO-5553: Agree, the Javaagent code should work no matter what RuntimeUnenhancedClasses is set to. After more digging, in 2.1.5 we used - JAVA_AGENT_JAR="$GERONIMO_HOME/bin/jpa.jar" but in 3.0, we are using - JAVA_AGENT_JAR="$GERONIMO_HOME/lib/agent/transformer.jar" and there is no jpa.jar anywhere to be found. So, the real question is, where did jpa.jar go and how do we register OpenJPA with framework/modules/geronimo-transformer/src/main/java/org/apache/geronimo/transformer/TransformerAgent.java ? > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang >Assignee: Donald Woods > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902990#action_12902990 ] Kevan Miller commented on GERONIMO-5553: Pre-compilation or special persistence.xml properties should not be required in this case. This sounds like a Geronimo problem which needs to be fixed. If Book.class is not being dynamically enhanced, then seems like something needs to be changed within Geronimo so that enhancement occurs. > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang >Assignee: Donald Woods > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902980#action_12902980 ] Donald Woods commented on GERONIMO-5553: I decompiled your org.apache.sample.entities.Book.class and did not see that it had been enhanced. In OpenJPA 2.0, we have turned RuntimeUnenhancedClasses off/unsupported by default (it was enabled in 1.0 and 1.2) - http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/manual.html#openjpa.RuntimeUnenhancedClasses To enable runtime enhancement (which we strongly discourage for production applications), you need to update your persistence.xml to set the following property - . . . The better solution, is to use build time enhancement, which can be done via ANT, Maven plugin or Eclipse plugin - http://openjpa.apache.org/entity-enhancement.html > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-5553: -- Assignee: Donald Woods > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang >Assignee: Donald Woods > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5555) The version of the application when deploying an EBA is set incorrectly
The version of the application when deploying an EBA is set incorrectly --- Key: GERONIMO- URL: https://issues.apache.org/jira/browse/GERONIMO- Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0-M1 Reporter: Joe Bohn Assignee: Joe Bohn Priority: Minor Fix For: 3.0 When deploying an EBA into Apache Geronimo the version set for the application is pulled from the Application Metadata but it appears that it is constructing the version incorrectly. For example, in the following deployment the application version is set to 0.2.2-incubating rather than 0.2.0-incubating: b...@tetra:~/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT>./bin/deploy -u system -p manager deploy ~/vote-aries-rc3/source-archives/samples-0.2-incubating/blog/blog-jpa-eba/target/org.apache.aries.samples.blog.jpa.eba-0.2-incubating.eba Using GERONIMO_HOME: /Users/bohn/g-images/trunk/geronimo-tomcat7-javaee6-3.0-SNAPSHOT Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home Deployed application/org.apache.aries.samples.blog.jpa.eba/0.2.2-incubating/eba -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 988228
Geronimo Revision: 988228 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100823/build-1400.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100823
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 46 minutes 48 seconds
[INFO] Finished at: Mon Aug 23 14:53:05 EDT 2010
[INFO] Final Memory: 342M/1016M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100823/logs-1400-tomcat/
[INFO] Running TestSuite
[INFO] Tests run: 40, Failures: 34, Errors: 0, Skipped: 0, Time elapsed:
171.615 sec <<< FAILURE!
[INFO] Running TestSuite
[INFO] Tests run: 12, Failures: 8, Errors: 0, Skipped: 0, Time elapsed: 64.358
sec <<< FAILURE!
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100823/logs-1400-jetty/
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Geronimo TestSuite
[INFO] Geronimo TestSuite :: Commands TestSuite
[INFO] Geronimo TestSuite :: Concurrent TestSuite
[INFO] Geronimo TestSuite :: Console Testsuite
[INFO] Geronimo TestSuite :: CORBA TestSuite
[INFO] Geronimo TestSuite :: Deployment Testsuite
[INFO] Geronimo TestSuite :: Enterprise Testsuite
[INFO] Geronimo TestSuite :: Security Testsuite
[INFO] Geronimo TestSuite :: Web-tier Testsuite
[INFO] Geronimo TestSuite :: WebServices TestSuite
[INFO]
[INFO] Building Geronimo TestSuite
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2.2-SNAPSHOT/testsuite-2.2.2-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo TestSuite :: Commands TestSuite
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-commands:2.2.2-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-commands:2.2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-jsr88:2.2.2-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-jsr88:2.2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-system:2.2.2-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-system:2.2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-cli:2.2.2-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-cli:2.2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-kernel:2.2.2-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-kernel:2.2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-crypto:2.2.2-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-crypto:2.2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-common:2.2.2-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-common:2.2.2-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-plugin:2.2.2-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.ap
[jira] Commented: (GERONIMO-5058) Move the term "j2ee" to "javaee" refered by plugin names and package names
[ https://issues.apache.org/jira/browse/GERONIMO-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902903#action_12902903 ] David Jencks commented on GERONIMO-5058: please warn the dev list before making this change. If anyone has local modifications in an affected module it could be confusing to merge. > Move the term "j2ee" to "javaee" refered by plugin names and package names > -- > > Key: GERONIMO-5058 > URL: https://issues.apache.org/jira/browse/GERONIMO-5058 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 3.0 > > > 1. Following are planned to modify: > (1) framework configs: > trunk\framework\configs\j2ee-system\ > trunk\framework\configs\j2ee-security\ > trunk\framework\configs\geronimo-gbean-deployer\src\it\j2ee-system-it1\ > trunk\framework\configs\geronimo-gbean-deployer\src\it\j2ee-system-it2\ > (2) plugins: > trunk\plugins\j2ee\ > trunk\plugins\j2ee\j2ee-server\ > trunk\plugins\j2ee\j2ee-deployer\ > trunk\plugins\j2ee\geronimo-j2ee-schema\ > trunk\plugins\j2ee\geronimo-j2ee-builder\ > trunk\plugins\j2ee\geronimo-j2ee-builder\src\main\java\org\apache\geronimo\j2ee\ > trunk\plugins\j2ee\geronimo-j2ee-builder\src\test\java\org\apache\geronimo\j2ee\ > trunk\plugins\j2ee\geronimo-j2ee\ > trunk\plugins\j2ee\geronimo-j2ee\src\main\java\org\apache\geronimo\j2ee\ > trunk\plugins\j2ee\geronimo-j2ee\src\test\java\org\apache\geronimo\j2ee\ > --- > 2. Keep as is: > trunk\plugins\corba\j2ee-corba-yoko\ > trunk\plugins\webservices\geronimo-webservices-builder\src\test\resources\webservices-j2ee14.xml > --- > 3. jsr77 stuffs, keep as is: > trunk\plugins\j2ee\geronimo-j2ee\src\main\java\org\apache\geronimo\j2ee\j2eeobjectnames\ > trunk\plugins\j2ee\geronimo-j2ee\src\test\java\org\apache\geronimo\j2ee\j2eeobjectnames\ > trunk\framework\modules\geronimo-management\src\main\java\org\apache\geronimo\management\J2EE*.java > trunk\framework\modules\geronimo-management\src\main\java\org\apache\geronimo\management\geronimo\J2EE*.java > trunk\plugins\j2ee\geronimo-j2ee\src\main\java\org\apache\geronimo\j2ee\j2eeobjectnames\J2ee*.java > trunk\plugins\j2ee\geronimo-j2ee\src\main\java\org\apache\geronimo\j2ee\management\impl\J2EE*Impl.java > --- > 4. Schemas, keep as is: > trunk\plugins\j2ee\geronimo-j2ee-schema\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\j2ee\geronimo-j2ee-builder\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\j2ee\geronimo-web-2.5-builder\src\test\resources\j2ee_1_4schema\ > trunk\plugins\j2ee\geronimo-web-2.5-builder\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\j2ee\geronimo-web-2.5-builder\src\test\resources\j2ee_1_2dtd\ > trunk\plugins\openejb\geronimo-openejb-builder\src\test\resources\j2ee_1_4schema\ > trunk\plugins\openejb\geronimo-openejb-builder\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\openejb\geronimo-openejb-builder\src\test\resources\j2ee_1_2dtd\ > trunk\plugins\client\geronimo-client-builder\src\test\resources\j2ee_1_3dtd\ > trunk\plugins\connector-1_6\geronimo-connector-builder-1_6\src\test\resources\j2ee_1_3dtd\ > > 5. j2ee 1.3 & 1.4 stuffs, keep as is: > trunk\testsupport\test-deployment-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.4\test-war-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.4\test-rar-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.4\test-ejb-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.4\test-ear-j2ee_1.4\ > trunk\testsupport\test-deployment-j2ee_1.3\ > trunk\testsupport\test-deployment-j2ee_1.3\test-war-j2ee_1.3\ > trunk\testsupport\test-deployment-j2ee_1.3\test-rar-j2ee_1.3\ > trunk\testsupport\test-deployment-j2ee_1.3\test-ejb-j2ee_1.3\ > trunk\testsupport\test-deployment-j2ee_1.3\test-ear-j2ee_1.3\ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Retrieving the ValidatorFactory JNDI entry for a module context.
I'm trying to implement the bean validation feature described in
section EE.6.27 of the Java EE 6 specification. This requires that the
web container set a property named
"javax.faces.validator.beanValidator.ValidatorFactory" in the
ServletContext. I know where this should be set, but I'm having
problems getting access to the ValidatorFactory instance that I need to
satisfy this requirement.
For example, I've tried adding the following code to TomcatContainer to
set this property:
// now set the module context ValidatorFactory in a context property.
try {
javax.naming.Context ctx =contextInfo.getJndiContext();
Object validatorFactory =ctx.lookup("java:comp/ValidatorFactory");
context.getServletContext().setAttribute("javax.faces.validator.beanValidator.ValidatorFactory",validatorFactory);
}catch (NamingException e) {
// ignore. We just don't set the property if it's not available.
}
This results in a NamingException, which probably means that
contextInfo.getJndiContext() is not the correct place to retrieve this
or the context has not yet been set up correctly. I've also tried using
an InitialContext to do the lookup with the same result. I had a
similar problem with Jetty where I tried using
try {
javax.naming.Context ctx
=integrationContext.getComponentContext();
Object validatorFactory =ctx.lookup("java:comp/ValidatorFactory");
to lookup the factory. How should I be obtaining this value when
setting up the container?
I have a similar issue with passing the ValidatorFactory when setting up
the JPA provider. The call to createContainerEntityManagerFactory() is
made in constructor of the PersistenceUnitGBean. In that context, how
should the lookup for the ValidatorFactory instance for the module be
performed?
Rick
[BUILD] trunk: Failed for Revision: 989664
Geronimo Revision: 989664 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 46 minutes 8 seconds
[INFO] Finished at: Thu Aug 26 10:01:39 EDT 2010
[INFO] Final Memory: 470M/1013M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/logs-0900-tomcat/
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/commands-testsuite/3.0-SNAPSHOT/commands-testsuite-3.0-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo TestSuite :: Commands Testsuite :: Deployer
[INFO]task-segment: [install]
[INFO]
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/plugins/maven-failsafe-plugin/2.5/maven-failsafe-plugin-2.5.pom
9K downloaded (maven-failsafe-plugin-2.5.pom)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire/2.5/surefire-2.5.pom
6K downloaded (surefire-2.5.pom)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/maven-parent/15/maven-parent-15.pom
23K downloaded (maven-parent-15.pom)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/plugins/maven-failsafe-plugin/2.5/maven-failsafe-plugin-2.5.jar
46K downloaded (maven-failsafe-plugin-2.5.jar)
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/deploy-3.0-SNAPSHOT.jar
[org.codehaus.mojo.pluginsupport.logging.Logging] : Initialized
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:3.0-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:3.0-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0-SNAPSHOT/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/commands-testsuite/deploy/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting
[jira] Created: (GERONIMO-5554) blueprint deadlock during server start
blueprint deadlock during server start -- Key: GERONIMO-5554 URL: https://issues.apache.org/jira/browse/GERONIMO-5554 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0 Reporter: Kevan Miller Fix For: 3.0 I stumbled upon a deadlock during server startup. Only seen it once. Was running 'JAVA_OPTS=-verbosegc ./geronimo run --long', but doubt that makes a significant difference. Setting JAVA_OPTS would mean we're running with Java heap/permgen defaults, not the Geronimo defaults. Looked like we were loading rmi-naming. Here's the last console output: Module 2/34 org.apache.geronimo.framework/rmi-naming/3.0-SNAPSHOT/car [GC 49143K->34248K(83008K), 0.0153521 secs] [GC 34257K(83008K), 0.0029171 secs] [GC 34267K(83008K), 0.0015866 secs] Here are the thread dumps from SIGQUIT: Full thread dump Java HotSpot(TM) 64-Bit Server VM (16.3-b01-279 mixed mode): "Blueprint Event Dispatcher: 1" daemon prio=5 tid=11ce57800 nid=0x119b19000 waiting on condition [119b18000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <1080c97f8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:637) "JMX OSGi Agent" daemon prio=5 tid=101e6 nid=0x11996c000 waiting on condition [11996b000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <1078b00a8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:637) "Timer-2" daemon prio=5 tid=11b82b000 nid=0x117a14000 in Object.wait() [117a13000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <108fcf068> (a java.util.TaskQueue) at java.lang.Object.wait(Object.java:485) at java.util.TimerThread.mainLoop(Timer.java:483) - locked <108fcf068> (a java.util.TaskQueue) at java.util.TimerThread.run(Timer.java:462) "gogo shell pipe thread" daemon prio=5 tid=102aca800 nid=0x11961a000 runnable [119619000] java.lang.Thread.State: RUNNABLE at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:199) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) - locked <107e652e0> (a java.io.BufferedInputStream) at jline.Terminal.readCharacter(Terminal.java:99) at org.apache.felix.karaf.shell.console.jline.Console$Pipe.run(Console.java:386) at java.lang.Thread.run(Thread.java:637) "Karaf Shell Console Thread" daemon prio=5 tid=11ca14800 nid=0x118f55000 waiting on condition [118f54000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <108b6ac38> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925) at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:317) at org.apache.felix.karaf.shell.console.jline.Console$ConsoleInputStream.read(Console.java:324) at org.apache.felix.karaf.shell.console.jline.Console$ConsoleInputStream.read(Console.java:341) at jline.Terminal.readCharacter(Terminal.java:99) at jline.UnixTerminal.readVirtualKey(UnixTerminal.java:144) at jline.ConsoleReader.readVirtualKey(ConsoleReader.java:1504) at jline.ConsoleReader.readBinding(ConsoleReader.java:674) at jline.ConsoleReader.readLine(Consol
[jira] Commented: (YOKO-430) Nothing can be downloaded
[ https://issues.apache.org/jira/browse/YOKO-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902820#action_12902820 ] Kevan Miller commented on YOKO-430: --- Sub-project status does not prevent Yoko from being available in the dist/geronimo directory. There needs to be a review of our release practices and, if deemed necessary, release artifacts be made available from the dist directory. At a minimum, we need to update the Yoko documentation to be accurate. Clearly it's not. > Nothing can be downloaded > - > > Key: YOKO-430 > URL: https://issues.apache.org/jira/browse/YOKO-430 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: Web Site >Reporter: Elad >Priority: Critical > > Going to the download page: https://cwiki.apache.org/YOKO/download.html and > clicking any of the links leads to an error message such as "The requested > URL > /dist/incubator/yoko/1.0-incubator-M2/yoko-distribution-1.0-incubating-M2-runtime-bin.zip > was not found on this server." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (YOKO-430) Nothing can be downloaded
[ https://issues.apache.org/jira/browse/YOKO-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902794#action_12902794 ] Rick McGuire commented on YOKO-430: --- The yoko incubating project never developed a healthy community, so the yoko code has become a sub-component of the Geronimo server. Like other subcomponents (e.g., xbean), the artifacts are only published to the maven central repository, > Nothing can be downloaded > - > > Key: YOKO-430 > URL: https://issues.apache.org/jira/browse/YOKO-430 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: Web Site >Reporter: Elad >Priority: Critical > > Going to the download page: https://cwiki.apache.org/YOKO/download.html and > clicking any of the links leads to an error message such as "The requested > URL > /dist/incubator/yoko/1.0-incubator-M2/yoko-distribution-1.0-incubating-M2-runtime-bin.zip > was not found on this server." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 989477
Geronimo Revision: 989477 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 40 minutes 17 seconds [INFO] Finished at: Thu Aug 26 03:45:23 EDT 2010 [INFO] Final Memory: 456M/1012M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100826/logs-0300-tomcat/ [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure
[jira] Resolved: (GERONIMODEVTOOLS-669) Modification to VM arguements is lost
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-669. Fix Version/s: 3.0 Resolution: Fixed Server VM arguments section was added because no solution found to save the VM arguments in configuration dialog. Now, I find a solution to save VM arugments in configuration dialog. I override the performApply() method in GeronimoLaunchConfigurationTabGroup. So it's time to remove VM arguments section. Submit the fix in revision #989524 > Modification to VM arguements is lost > -- > > Key: GERONIMODEVTOOLS-669 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-669 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: OS:win xp > JDK:1.6_U18 >Reporter: Lu Jiang >Assignee: Delos Dai >Priority: Minor > Fix For: 3.0 > > > Steps to reproduce: > 1. new a Geronimo server in Eclipse > 2.Double click the server,then you can see the server overview. > 3.Under Gereral Information,click the link open lauch configuration. > 4.Click Arguements tag,and and do some modifications to VM arguements. > 5.Click Apply and OK. > 6.Reopen the lauch configuration. > The modifications to VM arguements are lost. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902769#action_12902769 ] Han Hong Fang commented on GERONIMO-5553: - Related JIRA: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671 > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5553) Fail to enchance entities on Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lu Jiang updated GERONIMO-5553: --- Attachment: booknew.war This is the simple jpa demo I used for test. > Fail to enchance entities on Geronimo > - > > Key: GERONIMO-5553 > URL: https://issues.apache.org/jira/browse/GERONIMO-5553 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: persistence >Affects Versions: 3.0 > Environment: OS:win xp > Geronimo :3.0 20100824 build >Reporter: Lu Jiang > Fix For: 3.0 > > Attachments: booknew.war > > > I tried to deploy a simple jpa sample on geronimo.But when persist data into > database. > Following exception will occur. > > org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance > "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. > Ensure that it has been enhanced. > FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-671) cannot start geronimo after adding javaagent arguements
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902768#action_12902768 ] Han Hong Fang commented on GERONIMODEVTOOLS-671: Thanks for attaching the jar file. I tested with jpa.jar, above-mentioned exception occurs when starting server in eclipse using javaagent argument. But same exception when starting server outside eclipse. Noticed that https://issues.apache.org/jira/browse/GERONIMO-5553 is opened under server for openjpa enhancement, so I suggest to close this JIRA. Regards, Han Hong Fang > cannot start geronimo after adding javaagent arguements > --- > > Key: GERONIMODEVTOOLS-671 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: OS:windows xp > Eclipse :3.6 > Geronimo :3.0 >Reporter: Lu Jiang >Assignee: Delos Dai >Priority: Minor > Attachments: jpa.jar > > > Add something like -javaagent:"D:/jpa.jar" to Server VM arguements in > eclipse. > Then geronimo will fail to start for the following error: > java.lang.reflect.InvocationTargetException > 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 > sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323) > at > sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338) > Caused by: java.lang.NoClassDefFoundError: > org/apache/commons/lang/exception/NestableRuntimeException > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) > at java.lang.ClassLoader.defineClass(ClassLoader.java:616) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) > at java.net.URLClassLoader.access$000(URLClassLoader.java:58) > at java.net.URLClassLoader$1.run(URLClassLoader.java:197) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > at > org.apache.openjpa.enhance.PCEnhancerAgent.premain(PCEnhancerAgent.java:127) > ... 6 more > Caused by: java.lang.ClassNotFoundException: > org.apache.commons.lang.exception.NestableRuntimeException > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > ... 19 more > Exception in thread "main" FATAL ERROR in native method: processing of > -javaagent failed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5553) Fail to enchance entities on Geronimo
Fail to enchance entities on Geronimo - Key: GERONIMO-5553 URL: https://issues.apache.org/jira/browse/GERONIMO-5553 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: persistence Affects Versions: 3.0 Environment: OS:win xp Geronimo :3.0 20100824 build Reporter: Lu Jiang Fix For: 3.0 I tried to deploy a simple jpa sample on geronimo.But when persist data into database. Following exception will occur. org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance "org.apache.sample.entities.b...@97781f" to PersistenceCapable failed. Ensure that it has been enhanced. FailedObject: org.apache.sample.entities.b...@97781f -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-671) cannot start geronimo after adding javaagent arguements
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lu Jiang updated GERONIMODEVTOOLS-671: -- Attachment: jpa.jar Hi, I used this jpa.jar in attatchment.It's pulled from geronimo repository. > cannot start geronimo after adding javaagent arguements > --- > > Key: GERONIMODEVTOOLS-671 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: OS:windows xp > Eclipse :3.6 > Geronimo :3.0 >Reporter: Lu Jiang >Assignee: Delos Dai >Priority: Minor > Attachments: jpa.jar > > > Add something like -javaagent:"D:/jpa.jar" to Server VM arguements in > eclipse. > Then geronimo will fail to start for the following error: > java.lang.reflect.InvocationTargetException > 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 > sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323) > at > sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338) > Caused by: java.lang.NoClassDefFoundError: > org/apache/commons/lang/exception/NestableRuntimeException > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) > at java.lang.ClassLoader.defineClass(ClassLoader.java:616) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) > at java.net.URLClassLoader.access$000(URLClassLoader.java:58) > at java.net.URLClassLoader$1.run(URLClassLoader.java:197) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > at > org.apache.openjpa.enhance.PCEnhancerAgent.premain(PCEnhancerAgent.java:127) > ... 6 more > Caused by: java.lang.ClassNotFoundException: > org.apache.commons.lang.exception.NestableRuntimeException > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > ... 19 more > Exception in thread "main" FATAL ERROR in native method: processing of > -javaagent failed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-667) Configuration elements duplicated in Geronimo deployment plan editor for geronimo-application.xml
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902758#action_12902758 ] Han Hong Fang commented on GERONIMODEVTOOLS-667: By checking schema geronimo-application-2.0.xsd, I think modules and external modules on deployment plan editor are for element module and ext-module respectively. Ref to the quotation below. STARTSTART An optional module element which defines various modules included in the enterprise application archive. It mirrors the moduleType defined by application_1_4.xsd and adds an optional alt-dd element defining a Geronimo specific deployment descriptor. It is used to define modules included in this application externally and these module could be included in the archive, or they may reside in Geronimo repository. It defines optional internal-path or external-path to module/repository element being referenced. END END > Configuration elements duplicated in Geronimo deployment plan editor for > geronimo-application.xml > - > > Key: GERONIMODEVTOOLS-667 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-667 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: OS: Windows XP SP3 > JDK: Sun JDK 1.6.0_20 > Eclipse 3.6 >Reporter: Wang Guang Zhe >Assignee: Delos Dai > > When I test the geronimo deployment plan editor for geronimo-application.xml, > I found in the deployment configuration part, there are "modules" and > "external modules" elements, which are duplicated in the configuration > content. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-671) cannot start geronimo after adding javaagent arguements
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902757#action_12902757 ] Han Hong Fang commented on GERONIMODEVTOOLS-671: I can successfully start Geronimo in eclipse and outside eclilpse using -javaagent argument pointing to a dummy agent which does nothing except prints a greeting message. Can you upload your jpa.jar for problem reproducing? Regards, Han Hong Fang > cannot start geronimo after adding javaagent arguements > --- > > Key: GERONIMODEVTOOLS-671 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: OS:windows xp > Eclipse :3.6 > Geronimo :3.0 >Reporter: Lu Jiang >Assignee: Delos Dai >Priority: Minor > > Add something like -javaagent:"D:/jpa.jar" to Server VM arguements in > eclipse. > Then geronimo will fail to start for the following error: > java.lang.reflect.InvocationTargetException > 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 > sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323) > at > sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338) > Caused by: java.lang.NoClassDefFoundError: > org/apache/commons/lang/exception/NestableRuntimeException > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) > at java.lang.ClassLoader.defineClass(ClassLoader.java:616) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) > at java.net.URLClassLoader.access$000(URLClassLoader.java:58) > at java.net.URLClassLoader$1.run(URLClassLoader.java:197) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > at > org.apache.openjpa.enhance.PCEnhancerAgent.premain(PCEnhancerAgent.java:127) > ... 6 more > Caused by: java.lang.ClassNotFoundException: > org.apache.commons.lang.exception.NestableRuntimeException > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > ... 19 more > Exception in thread "main" FATAL ERROR in native method: processing of > -javaagent failed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
