[jira] Closed: (GERONIMO-5532) Add config-substitution.properties overrrides options to geronimo-maven-plugin start-server goal
[ https://issues.apache.org/jira/browse/GERONIMO-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-5532. -- Resolution: Invalid We can use existing properties attribute of geronimo -maven-plugin to set oroperty value in config-substituions.properties like below, so close this invalide improvement. optionSets optionSet iddefault/id options option-XX:MaxPermSize=256m/option option-Dnode.name=server1/option /options properties property nameorg.apache.geronimo.config.substitution.PortOffset/name value1/value /property property nameorg.apache.geronimo.config.substitution.MulticastEnabled/name valuetrue/value /property /properties /optionSet /optionSets Add config-substitution.properties overrrides options to geronimo-maven-plugin start-server goal - Key: GERONIMO-5532 URL: https://issues.apache.org/jira/browse/GERONIMO-5532 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: geronimo-maven-plugin Affects Versions: 2.2.2 Environment: Add config-substitution.properties overrride to georonimo maven plugin start-server plugin, so that, users can change substitution properties before start-server. Reporter: viola.lu Assignee: viola.lu Priority: Minor May we can use System.setProperty(org.apache.geronimo.config.substitution.PortOffset, + actualPortOffset); something like that to apply changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (YOKO-430) Nothing can be downloaded
[ https://issues.apache.org/jira/browse/YOKO-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elad updated YOKO-430: -- Priority: Critical (was: Blocker) Reduced priority since items can be downloaded from http://repo2.maven.org/maven2/org/apache/yoko/ 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] Created: (GERONIMO-5549) Remove command-testsuite/gshell
Remove command-testsuite/gshell --- Key: GERONIMO-5549 URL: https://issues.apache.org/jira/browse/GERONIMO-5549 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: testsuite Affects Versions: 3.0 Reporter: viola.lu Assignee: viola.lu Priority: Minor Fix For: 3.0 Gshell is removed from Geronimo 3.0, so remove its corresponding tests from command-testsuite -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5547) Geronimo_3.0_trunk can't change the password for all users and register new user
[ https://issues.apache.org/jira/browse/GERONIMO-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhen Zhang closed GERONIMO-5547. Resolution: Invalid It is Ok now in admin console Geronimo_3.0_trunk can't change the password for all users and register new user - Key: GERONIMO-5547 URL: https://issues.apache.org/jira/browse/GERONIMO-5547 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 3.0 Environment: OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Priority: Critical Fix For: 3.0 DO NOT start server at first ! setps to recur: 1. cd [GERONIMO HOME]\var\security\ 2. open users.properties and change the password of system 3. save the change and startup the Geronimo server 4. open http://localhost:8080/console; 5. login with User name system and your new password ,but you can't access to the admin console 6. cd [GERONIMO HOME]\var\security\ ,then open users.properties, you will see your new password is not encode Geronimo log info: 2010-08-24 10:45:42,343 ERROR [AbstractEncryption] Unable to decrypt java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2281) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:781) at java.io.ObjectInputStream.init(ObjectInputStream.java:280) at org.apache.geronimo.crypto.AbstractEncryption.decrypt(AbstractEncryption.java:76) at org.apache.geronimo.crypto.EncryptionManager.decrypt(EncryptionManager.java:108) at org.apache.geronimo.security.realm.providers.PropertiesFileLoginModule.login(PropertiesFileLoginModule.java:203) at org.apache.felix.karaf.jaas.boot.ProxyLoginModule.login(ProxyLoginModule.java:83) 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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) at javax.security.auth.login.LoginContext$5.run(LoginContext.java:706) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:703) at javax.security.auth.login.LoginContext.login(LoginContext.java:575) at org.apache.geronimo.security.ContextManager.login(ContextManager.java:93) at org.apache.geronimo.tomcat.security.impl.GeronimoLoginService.login(GeronimoLoginService.java:62) at org.apache.geronimo.tomcat.security.impl.GeronimoLoginService.login(GeronimoLoginService.java:53) at org.apache.geronimo.tomcat.security.authentication.FormAuthenticator.validateRequest(FormAuthenticator.java:153) at org.apache.geronimo.tomcat.security.SecurityValve.invoke(SecurityValve.java:62) at org.apache.geronimo.tomcat.security.jacc.JACCSecurityValve.invoke(JACCSecurityValve.java:54) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:700) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:146) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:108) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:402) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:254) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:267) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:245) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:260) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:241) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:371) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at
[jira] Closed: (GERONIMO-5509) Invalid deployment descriptor error: cvc-attribute.4: The value '2.0' does not equal the fixed value '1.0' of attribute 'version'
[ https://issues.apache.org/jira/browse/GERONIMO-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-5509. -- Resolution: Fixed This error disappeared after Geronimo 5495 was fixed. Latest build 2010.08.24-15:32:37.578+0800. But there is a he application was not deployed. xml problem for web app web.war org.apache.geronimo.common.DeploymentException: xml problem for web app web.war So close this one, open another jira to track web.war xml problem. Invalid deployment descriptor error: cvc-attribute.4: The value '2.0' does not equal the fixed value '1.0' of attribute 'version' - Key: GERONIMO-5509 URL: https://issues.apache.org/jira/browse/GERONIMO-5509 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Environment: ubuntu 8.04 x86-32 sun java 1.6.0_20 Reporter: Forrest Xia Assignee: viola.lu Attachments: dayTrader-derby-plan.xml, daytrader-webprofile-ear-3.0-SNAPSHOT.ear Steps: 1. start geronimo 3.0 snapshot web profile build 2. deploy the attached daytrader application with the attached deployment plan in the admin console 3. then an deployment exception throws out like this: 2010-08-09 12:24:03,465 ERROR [DeploymentPortlet] Deployment Failed Error parsing geronimo-openejb.xml with xmlbeans. For debug purposes, XML content written to: /home/forrestxm/temp/geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT/var/temp/openejb-jar-5019648766953734149.xml org.apache.geronimo.common.DeploymentException: Error parsing geronimo-openejb.xml with xmlbeans. For debug purposes, XML content written to: /home/forrestxm/temp/geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT/var/temp/openejb-jar-5019648766953734149.xml at org.apache.geronimo.openejb.deployment.XmlUtil.convertToXmlbeans(XmlUtil.java:107) at org.apache.geronimo.openejb.deployment.EjbModuleBuilder.createModule(EjbModuleBuilder.java:372) at org.apache.geronimo.openejb.deployment.EjbModuleBuilder.createModule(EjbModuleBuilder.java:258) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:864) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:457) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:319) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:231) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: errors: error: cvc-attribute.4: The value '2.0' does not equal the fixed value '1.0' of attribute 'version' Descriptor: xml-fragment xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; xmlns:pkgen=http://openejb.apache.org/xml/ns/pkgen-2.1; xmlns:naming=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:o=http://openejb.apache.org/xml/ns/openejb-jar-2.2; xmlns:ns6=http://geronimo.apache.org/xml/ns/openejb-clustering-wadi-1.2; xmlns:ns7=http://geronimo.apache.org/xml/ns/j2ee/ejb/openejb-2.0; xmlns:ns8=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:ns9=http://java.sun.com/xml/ns/persistence; ns9:persistence version=2.0 ns9:persistence-unit name=daytrader ns9:properties ns9:property name=openjpa.jdbc.DBDictionary value=derby/ /ns9:properties /ns9:persistence-unit /ns9:persistence /xml-fragment at org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.validateDD(XmlBeansUtil.java:188) at
[jira] Created: (GERONIMO-5550) xml problem for web.war error when deploy daytrader
xml problem for web.war error when deploy daytrader -- Key: GERONIMO-5550 URL: https://issues.apache.org/jira/browse/GERONIMO-5550 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: web Affects Versions: 3.0 Environment: WinXP JDk: 1.6.0_20 Reporter: viola.lu Assignee: viola.lu Priority: Minor Steps: 1.Deploy attached daytrader sample from https://issues.apache.org/jira/browse/GERONIMO-5509 2.Got errors below: The application was not deployed. xml problem for web app web.war org.apache.geronimo.common.DeploymentException: xml problem for web app web.war at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:381) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule(TomcatModuleBuilder.java:275) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:272) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:153) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:864) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:457) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:319) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:231) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: errors: error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): configId error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): parentId error: cvc-complex-type.2.4a: Expected elements 'environm...@http://geronimo.apache.org/xml/ns/deployment-1.2 context-r...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work-...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster...@http://geronimo.apache.org/xml/ns/j2ee/application-2.0 web-contai...@http://geronimo.apache.org/xml/ns/naming-1.2 h...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross-cont...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 disable-cook...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 valve-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 listener-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 tomcat-re...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 mana...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 clus...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 abstract-naming-en...@http://geronimo.apache.org/xml/ns/naming-1.2 env-en...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-local-...@http://geronimo.apache.org/xml/ns/naming-1.2 service-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-env-...@http://geronimo.apache.org/xml/ns/naming-1.2 message-destinat...@http://geronimo.apache.org/xml/ns/naming-1.2 security-realm-n...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 serv...@http://geronimo.apache.org/xml/ns/deployment-1.2' instead of 'context-priority-classloa...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here Descriptor: false jdbc/TradeDataSource TradeDataSource at org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.validateDD(XmlBeansUtil.java:188) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:375) ... 19 more -- This message is automatically generated by JIRA. - You can reply to this email to add a
[BUILD] trunk: Failed for Revision: 988409
Geronimo Revision: 988409 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 41 minutes 46 seconds [INFO] Finished at: Tue Aug 24 03:46:56 EDT 2010 [INFO] Final Memory: 454M/1013M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/logs-0300-tomcat/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 15.509 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.94 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/logs-0300-jetty/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 16.921 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/samples-0300.log Build status: OK
[jira] Resolved: (GERONIMO-4995) Jetty8 under osgi
[ https://issues.apache.org/jira/browse/GERONIMO-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-4995. Resolution: Fixed Jetty8 under osgi - Key: GERONIMO-4995 URL: https://issues.apache.org/jira/browse/GERONIMO-4995 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: Jetty, osgi Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Most of the bundlelizing is done for jetty but we should have a jira issue to hang further fixes onto. For instance the jetty8-deployer plugin doesn't start due to mixed up car-maven-plugin configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4995) Jetty8 under osgi
[ https://issues.apache.org/jira/browse/GERONIMO-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-4995. -- Jetty8 under osgi - Key: GERONIMO-4995 URL: https://issues.apache.org/jira/browse/GERONIMO-4995 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: Jetty, osgi Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Most of the bundlelizing is done for jetty but we should have a jira issue to hang further fixes onto. For instance the jetty8-deployer plugin doesn't start due to mixed up car-maven-plugin configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4360) Connector 1.6 implementation
[ https://issues.apache.org/jira/browse/GERONIMO-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-4360. Resolution: Fixed Connector 1.6 implementation Key: GERONIMO-4360 URL: https://issues.apache.org/jira/browse/GERONIMO-4360 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: connector, javaee6 Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 We'll need some changes in component and in the wrapping in server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4360) Connector 1.6 implementation
[ https://issues.apache.org/jira/browse/GERONIMO-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-4360. -- Connector 1.6 implementation Key: GERONIMO-4360 URL: https://issues.apache.org/jira/browse/GERONIMO-4360 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: connector, javaee6 Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 We'll need some changes in component and in the wrapping in server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5092) Update the CORBA plugins for the OSGi classloading model.
[ https://issues.apache.org/jira/browse/GERONIMO-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-5092. -- Update the CORBA plugins for the OSGi classloading model. -- Key: GERONIMO-5092 URL: https://issues.apache.org/jira/browse/GERONIMO-5092 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: CORBA, javaee6, osgi Affects Versions: 3.0 Reporter: Rick McGuire Fix For: 3.0 -- 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-tabpanelfocusedCommentId=12901815#action_12901815 ] Rick McGuire commented on GERONIMO-5058: Rex, are you still planning on making these changes? 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.
[jira] Assigned: (GERONIMO-4926) Fix ConfigurationMonitorGBean management of PCRegistry class.
[ https://issues.apache.org/jira/browse/GERONIMO-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire reassigned GERONIMO-4926: -- Assignee: Rick McGuire Fix ConfigurationMonitorGBean management of PCRegistry class. -- Key: GERONIMO-4926 URL: https://issues.apache.org/jira/browse/GERONIMO-4926 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Rick McGuire Assignee: Rick McGuire Fix For: 3.0 The ConfigurationMonitorGBean maintains a cache of active configuration class loaders and when a configuration is shutdown, it tells the openjpa PCRegistry to remove any cached classes associated with that class loader. This won't work any more because there is no such thing as a configuration class loader. It might be possible to get the bundle for the class loader, then request the list of managed classes and iterate through the classes looking for any class that might be defined using a BundleReference class loader for that bundle. If one is found, then that classloader can be used for the deregister() operation. For now, the insertion of the map entries is disabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Deploy ear with Geronimo 2.2
I've resolved the problem. I've packed a new ear with a new jar and new war, using the same content for xml plans as the old ear and deployment is fine using the deployer of Geronimo 2.2. I don't know why, but I think the ear file was corrupt and only G2.2 is able to detect it if deployment is performed through command line. Thanks for your time -- View this message in context: http://apache-geronimo.328035.n3.nabble.com/Deploy-ear-with-Geronimo-2-2-tp1294285p1309179.html Sent from the Development mailing list archive at Nabble.com.
[jira] Resolved: (GERONIMO-4926) Fix ConfigurationMonitorGBean management of PCRegistry class.
[ https://issues.apache.org/jira/browse/GERONIMO-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-4926. Resolution: Duplicate Duplicate of GERONIMO-5068 Fix ConfigurationMonitorGBean management of PCRegistry class. -- Key: GERONIMO-4926 URL: https://issues.apache.org/jira/browse/GERONIMO-4926 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Rick McGuire Assignee: Rick McGuire Fix For: 3.0 The ConfigurationMonitorGBean maintains a cache of active configuration class loaders and when a configuration is shutdown, it tells the openjpa PCRegistry to remove any cached classes associated with that class loader. This won't work any more because there is no such thing as a configuration class loader. It might be possible to get the bundle for the class loader, then request the list of managed classes and iterate through the classes looking for any class that might be defined using a BundleReference class loader for that bundle. If one is found, then that classloader can be used for the deregister() operation. For now, the insertion of the map entries is disabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4926) Fix ConfigurationMonitorGBean management of PCRegistry class.
[ https://issues.apache.org/jira/browse/GERONIMO-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed GERONIMO-4926. -- Fix ConfigurationMonitorGBean management of PCRegistry class. -- Key: GERONIMO-4926 URL: https://issues.apache.org/jira/browse/GERONIMO-4926 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Rick McGuire Assignee: Rick McGuire Fix For: 3.0 The ConfigurationMonitorGBean maintains a cache of active configuration class loaders and when a configuration is shutdown, it tells the openjpa PCRegistry to remove any cached classes associated with that class loader. This won't work any more because there is no such thing as a configuration class loader. It might be possible to get the bundle for the class loader, then request the list of managed classes and iterate through the classes looking for any class that might be defined using a BundleReference class loader for that bundle. If one is found, then that classloader can be used for the deregister() operation. For now, the insertion of the map entries is disabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ConfigurationUtil.getEditableConfigurationManager no longer needed?
I've been going through the open Jiras trying to figure out what the dangling work items are left. This https://issues.apache.org/jira/browse/GERONIMO-4925 appears to be one that should have something done with it. What is the state of the EditableConfigurationManager? There still appear to be some dependencies on this in the code, but I'm not sure that code is actually functional any more. I think if this is obsolete, then we should remove the EditableCoinfigurationManager and fix the code that uses it to use its logical replacement. If it is functional, then we can close this Jira out. Rick On 10/23/2009 4:30 AM, David Jencks wrote: On Oct 22, 2009, at 10:58 PM, Ivan wrote: Thanks, David, I opened a JIRA 4925 to track it. I will temporarily enable it, so that we would not have any compile error in the plugins. After the main integration work has been done, we could have time to consider whether we still need it, or we have a better way to implement it. About generating the bundle meta data in the deployment process, I am interested that how it would be implemented in the deployer, use BND or ASM tool ? There is probably a better solution, but so far we've been ok with a simple calculation of the packages needed by the gbeans plus dynamic import package *. I wrote some code in ExecutableConfigurationUtil that collects the classes needed for the gbeans in the plan and saves the list of packages to a file, then the ArchiveCarMojo reads this and uses it to construct a manifest. Since IMO we should only be using packed plugins in 3.0 we should move all the archive functionality into the deployer somewhere, including figuring out the manifest needed. Very likely the archiveing code can just go into ExecutableConfigurationUtil. thanks david jencks 2009/10/23 David Jencks david_jen...@yahoo.com mailto:david_jen...@yahoo.com To me, this issue of getting runtime modifications of running plugins to persist or work at all is a very low priority item. I think there is a very very good chance that once much of the server is running we will step back look at what we have and decide to completely change how this works, or if we allow it. I think there are much more pressing issues such as the fact that the osgi manifest info is put into plugins by the car-maven-plugin rather than a deployer, so that the only way to build a plugin or deploy an application is through a maven build and assembling a custom server. So, I would comment out or disable any functionality that requires EditableConfigurationManager and file a jira so we don't forget about it. However, as long as this doesn't constrain the basic architecture in any way, I have no problem with anyone working on it. thanks david jencks On Oct 22, 2009, at 7:50 AM, Ivan wrote: Hi, David: Do you have more comment on it ? Currently, I think that EditableConfigurationManager is a requried function, and I am sure that something is need to improve for it, Such as, it is better that we could have an attribute to mark it as not started, because while we stop the connector in the console, after we restarting the server, the connector will start again IIRC. 2009/10/22 Ivan xhh...@gmail.com mailto:xhh...@gmail.com The ActiveMQ plugin also depends on it. Basically, since we allow the user to add new gbeans in the config.xml file for an existed configuration, we may need the API to do it programically. 2009/10/22 Rick McGuire rick...@gmail.com mailto:rick...@gmail.com David Jencks wrote: I would rather make the server work without this functionality. I'm really not sure its appropriate to modify plugins in this way. Can we catalog the places this functionality is absolutely required before we put it back in? Well, to start with, both the jetty and tomcat plugins are using it, and not just for running the tests. Rick thanks david jencks On Oct 21, 2009, at 6:06 AM, Ivan wrote: If no objection, I will try to recover those functions tomorrow, including the help methods in the ConfigurationUtil. 2009/10/21 Ivan xhh...@gmail.com mailto:xhh...@gmail.com mailto:xhh...@gmail.com mailto:xhh...@gmail.com Seems that EditableConfigurationManager support is removed (at least temporarily) in the Geronimo kernel. I am not sure that adding the gbeans to the existed configuration in the runtime is a good
[jira] Commented: (GERONIMO-5550) xml problem for web.war error when deploy daytrader
[ https://issues.apache.org/jira/browse/GERONIMO-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901888#action_12901888 ] Forrest Xia commented on GERONIMO-5550: --- Another jira https://issues.apache.org/jira/browse/GERONIMO-5511 related to this one. xml problem for web.war error when deploy daytrader -- Key: GERONIMO-5550 URL: https://issues.apache.org/jira/browse/GERONIMO-5550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: web Affects Versions: 3.0 Environment: WinXP JDk: 1.6.0_20 Reporter: viola.lu Assignee: viola.lu Priority: Minor Steps: 1.Deploy attached daytrader sample from https://issues.apache.org/jira/browse/GERONIMO-5509 2.Got errors below: The application was not deployed. xml problem for web app web.war org.apache.geronimo.common.DeploymentException: xml problem for web app web.war at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:381) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule(TomcatModuleBuilder.java:275) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:272) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:153) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:864) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:457) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:319) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:231) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: errors: error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): configId error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): parentId error: cvc-complex-type.2.4a: Expected elements 'environm...@http://geronimo.apache.org/xml/ns/deployment-1.2 context-r...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work-...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster...@http://geronimo.apache.org/xml/ns/j2ee/application-2.0 web-contai...@http://geronimo.apache.org/xml/ns/naming-1.2 h...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross-cont...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 disable-cook...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 valve-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 listener-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 tomcat-re...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 mana...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 clus...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 abstract-naming-en...@http://geronimo.apache.org/xml/ns/naming-1.2 env-en...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-local-...@http://geronimo.apache.org/xml/ns/naming-1.2 service-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-env-...@http://geronimo.apache.org/xml/ns/naming-1.2 message-destinat...@http://geronimo.apache.org/xml/ns/naming-1.2 security-realm-n...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 serv...@http://geronimo.apache.org/xml/ns/deployment-1.2' instead of 'context-priority-classloa...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here Descriptor: false
[jira] Assigned: (GERONIMO-5511) context-priority-classloader is not allowed in geronimo-web.xml for backwards compatibility
[ https://issues.apache.org/jira/browse/GERONIMO-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu reassigned GERONIMO-5511: -- Assignee: viola.lu context-priority-classloader is not allowed in geronimo-web.xml for backwards compatibility --- Key: GERONIMO-5511 URL: https://issues.apache.org/jira/browse/GERONIMO-5511 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: web Affects Versions: 3.0 Environment: Ubuntu 8.04 x86-32 Sun java 1.6.0_20 Reporter: Forrest Xia Assignee: viola.lu Priority: Minor If the geronimo-web.xml includes element context-priority-classloader, the deployment will fail at validating xml schema like this: 2010-08-09 13:02:06,051 ERROR [DeploymentPortlet] Deployment failed xml problem for web app web.war org.apache.geronimo.common.DeploymentException: xml problem for web app web.war at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:381) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule(TomcatModuleBuilder.java:275) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:273) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:153) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:864) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:457) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:319) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:231) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: errors: error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): configId error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): parentId error: cvc-complex-type.2.4a: Expected elements 'environm...@http://geronimo.apache.org/xml/ns/deployment-1.2 context-r...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work-...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster...@http://geronimo.apache.org/xml/ns/j2ee/application-2.0 web-contai...@http://geronimo.apache.org/xml/ns/naming-1.2 h...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross-cont...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 disable-cook...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 valve-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 listener-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 tomcat-re...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 mana...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 clus...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 abstract-naming-en...@http://geronimo.apache.org/xml/ns/naming-1.2 env-en...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-local-...@http://geronimo.apache.org/xml/ns/naming-1.2 service-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-env-...@http://geronimo.apache.org/xml/ns/naming-1.2 message-destinat...@http://geronimo.apache.org/xml/ns/naming-1.2 security-realm-n...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 serv...@http://geronimo.apache.org/xml/ns/deployment-1.2' instead of 'context-priority-classloa...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here
[jira] Closed: (GERONIMO-5550) xml problem for web.war error when deploy daytrader
[ https://issues.apache.org/jira/browse/GERONIMO-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-5550. -- Resolution: Duplicate Close it, duplicate with https://issues.apache.org/jira/browse/GERONIMO-5511 xml problem for web.war error when deploy daytrader -- Key: GERONIMO-5550 URL: https://issues.apache.org/jira/browse/GERONIMO-5550 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: web Affects Versions: 3.0 Environment: WinXP JDk: 1.6.0_20 Reporter: viola.lu Assignee: viola.lu Priority: Minor Steps: 1.Deploy attached daytrader sample from https://issues.apache.org/jira/browse/GERONIMO-5509 2.Got errors below: The application was not deployed. xml problem for web app web.war org.apache.geronimo.common.DeploymentException: xml problem for web app web.war at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.getTomcatWebApp(TomcatModuleBuilder.java:381) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule(TomcatModuleBuilder.java:275) at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:272) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:153) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.addModules(EARConfigBuilder.java:864) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:457) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:319) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:231) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.xmlbeans.XmlException: Invalid deployment descriptor: errors: error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): configId error: cvc-complex-type.3.2.1: Attribute not allowed (no wildcards allowed): parentId error: cvc-complex-type.2.4a: Expected elements 'environm...@http://geronimo.apache.org/xml/ns/deployment-1.2 context-r...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 work-...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cluster...@http://geronimo.apache.org/xml/ns/j2ee/application-2.0 web-contai...@http://geronimo.apache.org/xml/ns/naming-1.2 h...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 cross-cont...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 disable-cook...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 valve-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 listener-ch...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 tomcat-re...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 mana...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 clus...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 abstract-naming-en...@http://geronimo.apache.org/xml/ns/naming-1.2 env-en...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-...@http://geronimo.apache.org/xml/ns/naming-1.2 ejb-local-...@http://geronimo.apache.org/xml/ns/naming-1.2 service-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-...@http://geronimo.apache.org/xml/ns/naming-1.2 resource-env-...@http://geronimo.apache.org/xml/ns/naming-1.2 message-destinat...@http://geronimo.apache.org/xml/ns/naming-1.2 security-realm-n...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1 serv...@http://geronimo.apache.org/xml/ns/deployment-1.2' instead of 'context-priority-classloa...@http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-2.0.1' here Descriptor: false jdbc/TradeDataSource TradeDataSource
[BUILD] trunk: Failed for Revision: 988522
Geronimo Revision: 988522 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/build-0900.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 39 minutes 8 seconds [INFO] Finished at: Tue Aug 24 09:44:21 EDT 2010 [INFO] Final Memory: 473M/1012M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/logs-0900-tomcat/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.124 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.442 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/logs-0900-jetty/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.025 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/samples-0900.log Build status: OK
[BUILD] trunk: Failed for Revision: 988674
Geronimo Revision: 988674 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 44 minutes 21 seconds [INFO] Finished at: Tue Aug 24 15:49:42 EDT 2010 [INFO] Final Memory: 445M/1014M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/logs-1500-tomcat/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.46 sec FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.323 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/logs-1500-jetty/ Running TestSuite Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 11.241 sec FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/samples-1500.log Build status: OK
Re: ConfigurationUtil.getEditableConfigurationManager no longer needed?
The old codes should work, before we find a better way to replace it, or maybe when we finally turn to blueprint, I suggest to keep the EditableConfigurationManager and close the JIRA. Thanks. 2010/8/24 Rick McGuire rick...@gmail.com I've been going through the open Jiras trying to figure out what the dangling work items are left. This https://issues.apache.org/jira/browse/GERONIMO-4925 appears to be one that should have something done with it. What is the state of the EditableConfigurationManager? There still appear to be some dependencies on this in the code, but I'm not sure that code is actually functional any more. I think if this is obsolete, then we should remove the EditableCoinfigurationManager and fix the code that uses it to use its logical replacement. If it is functional, then we can close this Jira out. Rick On 10/23/2009 4:30 AM, David Jencks wrote: On Oct 22, 2009, at 10:58 PM, Ivan wrote: Thanks, David, I opened a JIRA 4925 to track it. I will temporarily enable it, so that we would not have any compile error in the plugins. After the main integration work has been done, we could have time to consider whether we still need it, or we have a better way to implement it. About generating the bundle meta data in the deployment process, I am interested that how it would be implemented in the deployer, use BND or ASM tool ? There is probably a better solution, but so far we've been ok with a simple calculation of the packages needed by the gbeans plus dynamic import package *. I wrote some code in ExecutableConfigurationUtil that collects the classes needed for the gbeans in the plan and saves the list of packages to a file, then the ArchiveCarMojo reads this and uses it to construct a manifest. Since IMO we should only be using packed plugins in 3.0 we should move all the archive functionality into the deployer somewhere, including figuring out the manifest needed. Very likely the archiveing code can just go into ExecutableConfigurationUtil. thanks david jencks 2009/10/23 David Jencks david_jen...@yahoo.com mailto: david_jen...@yahoo.com To me, this issue of getting runtime modifications of running plugins to persist or work at all is a very low priority item. I think there is a very very good chance that once much of the server is running we will step back look at what we have and decide to completely change how this works, or if we allow it. I think there are much more pressing issues such as the fact that the osgi manifest info is put into plugins by the car-maven-plugin rather than a deployer, so that the only way to build a plugin or deploy an application is through a maven build and assembling a custom server. So, I would comment out or disable any functionality that requires EditableConfigurationManager and file a jira so we don't forget about it. However, as long as this doesn't constrain the basic architecture in any way, I have no problem with anyone working on it. thanks david jencks On Oct 22, 2009, at 7:50 AM, Ivan wrote: Hi, David: Do you have more comment on it ? Currently, I think that EditableConfigurationManager is a requried function, and I am sure that something is need to improve for it, Such as, it is better that we could have an attribute to mark it as not started, because while we stop the connector in the console, after we restarting the server, the connector will start again IIRC. 2009/10/22 Ivan xhh...@gmail.com mailto:xhh...@gmail.com The ActiveMQ plugin also depends on it. Basically, since we allow the user to add new gbeans in the config.xml file for an existed configuration, we may need the API to do it programically. 2009/10/22 Rick McGuire rick...@gmail.com mailto:rick...@gmail.com David Jencks wrote: I would rather make the server work without this functionality. I'm really not sure its appropriate to modify plugins in this way. Can we catalog the places this functionality is absolutely required before we put it back in? Well, to start with, both the jetty and tomcat plugins are using it, and not just for running the tests. Rick thanks david jencks On Oct 21, 2009, at 6:06 AM, Ivan wrote: If no objection, I will try to recover those functions tomorrow, including the help methods in the ConfigurationUtil. 2009/10/21 Ivan xhh...@gmail.com mailto:xhh...@gmail.com mailto:xhh...@gmail.com mailto:xhh...@gmail.com Seems that EditableConfigurationManager support is removed
[jira] Created: (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime
Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime --- Key: GERONIMODEVTOOLS-670 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK: IBM JDK 6 Eclipse: 3.6 Reporter: Wang Guang Zhe Assignee: Delos Dai I created an web, an ejb and an ear projects using the Geronimo 2.2 as the target runtime, the geronimo deployment plans which should be in these projects don't exist. -- 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: 988774
Geronimo Revision: 988774 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 15 seconds
[INFO] Finished at: Tue Aug 24 21:43:23 EDT 2010
[INFO] Final Memory: 458M/999M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100824/logs-2100-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 for Geronimo server
[jira] Created: (GERONIMO-5551) Failing to start the server with the error Main not found
Failing to start the server with the error Main not found Key: GERONIMO-5551 URL: https://issues.apache.org/jira/browse/GERONIMO-5551 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: startup/shutdown Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK： SUN JDK 1.6.0_20 Reporter: Wang Guang Zhe Fix For: 3.0 Sometimes the Geronimo 3.0 server fails to start with the only error message Main not found. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-636) Implement JEE5 backward capability for Geronimo 2.1.x servers
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-636: -- Assignee: Delos Dai Implement JEE5 backward capability for Geronimo 2.1.x servers - Key: GERONIMODEVTOOLS-636 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Delos Dai -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-636) Implement JEE5 backward capability for Geronimo 2.x servers
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-636: --- Summary: Implement JEE5 backward capability for Geronimo 2.x servers (was: Implement JEE5 backward capability for Geronimo 2.1.x servers) Implement JEE5 backward capability for Geronimo 2.x servers --- Key: GERONIMODEVTOOLS-636 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Delos Dai -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902304#action_12902304 ] Delos Dai commented on GERONIMODEVTOOLS-670: Now,I'm working on GERONIMODEVTOOLS-636 with some code refactoring work. This problem should be resolved, once GERONIMODEVTOOLS-636 is completed. Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime --- Key: GERONIMODEVTOOLS-670 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK: IBM JDK 6 Eclipse: 3.6 Reporter: Wang Guang Zhe Assignee: Delos Dai I created an web, an ejb and an ear projects using the Geronimo 2.2 as the target runtime, the geronimo deployment plans which should be in these projects don't exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902307#action_12902307 ] Lu Jiang commented on GERONIMODEVTOOLS-670: --- Another situation is if I develop a web app and it's target run time is 3.0,then the app is not able to run on geronimo 2.2 in eclipse. Error below will occur: The server does not support version 3.0 of the J2EE Web module specification. If I export the web project as .war, then deploy it through administrator console,it can be started. Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime --- Key: GERONIMODEVTOOLS-670 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK: IBM JDK 6 Eclipse: 3.6 Reporter: Wang Guang Zhe Assignee: Delos Dai I created an web, an ejb and an ear projects using the Geronimo 2.2 as the target runtime, the geronimo deployment plans which should be in these projects don't exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
