[jira] [Created] (GERONIMODEVTOOLS-806) The gep3 could not install successfully in the customized eclipse which does not contain org.eclipse.tm.terminal.view plugin
Yi Xiao created GERONIMODEVTOOLS-806: Summary: The gep3 could not install successfully in the customized eclipse which does not contain org.eclipse.tm.terminal.view plugin Key: GERONIMODEVTOOLS-806 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-806 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-beta-1, 3.0, 3.0-beta-2 Reporter: Yi Xiao As some customized eclipse such as RAD does not contain org.eclipse.tm.terminal.view plugin, when check the dependency of the GEP, it will fail. It's better change the org.eclipse.tm.terminal.view dependency as optional, and check the existence in GEP code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-806) The GEP3 could not install successfully in the customized eclipse which does not contain org.eclipse.tm.terminal.view plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-806: - Summary: The GEP3 could not install successfully in the customized eclipse which does not contain org.eclipse.tm.terminal.view plugin (was: The gep3 could not install successfully in the customized eclipse which does not contain org.eclipse.tm.terminal.view plugin) The GEP3 could not install successfully in the customized eclipse which does not contain org.eclipse.tm.terminal.view plugin -- Key: GERONIMODEVTOOLS-806 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-806 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0, 3.0-beta-1, 3.0-beta-2 Reporter: Yi Xiao As some customized eclipse such as RAD does not contain org.eclipse.tm.terminal.view plugin, when check the dependency of the GEP, it will fail. It's better change the org.eclipse.tm.terminal.view dependency as optional, and check the existence in GEP code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-806) The GEP3 could not install successfully in the customized eclipse which does not contain org.eclipse.tm.terminal.view plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-806: - Description: As some customized eclipse such as RAD does not contain org.eclipse.tm.terminal.view plugin, when check the dependency of the GEP, it will fail. It's better change the org.eclipse.tm.terminal.view dependency as optional, and check the existence in GEP code. If not, suggest the user to install the plugin first from http://download.eclipse.org/dsdp/tm/updates/3.2. was: As some customized eclipse such as RAD does not contain org.eclipse.tm.terminal.view plugin, when check the dependency of the GEP, it will fail. It's better change the org.eclipse.tm.terminal.view dependency as optional, and check the existence in GEP code. The GEP3 could not install successfully in the customized eclipse which does not contain org.eclipse.tm.terminal.view plugin -- Key: GERONIMODEVTOOLS-806 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-806 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0, 3.0-beta-1, 3.0-beta-2 Reporter: Yi Xiao As some customized eclipse such as RAD does not contain org.eclipse.tm.terminal.view plugin, when check the dependency of the GEP, it will fail. It's better change the org.eclipse.tm.terminal.view dependency as optional, and check the existence in GEP code. If not, suggest the user to install the plugin first from http://download.eclipse.org/dsdp/tm/updates/3.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-797. -- Resolution: Fixed Fix Version/s: 3.0 Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file --- Key: GERONIMODEVTOOLS-797 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-797 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-1 Environment: OS/X, Java 6, Geronimo 2.2.1 Reporter: Johannes Weberhofer Fix For: 3.0 Attachments: openejb-jar-2.2.xsd.patch openejb-jaar-2.2.xsd is not vaild. I have fixed some of the issues, mainly import issues. Some notes: * Updated geronimo-application-1.2.xsd to geronimo-application-2.0.xsd * Replaced naming:entity-manager-factory-ref by naming:persistence-context-ref: I'm not sure if that's correct * xs:complexType name=ejb-refType is already defined in geronimo-naming-1.2.xsd - but slightly different. For the meoment I removed it from the xsd, but I don't know how the remaining values should be handled * In the complexTypes session-beanType, openejb-jarType, message-driven-beanType and entity-beanType there are violations of the Unique Particle Attribution (http://www.w3.org/TR/xmlschema-1/#cos-nonambig) in the xs:choice sections. I don't know how to handle that correctly. For the changed lines, I attach a patch which could be used as basis for further work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-797) Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13412587#comment-13412587 ] Yi Xiao commented on GERONIMODEVTOOLS-797: -- Hi Johannes, The issue has been resolved in GERONIMODEVTOOLS-799, thank you for your patch. Latest beta version does not work with Eclipse Juno because of invalid openejb-jar-2.2.xsd file --- Key: GERONIMODEVTOOLS-797 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-797 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-1 Environment: OS/X, Java 6, Geronimo 2.2.1 Reporter: Johannes Weberhofer Fix For: 3.0 Attachments: openejb-jar-2.2.xsd.patch openejb-jaar-2.2.xsd is not vaild. I have fixed some of the issues, mainly import issues. Some notes: * Updated geronimo-application-1.2.xsd to geronimo-application-2.0.xsd * Replaced naming:entity-manager-factory-ref by naming:persistence-context-ref: I'm not sure if that's correct * xs:complexType name=ejb-refType is already defined in geronimo-naming-1.2.xsd - but slightly different. For the meoment I removed it from the xsd, but I don't know how the remaining values should be handled * In the complexTypes session-beanType, openejb-jarType, message-driven-beanType and entity-beanType there are violations of the Unique Particle Attribution (http://www.w3.org/TR/xmlschema-1/#cos-nonambig) in the xs:choice sections. I don't know how to handle that correctly. For the changed lines, I attach a patch which could be used as basis for further work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-798) ClassCastException deploying EAR under eclipse 3.8 4.2 with geronimo-3
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-798. -- Resolution: Fixed ClassCastException deploying EAR under eclipse 3.8 4.2 with geronimo-3 Key: GERONIMODEVTOOLS-798 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-1 Environment: Eclipse Version: 3.8.0 (Build id: I20120608-1200) Apache Geronimo v3.0 Server Adapter Version: 3.0.0-2030113455 Eclipse Web Developer Tools Version: 3.4.0.v201203141800-7O7MFsGEMkBJz0rWbgfTLwn-4WKIocbP_pkka3Il (Build id: 20110922230524) geronimo-tomcat7-javaee6-3.0-beta-1 Reporter: Michael Seele Assignee: Yi Xiao Attachments: patch.txt Original Estimate: 10m Remaining Estimate: 10m When you try to deploy an simple EAR under eclipse 3.8 or 4.2 into geronimo 3 you got a ClassCastException. The problem is that org.apache.geronimo.st.core.DeploymentUtils set's a IProject into the model instad of a String (please see the attached Patch). If you want to try this you can use the sample project from here: https://issues.apache.org/jira/secure/attachment/12535175/eclipseProjects.tgz This is the Exception you get: java.lang.ClassCastException: org.eclipse.core.internal.resources.Project cannot be cast to java.lang.String at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getModuleParticipants(JavaEEComponentExportOperation.java:67) at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getParticipants(JavaEEComponentExportOperation.java:43) at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.createFlatComponentArchiver(JavaEEComponentExportOperation.java:91) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:191) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207) at org.apache.geronimo.st.core.DeploymentUtils.createJarFile(DeploymentUtils.java:143) at org.apache.geronimo.st.core.commands.DeployCommand.getTargetFile(DeployCommand.java:51) at org.apache.geronimo.st.core.commands.DistributeCommand.execute(DistributeCommand.java:75) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.distribute(GeronimoServerBehaviourDelegate.java:717) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:480) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:441) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:273) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955) at
[jira] [Resolved] (GERONIMODEVTOOLS-794) Support Eclipse 4.2
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-794. -- Resolution: Fixed Have verified the issue, it works well now. Support Eclipse 4.2 --- Key: GERONIMODEVTOOLS-794 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-794 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Support GEP on Eclipse 4.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-794) Support Eclipse 4.2
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-794: Assignee: Jarek Gawor Support Eclipse 4.2 --- Key: GERONIMODEVTOOLS-794 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-794 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Support GEP on Eclipse 4.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-792) Provide the GEP build the unique timestamps each time
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-792. -- Resolution: Fixed Fix Version/s: 3.0 Provide the GEP build the unique timestamps each time - Key: GERONIMODEVTOOLS-792 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Yi Xiao Assignee: Yi Xiao Labels: GEP, timestamp Fix For: 3.0 Provide the feature to let p2 updates GEP more conveniently. Using the -PbuildWithTimestamp(maven cmd parameter) to add the timestamp for build -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-790) Application started twice
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-790. -- Resolution: Fixed Fix Version/s: 3.0 Application started twice - Key: GERONIMODEVTOOLS-790 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-790 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 Say we have an application that is already deployed to the server and the server is stopped. Now, the application is modified while the server is stopped and server restarted. What happens is that when server starts up, it will start the old version of the application. And after the server is full started, Eclipse will automatically deploy the new application. That's usuallly ok but if you are dealing with large applications or applications that take some time to initialize that's very painful. So the idea here is that when such case happens only the new version of the application is deployed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-789) Improve SynchronizeProjectOnServerTask
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-789. -- Resolution: Fixed Fix Version/s: 3.0 Improve SynchronizeProjectOnServerTask -- Key: GERONIMODEVTOOLS-789 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-789 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 There are some intermittent problems with SynchronizeProjectOnServerTask that cause modules in the server view to disappear sometimes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-779) Release GEP2.1.8
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-779. -- Resolution: Fixed Fix Version/s: 2.1.8 Release GEP2.1.8 Key: GERONIMODEVTOOLS-779 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-779 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.1.8 Reporter: Yi Xiao Assignee: Yi Xiao Fix For: 2.1.8 Attachments: releaseGep218_779.patch, releaseGep218_779_1.patch, releaseGep218_changeVersion_779_1.patch, releaseNotes_779.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-778) Using GEP3.0.X's eclipse/build.xml to replace the GEP2.1.X's
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-778. -- Resolution: Fixed Using GEP3.0.X's eclipse/build.xml to replace the GEP2.1.X's Key: GERONIMODEVTOOLS-778 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-778 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.1.8 Reporter: Yi Xiao Assignee: Yi Xiao Labels: ant, build.xml Attachments: usingGep3.0AntScriptInEclipse_778.patch, usingGep3.0AntScriptInEclipse_778_1.patch The build.xml in GEP3.0.x supports the latest eclipse3.7SR1 and is more graceful than GEP2.1.x's. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-799) Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-799. -- Resolution: Fixed Fix Version/s: 3.0 Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml -- Key: GERONIMODEVTOOLS-799 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 3.0 Reporter: Yi Xiao Assignee: Yi Xiao Fix For: 3.0 When edit, add, remove the security realm in geronimo-application.xml and openejb-jar.xml, there is always the ClassCastException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-801) Release GEP3.0.0
Yi Xiao created GERONIMODEVTOOLS-801: Summary: Release GEP3.0.0 Key: GERONIMODEVTOOLS-801 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-801 Project: Geronimo-Devtools Issue Type: Task Reporter: Yi Xiao Assignee: Yi Xiao Release the GEP3.0.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-800) Release GEP3.0.0
Yi Xiao created GERONIMODEVTOOLS-800: Summary: Release GEP3.0.0 Key: GERONIMODEVTOOLS-800 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-800 Project: Geronimo-Devtools Issue Type: Task Reporter: Yi Xiao Release the GEP3.0.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (GERONIMODEVTOOLS-801) Release GEP3.0.0
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao deleted GERONIMODEVTOOLS-801: - Release GEP3.0.0 Key: GERONIMODEVTOOLS-801 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-801 Project: Geronimo-Devtools Issue Type: Task Reporter: Yi Xiao Assignee: Yi Xiao Release the GEP3.0.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-798) ClassCastException deploying EAR under eclipse 3.8 4.2 with geronimo-3
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-798: Assignee: Yi Xiao ClassCastException deploying EAR under eclipse 3.8 4.2 with geronimo-3 Key: GERONIMODEVTOOLS-798 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-1 Environment: Eclipse Version: 3.8.0 (Build id: I20120608-1200) Apache Geronimo v3.0 Server Adapter Version: 3.0.0-2030113455 Eclipse Web Developer Tools Version: 3.4.0.v201203141800-7O7MFsGEMkBJz0rWbgfTLwn-4WKIocbP_pkka3Il (Build id: 20110922230524) geronimo-tomcat7-javaee6-3.0-beta-1 Reporter: Michael Seele Assignee: Yi Xiao Attachments: patch.txt Original Estimate: 10m Remaining Estimate: 10m When you try to deploy an simple EAR under eclipse 3.8 or 4.2 into geronimo 3 you got a ClassCastException. The problem is that org.apache.geronimo.st.core.DeploymentUtils set's a IProject into the model instad of a String (please see the attached Patch). If you want to try this you can use the sample project from here: https://issues.apache.org/jira/secure/attachment/12535175/eclipseProjects.tgz This is the Exception you get: java.lang.ClassCastException: org.eclipse.core.internal.resources.Project cannot be cast to java.lang.String at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getModuleParticipants(JavaEEComponentExportOperation.java:67) at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getParticipants(JavaEEComponentExportOperation.java:43) at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.createFlatComponentArchiver(JavaEEComponentExportOperation.java:91) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:191) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207) at org.apache.geronimo.st.core.DeploymentUtils.createJarFile(DeploymentUtils.java:143) at org.apache.geronimo.st.core.commands.DeployCommand.getTargetFile(DeployCommand.java:51) at org.apache.geronimo.st.core.commands.DistributeCommand.execute(DistributeCommand.java:75) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.distribute(GeronimoServerBehaviourDelegate.java:717) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:480) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:441) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:273) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955) at
[jira] [Commented] (GERONIMODEVTOOLS-798) ClassCastException deploying EAR under eclipse 3.8 4.2 with geronimo-3
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411352#comment-13411352 ] Yi Xiao commented on GERONIMODEVTOOLS-798: -- Hi Michael, Thank you for your patch. I'm not sure if your patch will effect the previous eclipse, I will investigate the issue in these days. ClassCastException deploying EAR under eclipse 3.8 4.2 with geronimo-3 Key: GERONIMODEVTOOLS-798 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-1 Environment: Eclipse Version: 3.8.0 (Build id: I20120608-1200) Apache Geronimo v3.0 Server Adapter Version: 3.0.0-2030113455 Eclipse Web Developer Tools Version: 3.4.0.v201203141800-7O7MFsGEMkBJz0rWbgfTLwn-4WKIocbP_pkka3Il (Build id: 20110922230524) geronimo-tomcat7-javaee6-3.0-beta-1 Reporter: Michael Seele Assignee: Yi Xiao Attachments: patch.txt Original Estimate: 10m Remaining Estimate: 10m When you try to deploy an simple EAR under eclipse 3.8 or 4.2 into geronimo 3 you got a ClassCastException. The problem is that org.apache.geronimo.st.core.DeploymentUtils set's a IProject into the model instad of a String (please see the attached Patch). If you want to try this you can use the sample project from here: https://issues.apache.org/jira/secure/attachment/12535175/eclipseProjects.tgz This is the Exception you get: java.lang.ClassCastException: org.eclipse.core.internal.resources.Project cannot be cast to java.lang.String at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getModuleParticipants(JavaEEComponentExportOperation.java:67) at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getParticipants(JavaEEComponentExportOperation.java:43) at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.createFlatComponentArchiver(JavaEEComponentExportOperation.java:91) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:191) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207) at org.apache.geronimo.st.core.DeploymentUtils.createJarFile(DeploymentUtils.java:143) at org.apache.geronimo.st.core.commands.DeployCommand.getTargetFile(DeployCommand.java:51) at org.apache.geronimo.st.core.commands.DistributeCommand.execute(DistributeCommand.java:75) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.distribute(GeronimoServerBehaviourDelegate.java:717) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:480) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:441) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:273) at
[jira] [Commented] (GERONIMODEVTOOLS-798) ClassCastException deploying EAR under eclipse 3.8 4.2 with geronimo-3
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411461#comment-13411461 ] Yi Xiao commented on GERONIMODEVTOOLS-798: -- I use eclipse 4.2 to investigate the issue. In 4.2, add the new method getModuleParticipants(...) uses the J2EEComponentExportDataModelProvider.PROJECT_NAME property. We should set the J2EEComponentExportDataModelProvider.PROJECT_NAME to the String type according to all the usage method in eclipse. I also add the code into org.apache.geronimo.st.core.DeploymentUtils I committed at revision 1360166 thanks very much for Michael's patch. ClassCastException deploying EAR under eclipse 3.8 4.2 with geronimo-3 Key: GERONIMODEVTOOLS-798 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-798 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-beta-1 Environment: Eclipse Version: 3.8.0 (Build id: I20120608-1200) Apache Geronimo v3.0 Server Adapter Version: 3.0.0-2030113455 Eclipse Web Developer Tools Version: 3.4.0.v201203141800-7O7MFsGEMkBJz0rWbgfTLwn-4WKIocbP_pkka3Il (Build id: 20110922230524) geronimo-tomcat7-javaee6-3.0-beta-1 Reporter: Michael Seele Assignee: Yi Xiao Attachments: patch.txt Original Estimate: 10m Remaining Estimate: 10m When you try to deploy an simple EAR under eclipse 3.8 or 4.2 into geronimo 3 you got a ClassCastException. The problem is that org.apache.geronimo.st.core.DeploymentUtils set's a IProject into the model instad of a String (please see the attached Patch). If you want to try this you can use the sample project from here: https://issues.apache.org/jira/secure/attachment/12535175/eclipseProjects.tgz This is the Exception you get: java.lang.ClassCastException: org.eclipse.core.internal.resources.Project cannot be cast to java.lang.String at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getModuleParticipants(JavaEEComponentExportOperation.java:67) at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.getParticipants(JavaEEComponentExportOperation.java:43) at org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation.createFlatComponentArchiver(JavaEEComponentExportOperation.java:91) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:191) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207) at org.apache.geronimo.st.core.DeploymentUtils.createJarFile(DeploymentUtils.java:143) at org.apache.geronimo.st.core.commands.DeployCommand.getTargetFile(DeployCommand.java:51) at org.apache.geronimo.st.core.commands.DistributeCommand.execute(DistributeCommand.java:75) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.distribute(GeronimoServerBehaviourDelegate.java:717) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:480) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:441) at
[jira] [Created] (GERONIMODEVTOOLS-799) Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml
Yi Xiao created GERONIMODEVTOOLS-799: Summary: Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml Key: GERONIMODEVTOOLS-799 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 3.0 Reporter: Yi Xiao When edit, add, remove the security realm in geronimo-application.xml and openejb-jar.xml, there is always the ClassCastException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-799) Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13410226#comment-13410226 ] Yi Xiao commented on GERONIMODEVTOOLS-799: -- Committed at revision 1359524 and 1359587 Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml -- Key: GERONIMODEVTOOLS-799 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 3.0 Reporter: Yi Xiao When edit, add, remove the security realm in geronimo-application.xml and openejb-jar.xml, there is always the ClassCastException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-799) Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-799: Assignee: Yi Xiao Could not synchronize the security tab with source tab in geronimo-application.xml and openejb-jar.xml -- Key: GERONIMODEVTOOLS-799 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-799 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 3.0 Reporter: Yi Xiao Assignee: Yi Xiao When edit, add, remove the security realm in geronimo-application.xml and openejb-jar.xml, there is always the ClassCastException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-791) Delete module while server is stopped
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13407123#comment-13407123 ] Yi Xiao commented on GERONIMODEVTOOLS-791: -- commit in GEP At revision: 1357610 and server at revision: 1357585 Like GERONIMODEVTOOLS-790, mark the removed applications when server is stopped, and pass them to server when server is started next time, the server won't start them, and then in GEP could delete them when synchronizing with server. also, using the -Dorg.apache.geronimo.st.v30.core.manageApplicationStart=true system property to enable the feature. Delete module while server is stopped - Key: GERONIMODEVTOOLS-791 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-791 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Right now when an application is removed (i.e. undeployed) from server view in Eclipse when the server is stopped, the application is actually undeployed from the server when the server is restarted. And in the process the application is needlessly started before it is undeployed. I don't know if that's entirely possible but would be nice to actually delete the application when the server is stopped (assuming GEP is connected to a local server). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-791) Delete module while server is stopped
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-791: Assignee: Yi Xiao Delete module while server is stopped - Key: GERONIMODEVTOOLS-791 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-791 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Yi Xiao Right now when an application is removed (i.e. undeployed) from server view in Eclipse when the server is stopped, the application is actually undeployed from the server when the server is restarted. And in the process the application is needlessly started before it is undeployed. I don't know if that's entirely possible but would be nice to actually delete the application when the server is stopped (assuming GEP is connected to a local server). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6368) Could not undeploy the application using deploy in offline mode
Yi Xiao created GERONIMO-6368: - Summary: Could not undeploy the application using deploy in offline mode Key: GERONIMO-6368 URL: https://issues.apache.org/jira/browse/GERONIMO-6368 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 3.0-beta-1 Reporter: Yi Xiao When server is shutdown, using the command: deploy -o undeploy moduleId get the following exception: java.lang.IllegalArgumentException: Artifact org.apache.geronimo.configs/openejb//car is not fully resolved at org.apache.geronimo.kernel.repository.Maven2Repository.getLocation(Maven2Repository.java:37) at org.apache.geronimo.kernel.repository.AbstractRepository.contains(AbstractRepository.java:61) at org.apache.geronimo.system.configuration.DependencyManager.locateBundle(DependencyManager.java:536) at org.apache.geronimo.system.configuration.DependencyManager.installed(DependencyManager.java:454) at org.apache.geronimo.system.configuration.DependencyManager.bundleChanged(DependencyManager.java:118) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEventPrivileged(Framework.java:1523) at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Framework.java:1459) at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:898) at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:833) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:137) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:131) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:309) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:290) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:125) at org.apache.geronimo.deployment.plugin.local.UndeployCommand.run(UndeployCommand.java:58) at java.lang.Thread.run(Unknown Source) Deployer operation failed: load of default/TestWEB0/1.0/war failed org.apache.geronimo.kernel.config.LifecycleException: load of default/TestWEB0/1.0/war failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:316) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:290) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:125) at org.apache.geronimo.deployment.plugin.local.UndeployCommand.run(UndeployCommand.java:58) at java.lang.Thread.run(Unknown Source) Caused by: org.osgi.framework.BundleException: The bundle default.TestWEB0_1.0.0 [292] could not be resolved. Reason: Missing Constraint: Import-Package: onimo.yoko; version=[0.0.0,0.0.0] at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:311) ... 4 more 2012-07-03 19:20:39,887 ERROR [DeployTool] Error: org.apache.geronimo.common.DeploymentException: Operation failed: load of default/TestWEB0/1.0/war failed org.apache.geronimo.kernel.config.LifecycleException: load of default/TestWEB0/1.0/war failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:316) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:290) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:125) at org.apache.geronimo.deployment.plugin.local.UndeployCommand.run(UndeployCommand.java:58) at java.lang.Thread.run(Unknown Source) Caused by: org.osgi.framework.BundleException: The bundle
[jira] [Updated] (GERONIMODEVTOOLS-792) Provide the GEP build the unique timestamps each time
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-792: - Description: Provide the feature to let p2 updates GEP more conveniently. Using the -PbuildWithTimestamp(maven cmd parameter) to add the timestamp for build was:Provide the feature to let p2 updates GEP more conveniently. Provide the GEP build the unique timestamps each time - Key: GERONIMODEVTOOLS-792 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Yi Xiao Assignee: Yi Xiao Labels: GEP, timestamp Provide the feature to let p2 updates GEP more conveniently. Using the -PbuildWithTimestamp(maven cmd parameter) to add the timestamp for build -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-792) Provide the GEP build the unique timestamps each time
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-792: Assignee: Yi Xiao Provide the GEP build the unique timestamps each time - Key: GERONIMODEVTOOLS-792 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Yi Xiao Assignee: Yi Xiao Labels: GEP, timestamp Provide the feature to let p2 updates GEP more conveniently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-792) Provide the GEP build the unique timestamps each time
Yi Xiao created GERONIMODEVTOOLS-792: Summary: Provide the GEP build the unique timestamps each time Key: GERONIMODEVTOOLS-792 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-792 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Yi Xiao Provide the feature to let p2 updates GEP more conveniently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-762: - Attachment: gep_nightly_build0.patch Fix the site info of nightly builds GEP needs a nightly builds repositary - Key: GERONIMODEVTOOLS-762 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Assignee: Yi Xiao Labels: build, gep,, nightly Attachments: gep_nightly_build.patch, gep_nightly_build0.patch The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: server idgeronimo-devtools-nightly-repo/id usernamepeople.apache.org.username/username passwordpeople.apache.org.password/password /server Thank Janet for helping me test to upload the devtools onto the apache site. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-762: - Attachment: (was: gep_nightly_build0.patch) GEP needs a nightly builds repositary - Key: GERONIMODEVTOOLS-762 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Assignee: Yi Xiao Labels: build, gep,, nightly Attachments: gep_nightly_build_new.patch The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: server idgeronimo-devtools-nightly-repo/id usernamepeople.apache.org.username/username passwordpeople.apache.org.password/password /server Thank Janet for helping me test to upload the devtools onto the apache site. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-762: - Attachment: (was: gep_nightly_build.patch) GEP needs a nightly builds repositary - Key: GERONIMODEVTOOLS-762 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Assignee: Yi Xiao Labels: build, gep,, nightly Attachments: gep_nightly_build_new.patch The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: server idgeronimo-devtools-nightly-repo/id usernamepeople.apache.org.username/username passwordpeople.apache.org.password/password /server Thank Janet for helping me test to upload the devtools onto the apache site. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-762: - Comment: was deleted (was: Fix the site info of nightly builds) GEP needs a nightly builds repositary - Key: GERONIMODEVTOOLS-762 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Assignee: Yi Xiao Labels: build, gep,, nightly Attachments: gep_nightly_build_new.patch The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: server idgeronimo-devtools-nightly-repo/id usernamepeople.apache.org.username/username passwordpeople.apache.org.password/password /server Thank Janet for helping me test to upload the devtools onto the apache site. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-767) When open EAR's geronimo-application.xml in GEP3.0 and the EAR are bind to Geronimo2.X, an exception will happen
When open EAR's geronimo-application.xml in GEP3.0 and the EAR are bind to Geronimo2.X, an exception will happen Key: GERONIMODEVTOOLS-767 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-767 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: Win7 64bit, Eclipse3.6SR2, Oracle-jdk-1.6.25 Reporter: Yi Xiao Assignee: Yi Xiao org.apache.geronimo.st.v21.core: CoreException: GeronimoServerInfo.loadExtensionPoints() org.eclipse.core.runtime.CoreException: Plug-in org.apache.geronimo.st.v21.core was unable to instantiate class org.apache.geronimo.st.v21.core.GeronimoV21ServerInfo. at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:904) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) at org.apache.geronimo.st.v21.core.GeronimoServerInfoManager.loadExtensionPoints(GeronimoServerInfoManager.java:50) at org.apache.geronimo.st.v21.core.GeronimoServerInfoManager.clinit(GeronimoServerInfoManager.java:36) at org.apache.geronimo.st.v21.ui.editors.GeronimoFormContentLoader.triggerGeronimoServerInfoUpdate(GeronimoFormContentLoader.java:136) at org.apache.geronimo.st.ui.editors.AbstractGeronimoFormContentLoader.doAddPages(AbstractGeronimoFormContentLoader.java:50) at org.apache.geronimo.st.ui.editors.SharedDeploymentPlanEditor.doAddPages(SharedDeploymentPlanEditor.java:66) at org.apache.geronimo.st.ui.editors.AbstractGeronimoJAXBBasedEditor.addPages(AbstractGeronimoJAXBBasedEditor.java:121) at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1254) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1207) at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1606) at org.eclipse.ui.internal.PartStack.add(PartStack.java:497) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103) at org.eclipse.ui.internal.PartStack.add(PartStack.java:483) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112) at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225) at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213) at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:778) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:677) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2860) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691) at
[jira] [Commented] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13113119#comment-13113119 ] Yi Xiao commented on GERONIMODEVTOOLS-706: -- Hi Hong fang, the rev #1173019 misses an file: plugins/org.apache.geronimo.st.v30.ui/src/main/java/org/apache/geronimo/st/v30/ui/view/KarafShellSSHTerminalView.java, pls append it, thx~ I try to use the trunk code to build and find the problem. Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby Attachments: enableKarafShell_706.patch, enableKarafShell_706_m0.patch, enableKarafShell_706_m1.patch, karafSSHTerminal.jpg, karafSSHTerminal_improvement.jpg (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
[ https://issues.apache.org/jira/browse/GERONIMO-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5432: -- Attachment: EncryptPasswordInServerXML_5432_optimize3.patch Sorry, Shawn, I will notice it next time. The EncryptPasswordInServerXML_5432_optimize3.patch is the latest one. Encrypt password values in server.xml for geronimo 2.2 onwards -- Key: GERONIMO-5432 URL: https://issues.apache.org/jira/browse/GERONIMO-5432 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: EncryptPasswordInServerXMLFor2.2.2_5432.patch, EncryptPasswordInServerXML_5432.patch, EncryptPasswordInServerXML_5432_optimize2.patch, EncryptPasswordInServerXML_5432_optimize3.patch, EncryptPasswordInServerXML_5432_optmize.patch Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5709) Track: Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
[ https://issues.apache.org/jira/browse/GERONIMO-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13105141#comment-13105141 ] Yi Xiao commented on GERONIMO-5709: --- The ArrayListString scannedJars isn't existed and the relative methods are also removed in GeronimoTldLocationCache.java, so the thread safety is unnecessary now. Suggest to close it. Track: Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache - Key: GERONIMO-5709 URL: https://issues.apache.org/jira/browse/GERONIMO-5709 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Track for GERONIMO-5683 in 2.2 and 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-706: - Attachment: karafSSHTerminal_improvement.jpg enableKarafShell_706_m1.patch The newest patch is enableKarafShell_706_m1.patch, the karafSSHTerminal_improvement.jpg show the result. Now, the user can use SSH terminal to connect different server. Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby Attachments: enableKarafShell_706.patch, enableKarafShell_706_m0.patch, enableKarafShell_706_m1.patch, karafSSHTerminal.jpg, karafSSHTerminal_improvement.jpg (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-764: - Attachment: controlBundleStartLevel_764_2.patch add a new patch: controlBundleStartLevel_764_2.patch. when the server shutdown, could not change the bundle start level, because GEP communicates with server when change it. Control the OSGI bundle's start level in GEP Key: GERONIMODEVTOOLS-764 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Yi Xiao Labels: OSGI, startLevel Fix For: 3.0 Attachments: controlBundleStartLevel_764.patch, controlBundleStartLevel_764_1.patch, controlBundleStartLevel_764_2.patch, defaultStartLevel.jpg, singleStartLevel.jpg 1 Provide a UI interface to control all the bundles' start level 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5709) Track: Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache
[ https://issues.apache.org/jira/browse/GERONIMO-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5709: -- Attachment: threadSafetyGeronimoTldLocationCacheFor2.2.patch The geronimo2.2 needs threadSafetyGeronimoTldLocationCacheFor2.2.patch Track: Thread safety for needScanJar(), scanJar(), and scannedJars.add() in GeronimoTldLocationsCache - Key: GERONIMO-5709 URL: https://issues.apache.org/jira/browse/GERONIMO-5709 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: threadSafetyGeronimoTldLocationCacheFor2.2.patch Track for GERONIMO-5683 in 2.2 and 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5704) Track: Farming module provision of utilizing encrypted password instead of plain text
[ https://issues.apache.org/jira/browse/GERONIMO-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5704: -- Attachment: armingModuleEncryptedPasswordFor2.2.2_5704.patch The armingModuleEncryptedPasswordFor2.2.2_5704.patch fits to 2.2.2 Track: Farming module provision of utilizing encrypted password instead of plain text - Key: GERONIMO-5704 URL: https://issues.apache.org/jira/browse/GERONIMO-5704 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: armingModuleEncryptedPasswordFor2.2.2_5704.patch, farmingModuleEncryptedPassword_5704.patch Track for GERONIMO-5691 for 2,2 and 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
[ https://issues.apache.org/jira/browse/GERONIMO-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5432: -- Attachment: EncryptPasswordInServerXMLFor2.2.2_5432.patch EncryptPasswordInServerXML_5432_optimize2.patch The EncryptPasswordInServerXML_5432_optimize2.patch is for 3.0, it removes some redundant codes; EncryptPasswordInServerXMLFor2.2.2_5432.patch is for 2.2.2 Encrypt password values in server.xml for geronimo 2.2 onwards -- Key: GERONIMO-5432 URL: https://issues.apache.org/jira/browse/GERONIMO-5432 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: EncryptPasswordInServerXMLFor2.2.2_5432.patch, EncryptPasswordInServerXML_5432.patch, EncryptPasswordInServerXML_5432_optimize2.patch, EncryptPasswordInServerXML_5432_optmize.patch Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
[ https://issues.apache.org/jira/browse/GERONIMO-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5432: -- Attachment: EncryptPasswordInServerXML_5432.patch The patch encrypts the SSH connector's keystorePass attribute in server.xml. keystorePass attribute is encrypted when server startups every time. Encrypt password values in server.xml for geronimo 2.2 onwards -- Key: GERONIMO-5432 URL: https://issues.apache.org/jira/browse/GERONIMO-5432 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: EncryptPasswordInServerXML_5432.patch Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5704) Track: Farming module provision of utilizing encrypted password instead of plain text
[ https://issues.apache.org/jira/browse/GERONIMO-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5704: -- Attachment: farmingModuleEncryptedPassword_5704.patch The patch is available. Track: Farming module provision of utilizing encrypted password instead of plain text - Key: GERONIMO-5704 URL: https://issues.apache.org/jira/browse/GERONIMO-5704 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: farmingModuleEncryptedPassword_5704.patch Track for GERONIMO-5691 for 2,2 and 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
[ https://issues.apache.org/jira/browse/GERONIMO-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13105049#comment-13105049 ] Yi Xiao commented on GERONIMO-5432: --- It's good idea! Encrypt password values in server.xml for geronimo 2.2 onwards -- Key: GERONIMO-5432 URL: https://issues.apache.org/jira/browse/GERONIMO-5432 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: EncryptPasswordInServerXML_5432.patch Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5432) Encrypt password values in server.xml for geronimo 2.2 onwards
[ https://issues.apache.org/jira/browse/GERONIMO-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5432: -- Attachment: EncryptPasswordInServerXML_5432_optmize.patch Optimize the process. Encrypt password values in server.xml for geronimo 2.2 onwards -- Key: GERONIMO-5432 URL: https://issues.apache.org/jira/browse/GERONIMO-5432 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2 Environment: geronimo tomcat assembly Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: EncryptPasswordInServerXML_5432.patch, EncryptPasswordInServerXML_5432_optmize.patch Password fields in plain text in server.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5705) Track: Encryption logic for connectionPassword attribute in ldap realm
[ https://issues.apache.org/jira/browse/GERONIMO-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5705: -- Attachment: EncryptionOfConnectionPassword_5705.patch have test it in the steps below: 1 Go to web console-Security Realms, create a ldap security realm(can use local apache ldap) 2 Edit the realm's connectionPassword 3 Check the connectionPassword in var/config.xml's realm configuration has been encrypted Track: Encryption logic for connectionPassword attribute in ldap realm -- Key: GERONIMO-5705 URL: https://issues.apache.org/jira/browse/GERONIMO-5705 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: EncryptionOfConnectionPassword_5705.patch Track for GERONIMO-5693 for 2.2 and 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5708) Track: Unlock keystore command line utility does not work with Configured Encryption
[ https://issues.apache.org/jira/browse/GERONIMO-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5708: -- Attachment: unlockKeystoreCli_5708.patch The error info is: org.apache.geronimo.common.DeploymentException: java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.management.geronimo.KeystoreException (no security manager: RMI class loader disabled) at org.apache.geronimo.deployment.cli.CommandUnlockKeystore.unLockKeyStore(CommandUnlockKeystore.java:189) at org.apache.geronimo.deployment.cli.CommandUnlockKeystore.execute(CommandUnlockKeystore.java:74) at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:171) at org.apache.geronimo.system.main.MainBridge.execute(MainBridge.java:64) at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65) at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:32) Caused by: java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: org.apache.geronimo.management.geronimo.KeystoreException (no security manager: RMI class loader disabled) at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(Unknown Source) at org.apache.geronimo.system.jmx.KernelDelegate.invokeKernel(KernelDelegate.java:898) at org.apache.geronimo.system.jmx.KernelDelegate.invoke(KernelDelegate.java:555) at org.apache.geronimo.deployment.cli.CommandUnlockKeystore.unLockKeyStore(CommandUnlockKeystore.java:183) ... 6 more Caused by: java.lang.ClassNotFoundException: org.apache.geronimo.management.geronimo.KeystoreException (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadClass(Unknown Source) at sun.rmi.server.LoaderHandler.loadClass(Unknown Source) at java.rmi.server.RMIClassLoader$2.loadClass(Unknown Source) at org.apache.geronimo.kernel.rmi.RMIClassLoaderSpiImpl.loadClass(RMIClassLoaderSpiImpl.java:53) at java.rmi.server.RMIClassLoader.loadClass(Unknown Source) at sun.rmi.server.MarshalInputStream.resolveClass(Unknown Source) at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source) at java.io.ObjectInputStream.readClassDesc(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) ... 14 more The patch is similar as GERONIMO-5692's. Track: Unlock keystore command line utility does not work with Configured Encryption - Key: GERONIMO-5708 URL: https://issues.apache.org/jira/browse/GERONIMO-5708 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2.2, 3.0 Attachments: unlockKeystoreCli_5708.patch Track for GERONIMO-5692 for 2.2 and 3.0. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-759: - Attachment: OSGIBundleDeploy_759_noIDPersist.patch the patch not persist the bundle id in GEP side Using the new APIs to manage the bundles status both in GEP and Server side Key: GERONIMODEVTOOLS-759 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Jarek Gawor Labels: OSGI, bundle Fix For: 3.0 Attachments: OSGIBundleDeploy.patch, OSGIBundleDeploy_759_noIDPersist.patch, OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch, OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch This improvement depends on the server's modules, so, if the server side does not update timely, it may cause the GEP compile failure! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13093352#comment-13093352 ] Yi Xiao commented on GERONIMODEVTOOLS-706: -- Thank you for your comments, Jarek. 1) Yes, now I just limit to one active terminal, if user switch to connect to another server, must stop current one. 2) Yes, only support local machine now, I can add a field in server page to connect to remote server. 3) em, it's a good idea. 4) The methods will be used on modifying and saving server page configurations(not done yet), Should be removed in the patch, sorry~ Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby Attachments: enableKarafShell_706.patch, enableKarafShell_706_m0.patch, karafSSHTerminal.jpg (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-766) Add the server listener to do some actions before or after server start and stop
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092588#comment-13092588 ] Yi Xiao commented on GERONIMODEVTOOLS-766: -- It's great, I will try it! Thx, Jarek. Add the server listener to do some actions before or after server start and stop Key: GERONIMODEVTOOLS-766 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Attachments: serverListener.patch I notice that the WST does not provide a convenient way to listen to the server's start and stop status. so first, I implement a register which can register, unregister the listeners; second, dispatch the before server start, after server start, before server stop and after server stop events when server start stop. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMODEVTOOLS-766) Add the server listener to do some actions before or after server start and stop
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao closed GERONIMODEVTOOLS-766. Resolution: Not A Problem Add the server listener to do some actions before or after server start and stop Key: GERONIMODEVTOOLS-766 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Attachments: serverListener.patch I notice that the WST does not provide a convenient way to listen to the server's start and stop status. so first, I implement a register which can register, unregister the listeners; second, dispatch the before server start, after server start, before server stop and after server stop events when server start stop. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-766) Add the server listener to do some actions before or after server start and stop
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13092599#comment-13092599 ] Yi Xiao commented on GERONIMODEVTOOLS-766: -- Hi, Jarek. It works, so I close it. Add the server listener to do some actions before or after server start and stop Key: GERONIMODEVTOOLS-766 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Attachments: serverListener.patch I notice that the WST does not provide a convenient way to listen to the server's start and stop status. so first, I implement a register which can register, unregister the listeners; second, dispatch the before server start, after server start, before server stop and after server stop events when server start stop. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-706: - Attachment: enableKarafShell_706_m0.patch The latest patch is enableKarafShell_706_m0.patch. Use the WST's listeners to replace the GEP's. Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby Attachments: enableKarafShell_706.patch, enableKarafShell_706_m0.patch, karafSSHTerminal.jpg (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-766) Add the server listener to do some actions before or after server start and stop
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-766: - Attachment: serverListener.patch Add the server listener to do some actions before or after server start and stop Key: GERONIMODEVTOOLS-766 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Attachments: serverListener.patch I notice that the WST does not provide a convenient way to listen to the server's start and stop status. so first, I implement a register which can register, unregister the listeners; second, dispatch the before server start, after server start, before server stop and after server stop events when server start stop. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-766) Add the server listener to do some actions before or after server start and stop
Add the server listener to do some actions before or after server start and stop Key: GERONIMODEVTOOLS-766 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-766 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Attachments: serverListener.patch I notice that the WST does not provide a convenient way to listen to the server's start and stop status. so first, I implement a register which can register, unregister the listeners; second, dispatch the before server start, after server start, before server stop and after server stop events when server start stop. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-706: - Attachment: karafSSHTerminal.jpg enableKarafShell_706.patch As the tab key could not work successfully in the eclipse's default console, I decide to use ssh terminal to support the remote karaf shell in eclipse. attach a pic to show the how it works now. Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby Attachments: enableKarafShell_706.patch, karafSSHTerminal.jpg (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090668#comment-13090668 ] Yi Xiao commented on GERONIMODEVTOOLS-759: -- I know you mean, Jarek. In my patch:OSGIBundleDeploy_759_persistence.patch, I modify the SynchronizeProjectOnServerTask, and when synchronizing with server, the bundle id will be updated, so I persist it. I still think save bundle id can save lots of time compare to look up bundle id every time from server, the SynchronizeProjectOnServerTask can guarantee the bundle id's correction, so I think just need to do a little modification in it we can use bundle id correctly. Using the new APIs to manage the bundles status both in GEP and Server side Key: GERONIMODEVTOOLS-759 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Jarek Gawor Labels: OSGI, bundle Fix For: 3.0 Attachments: OSGIBundleDeploy.patch, OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch, OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch This improvement depends on the server's modules, so, if the server side does not update timely, it may cause the GEP compile failure! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090733#comment-13090733 ] Yi Xiao commented on GERONIMODEVTOOLS-759: -- I find some other cases will lead to publish errors, I will consider it more carefully and provide a new patch. Using the new APIs to manage the bundles status both in GEP and Server side Key: GERONIMODEVTOOLS-759 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Jarek Gawor Labels: OSGI, bundle Fix For: 3.0 Attachments: OSGIBundleDeploy.patch, OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch, OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch This improvement depends on the server's modules, so, if the server side does not update timely, it may cause the GEP compile failure! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6120) Could not connect to karaf shell by SSH
Could not connect to karaf shell by SSH --- Key: GERONIMO-6120 URL: https://issues.apache.org/jira/browse/GERONIMO-6120 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 3.0 Environment: Win7-64bit, Oracle jdk 1.6.0_25 Reporter: Yi Xiao When use a SSH terminal to connect the geronimo, it always Authentication failure; The 8101 port has been listening; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086938#comment-13086938 ] Yi Xiao commented on GERONIMODEVTOOLS-706: -- The double prompt issue has been fixed due to Jarek's contribution to karaf. Now, the GEP uses -Djline.terminal=jline.UnsupportedTerminal, and the UnsupportedTermial use a different command parsing process compared with KarafWindowsTermial. The TAB function could not be used under the UnsupportedTerminal, so if we want to use the TAB, we should eliminate the -Djline.terminal=jline.UnsupportedTerminal, and try to enable the eclipse's console can read each character instead of a line. The eclipse's console intercept the stdin, stdout and stderr, so the Jline's readCharacter(in) could not work successfully. Maybe, we could start a separated console terminal from eclipse, any thoughts? Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5939) Support OBR resolution during bundle install
[ https://issues.apache.org/jira/browse/GERONIMO-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5939: -- Attachment: GERONIMO_5939_core_modify2.patch The newest patch is GERONIMO_5939_core_modify2.patch Support OBR resolution during bundle install Key: GERONIMO-5939 URL: https://issues.apache.org/jira/browse/GERONIMO-5939 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0-M1 Reporter: Jarek Gawor Assignee: Rex Wang Attachments: GERONIMO-5939-core.patch, GERONIMO_5939_core_modify.patch, GERONIMO_5939_core_modify2.patch, GeronimoOBR_5939.patch When installing an individual bundle (via the admin console, command line or shell) provide an option to perform OBR resolution to install the dependent bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6108) Some labels could not display correctly in admin console's DBWizard page
[ https://issues.apache.org/jira/browse/GERONIMO-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082159#comment-13082159 ] Yi Xiao commented on GERONIMO-6108: --- The cause is the fmt:message tag could not get the key correctly. I notice the tag key is generated dynamically by the info of tanql-connector type, however, some adapter types were commented. Now, I just cancel the comments, then display correctly! I'm really confused why the the adapters are commented, as the adapters are still existed in server, any comments? Some labels could not display correctly in admin console's DBWizard page Key: GERONIMO-6108 URL: https://issues.apache.org/jira/browse/GERONIMO-6108 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: win7-64bit, oracle jdk1.6_25; winxp-x86, IBM jdk sr9-fp1 Reporter: Yi Xiao Labels: DBWizard, console -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6108) Some labels could not display correctly in admin console's DBWizard page
[ https://issues.apache.org/jira/browse/GERONIMO-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-6108: -- Attachment: showDbWizardInfoCorrectly_6108.patch errorInfos.jpg Some labels could not display correctly in admin console's DBWizard page Key: GERONIMO-6108 URL: https://issues.apache.org/jira/browse/GERONIMO-6108 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: win7-64bit, oracle jdk1.6_25; winxp-x86, IBM jdk sr9-fp1 Reporter: Yi Xiao Labels: DBWizard, console Attachments: errorInfos.jpg, showDbWizardInfoCorrectly_6108.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5939) Support OBR resolution during bundle install
[ https://issues.apache.org/jira/browse/GERONIMO-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5939: -- Attachment: GERONIMO_5939_core_modify.patch Hi Rex, I've test your patch, it works fine! I make a little modification, you could review it. Support OBR resolution during bundle install Key: GERONIMO-5939 URL: https://issues.apache.org/jira/browse/GERONIMO-5939 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0-M1 Reporter: Jarek Gawor Assignee: Rex Wang Attachments: GERONIMO-5939-core.patch, GERONIMO_5939_core_modify.patch, GeronimoOBR_5939.patch When installing an individual bundle (via the admin console, command line or shell) provide an option to perform OBR resolution to install the dependent bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5939) Support OBR resolution during bundle install
[ https://issues.apache.org/jira/browse/GERONIMO-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082079#comment-13082079 ] Yi Xiao commented on GERONIMO-5939: --- Ok, thanks for your reminder~ I will test it ASAP! Support OBR resolution during bundle install Key: GERONIMO-5939 URL: https://issues.apache.org/jira/browse/GERONIMO-5939 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0-M1 Reporter: Jarek Gawor Assignee: Rex Wang Attachments: GERONIMO-5939-core.patch, GeronimoOBR_5939.patch When installing an individual bundle (via the admin console, command line or shell) provide an option to perform OBR resolution to install the dependent bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6108) Some labels could not display correctly in admin console's DBWizard page
Some labels could not display correctly in admin console's DBWizard page Key: GERONIMO-6108 URL: https://issues.apache.org/jira/browse/GERONIMO-6108 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Environment: win7-64bit, oracle jdk1.6_25; winxp-x86, IBM jdk sr9-fp1 Reporter: Yi Xiao -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-735) More user friendly message when deploying OSGi application
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-735: - Attachment: moreFriendlyMessage_735.patch Now, if the EBA could not deploy to the server, the unsatisfactory bundle infos will be report to the user. More user friendly message when deploying OSGi application -- Key: GERONIMODEVTOOLS-735 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-735 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0_M1 Reporter: Han Hong Fang Fix For: 3.0-M2, 3.0 Attachments: moreFriendlyMessage_735.patch, screenshot-1.jpg When OSGi application project doesn't contain OSGi bundle, or specified contained bundle can not be resolved at deployment time, more user friendly message which clearly points out the problem would be more nice that throw the DeploymentException. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-759: - Attachment: OSGIBundleDeploy_759_persistence.patch Using the new APIs to manage the bundles status both in GEP and Server side Key: GERONIMODEVTOOLS-759 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Jarek Gawor Labels: OSGI, bundle Fix For: 3.0 Attachments: OSGIBundleDeploy.patch, OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch, OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch This improvement depends on the server's modules, so, if the server side does not update timely, it may cause the GEP compile failure! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079890#comment-13079890 ] Yi Xiao commented on GERONIMODEVTOOLS-759: -- The newest path is OSGIBundleDeploy_759_persistence.patch. I reconstruct the code, add some classes in charge of the artifacts and bundles's persistence; And, use the writeObject method to persist the object to a file instead of using a XML file, the efficiency is higher. Although the object file is difficult to understand and unmodified compared to XML file, I think the persistence file is no need to modify manually. Using the new APIs to manage the bundles status both in GEP and Server side Key: GERONIMODEVTOOLS-759 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Jarek Gawor Labels: OSGI, bundle Fix For: 3.0 Attachments: OSGIBundleDeploy.patch, OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch, OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch This improvement depends on the server's modules, so, if the server side does not update timely, it may cause the GEP compile failure! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-764: - Attachment: controlBundleStartLevel_764_1.patch Control the OSGI bundle's start level in GEP Key: GERONIMODEVTOOLS-764 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Yi Xiao Labels: OSGI, startLevel Fix For: 3.0 Attachments: controlBundleStartLevel_764.patch, controlBundleStartLevel_764_1.patch, defaultStartLevel.jpg, singleStartLevel.jpg 1 Provide a UI interface to control all the bundles' start level 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079893#comment-13079893 ] Yi Xiao commented on GERONIMODEVTOOLS-764: -- The newest patch is controlBundleStartLevel_764_1.patch, it depends on the patch of GERONIMODEVTOOLS-759 Now, the default start level is separated from the server, when the eclipse is shutting down, the value persists to a local file automatically and retrieves when eclipse starts up. Control the OSGI bundle's start level in GEP Key: GERONIMODEVTOOLS-764 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Yi Xiao Labels: OSGI, startLevel Fix For: 3.0 Attachments: controlBundleStartLevel_764.patch, controlBundleStartLevel_764_1.patch, defaultStartLevel.jpg, singleStartLevel.jpg 1 Provide a UI interface to control all the bundles' start level 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-744) More flexible no-redeployment option
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13076081#comment-13076081 ] Yi Xiao commented on GERONIMODEVTOOLS-744: -- Hi Jarek, how to set the docBase attribute in an web application? I've create a myApp/META-INF/context.xml file which contains a 'Context docBase=.../Context' element. But, it does not work. More flexible no-redeployment option Key: GERONIMODEVTOOLS-744 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-744 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 It would be nice to let user specify a list of file extensions that do not cause the application to be re-deployed if one of the files with a matching extension is modified. Instead the given file would be simply copied and the application left running as is. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-744) More flexible no-redeployment option
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13076103#comment-13076103 ] Yi Xiao commented on GERONIMODEVTOOLS-744: -- I try to add the 'web:context docBase=/TestWeb/web:context' in geronimo-web.xml, the 'docBase' attribute has been transferred to server, but the server ignores it, so it does not work. Should we need to still retain the feature in 3.0? More flexible no-redeployment option Key: GERONIMODEVTOOLS-744 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-744 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0 It would be nice to let user specify a list of file extensions that do not cause the application to be re-deployed if one of the files with a matching extension is modified. Instead the given file would be simply copied and the application left running as is. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5939) Support OBR resolution during bundle install
[ https://issues.apache.org/jira/browse/GERONIMO-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5939: -- Attachment: GeronimoOBR_5939.patch Support OBR resolution during bundle install Key: GERONIMO-5939 URL: https://issues.apache.org/jira/browse/GERONIMO-5939 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0-M1 Reporter: Jarek Gawor Attachments: GeronimoOBR_5939.patch When installing an individual bundle (via the admin console, command line or shell) provide an option to perform OBR resolution to install the dependent bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5939) Support OBR resolution during bundle install
[ https://issues.apache.org/jira/browse/GERONIMO-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13073483#comment-13073483 ] Yi Xiao commented on GERONIMO-5939: --- According to the senario above, provide Three karaf shell commands: 1 obr:geronimo-addUrl 'URL of the repo file' 2 obr:geronimo-install 'symbolicName,version' 3 obr:geronimo-uninstall 'symbolicName,version' The geronimo-install command also can take optional parameters to indicate whether to start the bundle and assign the bundle's start level. The geronimo-uninstall command matches the install one, if you want to reinstall the obr bundles by no restart server, you should use geronimo-uninstall instead of osgi:uninstall Support OBR resolution during bundle install Key: GERONIMO-5939 URL: https://issues.apache.org/jira/browse/GERONIMO-5939 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0-M1 Reporter: Jarek Gawor Attachments: GeronimoOBR_5939.patch When installing an individual bundle (via the admin console, command line or shell) provide an option to perform OBR resolution to install the dependent bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6059) New look and feel of Geronimo 3.0 admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13073412#comment-13073412 ] Yi Xiao commented on GERONIMO-6059: --- The loading status is cool! Now, the console UI looks like a web2.0's application more and more. New look and feel of Geronimo 3.0 admin console --- Key: GERONIMO-6059 URL: https://issues.apache.org/jira/browse/GERONIMO-6059 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 Attachments: Geronimo-3.0-New-UI-Proposal-advanced-navigator.png, Geronimo-3.0-New-UI-Proposal-basic-navigator.png, Step-1-detail-improvements.PNG, Step-1-login-page.PNG, Step-1-welcome-page.PNG, old-cosole-full-opened-navigation-tree.png Geronimo 3.0 is milestone release that contains a lot of new features. So I think it's time to change the UI design of admin console to provide user a brand new look and feel. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6076) Graphics cannot be displayed on monitoring porlet
[ https://issues.apache.org/jira/browse/GERONIMO-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13071798#comment-13071798 ] Yi Xiao commented on GERONIMO-6076: --- I see the patch deletes the 'float: left' css style in every *container element, and replace the *Head element's div children with span, I really can not figure out why the change works~ Graphics cannot be displayed on monitoring porlet - Key: GERONIMO-6076 URL: https://issues.apache.org/jira/browse/GERONIMO-6076 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Shenghao Fang Assignee: Shenghao Fang Attachments: GERONIMO-6076.patch, ShowDojoCharting_6076.patch Graphics cannot be displayed on monitoring porlet. This is a regression by GERONIMO-5674. Monitoring portlet requires chart related dojo library which was removed by GERONIMO-5674. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5939) Support OBR resolution during bundle install
[ https://issues.apache.org/jira/browse/GERONIMO-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070359#comment-13070359 ] Yi Xiao commented on GERONIMO-5939: --- I notice that the geronimo3.0 already has the function of installing a bundle with its dependencies through karaf shell: obr:deploy 'bundle-identifier'. The defect is karaf does not persist the bundle and its dependencies into geronimo's local repository. So, I design a senario: 1 The user use a command(not exist yet), geronimo: obr-deploy 'bundle-identifier' to deploy a bundle which has the desc infos in obr.xml(include the referring repositories). 2 The obr-deploy command will resolve the bundle by obr's resolve API of Felix. 3 If the dependencies are satisfied, will download the bundles from remote sites and use the geronimo install bundle API to deploy the bundle into local repository and write the info into 'etc/startup.properties', otherwise, will just log the fail message into log. Support OBR resolution during bundle install Key: GERONIMO-5939 URL: https://issues.apache.org/jira/browse/GERONIMO-5939 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0-M1 Reporter: Jarek Gawor When installing an individual bundle (via the admin console, command line or shell) provide an option to perform OBR resolution to install the dependent bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5939) Support OBR resolution during bundle install
[ https://issues.apache.org/jira/browse/GERONIMO-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068797#comment-13068797 ] Yi Xiao commented on GERONIMO-5939: --- According to the spec of OSGI rfc-0112, the geronimo-obr does not support all the obr's functions, such as no repository admin to communicate with other repositories, no resolver to deploy a new bundle into local repository. So I think it need to reconstruct the code, and add the functions mentioned above. Support OBR resolution during bundle install Key: GERONIMO-5939 URL: https://issues.apache.org/jira/browse/GERONIMO-5939 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: deployment, osgi Affects Versions: 3.0-M1 Reporter: Jarek Gawor When installing an individual bundle (via the admin console, command line or shell) provide an option to perform OBR resolution to install the dependent bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-632) Implement usage scenarios where target runtime is or isn't a Web Profile type server configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068132#comment-13068132 ] Yi Xiao commented on GERONIMODEVTOOLS-632: -- The issue is contained in GERONIMODEVTOOLS-627. Implement usage scenarios where target runtime is or isn't a Web Profile type server configuration Key: GERONIMODEVTOOLS-632 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-632 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 i.e., only WAR-type artifacts should be deployed on a Web Profile server -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-618) Enhance introspection on Geronimo server for discovery of already-deployed OSGi bundles and dependencies amongst other bundles
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068138#comment-13068138 ] Yi Xiao commented on GERONIMODEVTOOLS-618: -- In the GEP side, we have already enable karaf shell in eclipse console to do the operation like listing, installing bundles to server side, so, I think it does not need do some duplicated functions. About list the dependencies of a bundle, the karaf's show dependency function is not assembled in geronimo3.0, however, we could install it manually: 1) download the jar from: http://repo2.maven.org/maven2/org/apache/karaf/shell/org.apache.karaf.shell.dev/2.2.1/org.apache.karaf.shell.dev-2.2.1.jar 2) install the jar from the osgi console's install view. 3) input the : dev:show-tree bundleId to show the bundle's dependency but, it just can view the dependencies of a bundle, if want to show the import-package, export-package infos, karaf-2.2.1 does not have the function, the jira: https://issues.apache.org/jira/browse/KARAF-502 can do more help. Enhance introspection on Geronimo server for discovery of already-deployed OSGi bundles and dependencies amongst other bundles -- Key: GERONIMODEVTOOLS-618 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-618 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Fix For: 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-623) Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068139#comment-13068139 ] Yi Xiao commented on GERONIMODEVTOOLS-623: -- The function is implemented, the more detailed can be found in GERONIMODEVTOOLS-759. Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime --- Key: GERONIMODEVTOOLS-623 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Priority: Minor Fix For: 3.0 Must include the following artifacts: o EBA o WAB o OSGi bundle o OSGi Blueprint bundle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-633) Implement new EJB packaging when target runtime does not have full EJB capabilities
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-633: Assignee: Yi Xiao Implement new EJB packaging when target runtime does not have full EJB capabilities --- Key: GERONIMODEVTOOLS-633 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-633 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Yi Xiao Fix For: 3.0 i.e., namespace compliance and placement of EJB jar files in the WAR -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-632) Implement usage scenarios where target runtime is or isn't a Web Profile type server configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-632: Assignee: Yi Xiao (was: Delos Dai) Implement usage scenarios where target runtime is or isn't a Web Profile type server configuration Key: GERONIMODEVTOOLS-632 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-632 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Yi Xiao Fix For: 3.0 i.e., only WAR-type artifacts should be deployed on a Web Profile server -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-627) Implement introspection on Geronimo server to determine its capabilities
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-627: Assignee: Yi Xiao (was: Delos Dai) Implement introspection on Geronimo server to determine its capabilities Key: GERONIMODEVTOOLS-627 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-627 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Yi Xiao Fix For: 3.0 May already be supported by WTP. For example: o Full JEE6 spec-compliant server o Full Web Profile spec-compliant server o Derivation of either -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-623) Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-623. -- Resolution: Fixed Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime --- Key: GERONIMODEVTOOLS-623 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Priority: Minor Fix For: 3.0 Must include the following artifacts: o EBA o WAB o OSGi bundle o OSGi Blueprint bundle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-623) Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-623: Assignee: Yi Xiao (was: Delos Dai) Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime --- Key: GERONIMODEVTOOLS-623 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Yi Xiao Priority: Minor Fix For: 3.0 Must include the following artifacts: o EBA o WAB o OSGi bundle o OSGi Blueprint bundle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-638) Fully support all major error scenarios
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068140#comment-13068140 ] Yi Xiao commented on GERONIMODEVTOOLS-638: -- Hi Tim, could you pls explain more about the issue? Fully support all major error scenarios Key: GERONIMODEVTOOLS-638 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-638 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Fix For: 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-617) Implement reordering of artifacts during deployment and run-on-server functions to adhere to specified dependencies in deployment plans and/or bundle manifest
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068146#comment-13068146 ] Yi Xiao commented on GERONIMODEVTOOLS-617: -- I think the function should use a OSGi standard way to resolve. The GEP just deliver the bundles to server, the server need to calculate every bundle's dependencies by obr way, so the issue is dependent by GERONIMO-5939. Implement reordering of artifacts during deployment and run-on-server functions to adhere to specified dependencies in deployment plans and/or bundle manifests to ensure proper start order when started on the Geronimo server Key: GERONIMODEVTOOLS-617 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-617 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Fix For: 3.0 See see org.osgi.service.startlevel OSGi package -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-617) Implement reordering of artifacts during deployment and run-on-server functions to adhere to specified dependencies in deployment plans and/or bundle manifests
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-617: Assignee: Yi Xiao Implement reordering of artifacts during deployment and run-on-server functions to adhere to specified dependencies in deployment plans and/or bundle manifests to ensure proper start order when started on the Geronimo server Key: GERONIMODEVTOOLS-617 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-617 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Yi Xiao Fix For: 3.0 See see org.osgi.service.startlevel OSGi package -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-613) Miscellaneous Enhancements
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved GERONIMODEVTOOLS-613. -- Resolution: Fixed Miscellaneous Enhancements -- Key: GERONIMODEVTOOLS-613 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-613 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Fix For: 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-642) Support Remote Server deployment
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-642: - Issue Type: Wish (was: Sub-task) Parent: (was: GERONIMODEVTOOLS-613) Support Remote Server deployment Key: GERONIMODEVTOOLS-642 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-642 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Fix For: 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6080) When shutdown server or uninstall module in browser, could not dispaly the confirm dialog
When shutdown server or uninstall module in browser, could not dispaly the confirm dialog - Key: GERONIMO-6080 URL: https://issues.apache.org/jira/browse/GERONIMO-6080 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Environment: Windows7-64bit, Oracle-JDK1.6.25 WindowsXP-32bit, Oracle-JDK1.6.24 Reporter: Yi Xiao -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6080) When shutdown server or uninstall module in browser, could not dispaly the confirm dialog
[ https://issues.apache.org/jira/browse/GERONIMO-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-6080: -- Attachment: showDialog_6080.patch When shutdown server or uninstall module in browser, could not dispaly the confirm dialog - Key: GERONIMO-6080 URL: https://issues.apache.org/jira/browse/GERONIMO-6080 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: Windows7-64bit, Oracle-JDK1.6.25 WindowsXP-32bit, Oracle-JDK1.6.24 Reporter: Yi Xiao Labels: confirm, dialog Attachments: showDialog_6080.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13066761#comment-13066761 ] Yi Xiao commented on GERONIMODEVTOOLS-764: -- Thanks for your comments. 14 I will make the configuration in my editor~ 2 Yes, I agree with your option #3. I will add some descriptions to illustrate that change the default start level will not effect the server side. 3 I will create the BundleInfo in OSGiModuleHandler and persist the BundleInfo in GEP for more bundle osgi control. Control the OSGI bundle's start level in GEP Key: GERONIMODEVTOOLS-764 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Yi Xiao Labels: OSGI, startLevel Fix For: 3.0 Attachments: controlBundleStartLevel_764.patch, defaultStartLevel.jpg, singleStartLevel.jpg 1 Provide a UI interface to control all the bundles' start level 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-764: - Attachment: controlBundleStartLevel_764.patch Control the OSGI bundle's start level in GEP Key: GERONIMODEVTOOLS-764 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Yi Xiao Labels: OSGI, startLevel Fix For: 3.0 Attachments: controlBundleStartLevel_764.patch 1 Provide a UI interface to control all the bundles' start level 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065765#comment-13065765 ] Yi Xiao commented on GERONIMODEVTOOLS-764: -- The patch add a section named Default OSGI Bundle Start Level in server page to control all the user bundle's start level, and also, add a menu item when right click the module in servers view named Change Start Level to control a single bundle's start level. I will attach pics to show them. Control the OSGI bundle's start level in GEP Key: GERONIMODEVTOOLS-764 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Yi Xiao Labels: OSGI, startLevel Fix For: 3.0 Attachments: controlBundleStartLevel_764.patch 1 Provide a UI interface to control all the bundles' start level 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-764: - Attachment: singleStartLevel.jpg defaultStartLevel.jpg Control the OSGI bundle's start level in GEP Key: GERONIMODEVTOOLS-764 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Environment: WinXP sp3 32bit Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1SR2 Reporter: Yi Xiao Assignee: Yi Xiao Labels: OSGI, startLevel Fix For: 3.0 Attachments: controlBundleStartLevel_764.patch, defaultStartLevel.jpg, singleStartLevel.jpg 1 Provide a UI interface to control all the bundles' start level 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5764) Support Bundles Deployment in deployment command line
[ https://issues.apache.org/jira/browse/GERONIMO-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13065200#comment-13065200 ] Yi Xiao commented on GERONIMO-5764: --- As the life cycle of Geronimo's modules is not under the control of OSGI framework, only +10 in GEP side still can not work successfully. It will be a heavy work to make all the Geronimo's modules' under the control of OSGI framework, I think an optional way is that try to start the resolved bundles after all the Geronimo's modules have been started. Anyway, I will still add the OSGI start level code in GEP side. Support Bundles Deployment in deployment command line - Key: GERONIMO-5764 URL: https://issues.apache.org/jira/browse/GERONIMO-5764 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands, console, deployment Affects Versions: 3.0 Reporter: viola.lu Assignee: Rex Wang Priority: Critical Fix For: 3.0 Attachments: GERONIMO-5764-install-bundle.patch, GERONIMO-5764-install-uninstall-bundle.patch, GERONIMO-5764-record-bundle.patch, GERONIMO-5764.patch Now we have to deploy a regular bundle via karaf shell: osgi:install file:/[bunlde_path], not deployer command line, so open this jira to track this feature enablement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
