[jira] [Commented] (GERONIMO-5836) Identify migration differences from 2.x to 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13080719#comment-13080719 ] Chi Runhua commented on GERONIMO-5836: -- I've created a page on G3.0 doc site wit the following topics based on feedbacks from Viola, Ivan and other members within the community for differences between 2.x and 3.0. Please review and feel free to comment on or update. # Classloading options in the deployment plan # DB initialization at deployment time # JavaMail session generation and resource lookup # Dependencies changes # Servlets expecting multipart request # Changes regarding EJB component https://cwiki.apache.org/GMOxDOC30/migrating-from-g-2x-to-g-3x.html Jeff Identify migration differences from 2.x to 3.0 -- Key: GERONIMO-5836 URL: https://issues.apache.org/jira/browse/GERONIMO-5836 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor We need to identify the migration differences from 2.X to 3.0 and work out a piece of document for that. As far as I know that inverse-classloading doesn't work in 3.0. There might be more, please update the JIRA if you find any. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-5836) Identify migration differences from 2.x to 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5836: Assignee: Chi Runhua Identify migration differences from 2.x to 3.0 -- Key: GERONIMO-5836 URL: https://issues.apache.org/jira/browse/GERONIMO-5836 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor We need to identify the migration differences from 2.X to 3.0 and work out a piece of document for that. As far as I know that inverse-classloading doesn't work in 3.0. There might be more, please update the JIRA if you find any. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5701) [Doc]Update doc about running hudson sample on Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5701. -- Resolution: Fixed [Doc]Update doc about running hudson sample on Geronimo 3.0 --- Key: GERONIMO-5701 URL: https://issues.apache.org/jira/browse/GERONIMO-5701 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0-M1, 3.0-M2, 3.0 Environment: 3.0-M1 Reporter: viola.lu Assignee: Chi Runhua Priority: Minor Fix For: 3.0 According to the jira https://issues.apache.org/jira/browse/GERONIMO-5697, should update https://cwiki.apache.org/GMOxSAMPLES/running-hudson-on-geronimo.html for Geronimo 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5580) Document Update: Migrating from Tomcat to Geronimo, geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5580. -- Resolution: Fixed Doc updated accordingly. https://cwiki.apache.org/GMOxDOC30/migrating-from-tomcat-to-geronimo.html https://cwiki.apache.org/GMOxDOC30/geronimo-webxml.html Document Update: Migrating from Tomcat to Geronimo, geronimo-web.xml - Key: GERONIMO-5580 URL: https://issues.apache.org/jira/browse/GERONIMO-5580 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.2.2, 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Once the patch is checked-in, we should update Geronimo document accordingly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6011) Update geronimo-tomcat-config.1.0.xsd to include context element
[
https://issues.apache.org/jira/browse/GERONIMO-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chi Runhua resolved GERONIMO-6011.
--
Resolution: Fixed
Fix Version/s: 3.0
Committed revision 1148188.
Update geronimo-tomcat-config.1.0.xsd to include context element
--
Key: GERONIMO-6011
URL: https://issues.apache.org/jira/browse/GERONIMO-6011
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Reporter: Chi Runhua
Assignee: Chi Runhua
Priority: Minor
Fix For: 3.0
context element is tomcat-specific and now supported in tomcat-2.0.1.xsd,
but if a user uses web-2.0.1 as the default namespace and container-config
for tomcat-specific attributes in the deployment plan, the context element
will be a problem.
Take the following xml as an example:
{code:xml}
web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1;
xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2;
sys:environment
sys:moduleId
sys:groupIddefault/sys:groupId
sys:artifactIdgeronimo-web-6/sys:artifactId
sys:version1.0/sys:version
sys:typecar/sys:type
/sys:moduleId
/sys:environment
container-config
tomcat
xmlns=http://geronimo.apache.org/xml/ns/web/tomcat/config-1.0;
context ogEffectiveWebXml=true useHttpOnly=true
cacheMaxSize=2410 cacheObjectMaxSize=512 cachingAllowed=true
unloadDelay=2000/context
hosttesthost.com/host
valve-chainFirstValve/valve-chain
tomcat-realmTomcatRealm/tomcat-realm
/tomcat
/container-config
/web-app
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6011) Update geronimo-tomcat-config.1.0.xsd to include context element
[
https://issues.apache.org/jira/browse/GERONIMO-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chi Runhua reassigned GERONIMO-6011:
Assignee: Chi Runhua
Update geronimo-tomcat-config.1.0.xsd to include context element
--
Key: GERONIMO-6011
URL: https://issues.apache.org/jira/browse/GERONIMO-6011
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: Tomcat
Reporter: Chi Runhua
Assignee: Chi Runhua
Priority: Minor
context element is tomcat-specific and now supported in tomcat-2.0.1.xsd,
but if a user uses web-2.0.1 as the default namespace and container-config
for tomcat-specific attributes in the deployment plan, the context element
will be a problem.
Take the following xml as an example:
{code:xml}
web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1;
xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2;
sys:environment
sys:moduleId
sys:groupIddefault/sys:groupId
sys:artifactIdgeronimo-web-6/sys:artifactId
sys:version1.0/sys:version
sys:typecar/sys:type
/sys:moduleId
/sys:environment
container-config
tomcat
xmlns=http://geronimo.apache.org/xml/ns/web/tomcat/config-1.0;
context ogEffectiveWebXml=true useHttpOnly=true
cacheMaxSize=2410 cacheObjectMaxSize=512 cachingAllowed=true
unloadDelay=2000/context
hosttesthost.com/host
valve-chainFirstValve/valve-chain
tomcat-realmTomcatRealm/tomcat-realm
/tomcat
/container-config
/web-app
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6075) Support bundle installation and uninstallation via Karaf shell
Support bundle installation and uninstallation via Karaf shell -- Key: GERONIMO-6075 URL: https://issues.apache.org/jira/browse/GERONIMO-6075 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: commands Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor deploy:install-bundle deploy:uninstall-bundle should be supported via Karaf shell in Geronimo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6075) Support bundle installation and uninstallation via Karaf shell
[ https://issues.apache.org/jira/browse/GERONIMO-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-6075: - Attachment: 6075.patch Support bundle installation and uninstallation via Karaf shell -- Key: GERONIMO-6075 URL: https://issues.apache.org/jira/browse/GERONIMO-6075 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 3.0 Attachments: 6075.patch deploy:install-bundle deploy:uninstall-bundle should be supported via Karaf shell in Geronimo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6075) Support bundle installation and uninstallation via Karaf shell
[ https://issues.apache.org/jira/browse/GERONIMO-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13064630#comment-13064630 ] Chi Runhua commented on GERONIMO-6075: -- Hi Ivan, you mean refer to GERONIMO-5764 for the details. IIUC, the logic of those 2 commands is to record the bundle in Geronimo repository and record the information in /etc/startup.properties file after installation, then remove the record after uninstallation. In this way, the bundle could survive after a clean start. Rex had already implemented the feature in GERONIMO-5764. This JIRA is to simply enable the commands for Karaf shell. HTH. Support bundle installation and uninstallation via Karaf shell -- Key: GERONIMO-6075 URL: https://issues.apache.org/jira/browse/GERONIMO-6075 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 3.0 Attachments: 6075.patch, GERONIMO-6075-updated.patch deploy:install-bundle deploy:uninstall-bundle should be supported via Karaf shell in Geronimo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6075) Support bundle installation and uninstallation via Karaf shell
[ https://issues.apache.org/jira/browse/GERONIMO-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-6075. -- Resolution: Fixed Committed revision 1146091. Support bundle installation and uninstallation via Karaf shell -- Key: GERONIMO-6075 URL: https://issues.apache.org/jira/browse/GERONIMO-6075 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 3.0 Attachments: 6075.patch, GERONIMO-6075-updated.patch deploy:install-bundle deploy:uninstall-bundle should be supported via Karaf shell in Geronimo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (GERONIMO-6075) Support bundle installation and uninstallation via Karaf shell
[ https://issues.apache.org/jira/browse/GERONIMO-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13064630#comment-13064630 ] Chi Runhua edited comment on GERONIMO-6075 at 7/13/11 3:25 PM: --- Hi Ivan, you mean refer to GERONIMO-5764 for the details. IIUC, the logic of those 2 commands is to persist the bundle in Geronimo repository and record its information in /etc/startup.properties file after installation, then remove the record after uninstallation. In this way, the bundle could survive a clean start. Rex had already implemented the feature in GERONIMO-5764. This JIRA is to simply enable the commands for Karaf shell. HTH. was (Author: chi runhua): Hi Ivan, you mean refer to GERONIMO-5764 for the details. IIUC, the logic of those 2 commands is to record the bundle in Geronimo repository and record the information in /etc/startup.properties file after installation, then remove the record after uninstallation. In this way, the bundle could survive after a clean start. Rex had already implemented the feature in GERONIMO-5764. This JIRA is to simply enable the commands for Karaf shell. HTH. Support bundle installation and uninstallation via Karaf shell -- Key: GERONIMO-6075 URL: https://issues.apache.org/jira/browse/GERONIMO-6075 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 3.0 Attachments: 6075.patch, GERONIMO-6075-updated.patch deploy:install-bundle deploy:uninstall-bundle should be supported via Karaf shell in Geronimo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5836) Identify migration differences from 2.x to 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058505#comment-13058505 ] Chi Runhua commented on GERONIMO-5836: -- For DB initialization at deployment time, org.apache.geronimo.connector.DatabaseInitializationGBean in 2.X should be changed to org.apache.geronimo.connector.wrapper.DatabaseInitializationGBean Identify migration differences from 2.x to 3.0 -- Key: GERONIMO-5836 URL: https://issues.apache.org/jira/browse/GERONIMO-5836 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Affects Versions: 3.0 Reporter: Chi Runhua Priority: Minor We need to identify the migration differences from 2.X to 3.0 and work out a piece of document for that. As far as I know that inverse-classloading doesn't work in 3.0. There might be more, please update the JIRA if you find any. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6010) NPE when creating keystore from console
[ https://issues.apache.org/jira/browse/GERONIMO-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-6010. -- Resolution: Fixed Fix Version/s: 3.0 Thanks Shenghao Fang for the patch. Committed revision 1140982. Jeff C NPE when creating keystore from console --- Key: GERONIMO-6010 URL: https://issues.apache.org/jira/browse/GERONIMO-6010 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Environment: oracle jdk1.6_23 Geronimo build 0615 Reporter: Chi Runhua Assignee: Shenghao Fang Priority: Minor Fix For: 3.0 Attachments: GERONIMO-6010.patch 2011-06-15 15:08:23,498 WARN [FileKeystoreManager] The ConfigurationManager in the kernel does not allow changes at runtime 2011-06-15 15:08:23,500 ERROR [[Keystores]] Servlet.service() for servlet Keystores threw exception java.lang.NullPointerException at org.apache.geronimo.console.keystores.BaseKeystoreHandler$KeystoreData.unlockEdit(BaseKeystoreHandler.java:253) at org.apache.geronimo.console.keystores.CreateKeystoreHandler.actionAfterView(CreateKeystoreHandler.java:71) at org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:114) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:117) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:84) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:112) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:359) at org.apache.pluto.container.driver.PortletServlet.doPost(PortletServlet.java:267) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:101) at org.apache.pluto.container.impl.PortletContainerImpl.doAction(PortletContainerImpl.java:251) at org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:135) at org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:205) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.RedirectByHashFilter.doFilter(RedirectByHashFilter.java:116) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.apache.geronimo.tomcat.security.SecurityValve.invoke(SecurityValve.java:87) at org.apache.geronimo.tomcat.security.jacc.JACCSecurityValve.invoke(JACCSecurityValve.java:54) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:700) at
[jira] [Created] (GERONIMO-6027) fail to create BIO HTTPS connector for Tomcat using admin console
fail to create BIO HTTPS connector for Tomcat using admin console - Key: GERONIMO-6027 URL: https://issues.apache.org/jira/browse/GERONIMO-6027 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Chi Runhua Priority: Minor Tried to create a BIO https connector using admin console, and input all required fields, then click save. The connector fails to start. 2011-06-29 15:31:47,433 WARN [ConnectorGBean] test_BIOHTTPS connector failed 2011-06-29 15:31:47,433 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car,j2eeType=GBean,name=test_BIOHTTPS org.apache.xbean.recipe.ConstructionException: Error creating gbean of class: org.apache.geronimo.tomcat.connector.Https11ConnectorGBean, attempting to set nonexistent properties: [clientAuth] at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:955) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:567) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.connector.Https11Protocol$$EnhancerByCGLIB$$c056c043.startRecursive(generated) at org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorPortlet.java:152) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:117) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:84) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:112) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:359) at org.apache.pluto.container.driver.PortletServlet.doPost(PortletServlet.java:267) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:101) at org.apache.pluto.container.impl.PortletContainerImpl.doAction(PortletContainerImpl.java:251) at org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:135) at org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:205) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.RedirectByHashFilter.doFilter(RedirectByHashFilter.java:116) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130) at
[jira] [Updated] (GERONIMO-6027) fail to create BIO HTTPS connector for Tomcat using admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-6027: - Component/s: Tomcat console fail to create BIO HTTPS connector for Tomcat using admin console - Key: GERONIMO-6027 URL: https://issues.apache.org/jira/browse/GERONIMO-6027 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, Tomcat Reporter: Chi Runhua Priority: Minor Tried to create a BIO https connector using admin console, and input all required fields, then click save. The connector fails to start. 2011-06-29 15:31:47,433 WARN [ConnectorGBean] test_BIOHTTPS connector failed 2011-06-29 15:31:47,433 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car,j2eeType=GBean,name=test_BIOHTTPS org.apache.xbean.recipe.ConstructionException: Error creating gbean of class: org.apache.geronimo.tomcat.connector.Https11ConnectorGBean, attempting to set nonexistent properties: [clientAuth] at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:955) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:567) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.tomcat.connector.Https11Protocol$$EnhancerByCGLIB$$c056c043.startRecursive(generated) at org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorPortlet.java:152) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:117) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:84) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:112) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:359) at org.apache.pluto.container.driver.PortletServlet.doPost(PortletServlet.java:267) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:101) at org.apache.pluto.container.impl.PortletContainerImpl.doAction(PortletContainerImpl.java:251) at org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:135) at org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:205) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.RedirectByHashFilter.doFilter(RedirectByHashFilter.java:116) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48) at
[jira] [Resolved] (GERONIMO-5943) The 'Apache Aries Samples running in Geronimo 3.0' guide uses incorrect links
[ https://issues.apache.org/jira/browse/GERONIMO-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5943. -- Resolution: Fixed The 'Apache Aries Samples running in Geronimo 3.0' guide uses incorrect links - Key: GERONIMO-5943 URL: https://issues.apache.org/jira/browse/GERONIMO-5943 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Bartosz Kowalewski Assignee: Chi Runhua The 'Apache Aries Samples running in Geronimo 3.0' guide (https://cwiki.apache.org/GMOxDEV/apache-aries-samples-running-in-geronimo-30.html) points to https://cwiki.apache.org/ARIES/downloads.html, while it should point to http://aries.apache.org/downloads/currentrelease.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-5943) The 'Apache Aries Samples running in Geronimo 3.0' guide uses incorrect links
[ https://issues.apache.org/jira/browse/GERONIMO-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5943: Assignee: Chi Runhua The 'Apache Aries Samples running in Geronimo 3.0' guide uses incorrect links - Key: GERONIMO-5943 URL: https://issues.apache.org/jira/browse/GERONIMO-5943 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Bartosz Kowalewski Assignee: Chi Runhua The 'Apache Aries Samples running in Geronimo 3.0' guide (https://cwiki.apache.org/GMOxDEV/apache-aries-samples-running-in-geronimo-30.html) points to https://cwiki.apache.org/ARIES/downloads.html, while it should point to http://aries.apache.org/downloads/currentrelease.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5857) A mistake of the sample wsdl in JAX-RPC doc
[ https://issues.apache.org/jira/browse/GERONIMO-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5857. -- Resolution: Fixed 2.1/2.2/3.0 doc updated accordingly. A mistake of the sample wsdl in JAX-RPC doc --- Key: GERONIMO-5857 URL: https://issues.apache.org/jira/browse/GERONIMO-5857 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.7, 2.2.1, 3.0-M1 Reporter: Rex Wang Assignee: Chi Runhua Attachments: jaxrpc-converter-sample.zip in https://cwiki.apache.org/GMOxDOC21/developing-jax-rpc-web-services.html there is a mistake in the converter.wsdl all the soap:body use=literal / should be soap:body use=literal namespace=http://org.apache.geronimo.samples.jaxrpc// otherwise either our tool: jaxws-tools.bat wsimport -s C:\WSDL http://localhost:8080/jaxws-conveter/converter?wsdl and sun's tool wscomiple will report the same error: input message of binding operation greetMe must specify a value for the namespace attribute Ref: the warning message in eclipse of this line WS-I: (BP2020) A rpc-literal binding contains soapbind:body element(s) that either does not have a namespace attribute, or has a namespace attribute value that is not an absolute URI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5857) A mistake of the sample wsdl in JAX-RPC doc
[ https://issues.apache.org/jira/browse/GERONIMO-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua closed GERONIMO-5857. A mistake of the sample wsdl in JAX-RPC doc --- Key: GERONIMO-5857 URL: https://issues.apache.org/jira/browse/GERONIMO-5857 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.7, 2.2.1, 3.0-M1 Reporter: Rex Wang Assignee: Chi Runhua Attachments: jaxrpc-converter-sample.zip in https://cwiki.apache.org/GMOxDOC21/developing-jax-rpc-web-services.html there is a mistake in the converter.wsdl all the soap:body use=literal / should be soap:body use=literal namespace=http://org.apache.geronimo.samples.jaxrpc// otherwise either our tool: jaxws-tools.bat wsimport -s C:\WSDL http://localhost:8080/jaxws-conveter/converter?wsdl and sun's tool wscomiple will report the same error: input message of binding operation greetMe must specify a value for the namespace attribute Ref: the warning message in eclipse of this line WS-I: (BP2020) A rpc-literal binding contains soapbind:body element(s) that either does not have a namespace attribute, or has a namespace attribute value that is not an absolute URI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6010) NPE when creating keystore from console
NPE when creating keystore from console --- Key: GERONIMO-6010 URL: https://issues.apache.org/jira/browse/GERONIMO-6010 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Environment: oracle jdk1.6_23 Geronimo build 0615 Reporter: Chi Runhua Priority: Minor 2011-06-15 15:08:23,498 WARN [FileKeystoreManager] The ConfigurationManager in the kernel does not allow changes at runtime 2011-06-15 15:08:23,500 ERROR [[Keystores]] Servlet.service() for servlet Keystores threw exception java.lang.NullPointerException at org.apache.geronimo.console.keystores.BaseKeystoreHandler$KeystoreData.unlockEdit(BaseKeystoreHandler.java:253) at org.apache.geronimo.console.keystores.CreateKeystoreHandler.actionAfterView(CreateKeystoreHandler.java:71) at org.apache.geronimo.console.MultiPagePortlet.processAction(MultiPagePortlet.java:114) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:117) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:84) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:112) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:359) at org.apache.pluto.container.driver.PortletServlet.doPost(PortletServlet.java:267) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:101) at org.apache.pluto.container.impl.PortletContainerImpl.doAction(PortletContainerImpl.java:251) at org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:135) at org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:205) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.RedirectByHashFilter.doFilter(RedirectByHashFilter.java:116) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.apache.geronimo.tomcat.security.SecurityValve.invoke(SecurityValve.java:87) at org.apache.geronimo.tomcat.security.jacc.JACCSecurityValve.invoke(JACCSecurityValve.java:54) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:700) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48) at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at
[jira] [Created] (GERONIMO-6011) Update geronimo-tomcat-config.1.0.xsd to include context element
Update geronimo-tomcat-config.1.0.xsd to include context element
--
Key: GERONIMO-6011
URL: https://issues.apache.org/jira/browse/GERONIMO-6011
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Tomcat
Reporter: Chi Runhua
Priority: Minor
context element is tomcat-specific and now supported in tomcat-2.0.1.xsd, but
if a user uses web-2.0.1 as the default namespace and container-config for
tomcat-specific attributes in the deployment plan, the context element will
be a problem.
Take the following xml as an example:
{code:xml}
web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1;
xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2;
sys:environment
sys:moduleId
sys:groupIddefault/sys:groupId
sys:artifactIdgeronimo-web-6/sys:artifactId
sys:version1.0/sys:version
sys:typecar/sys:type
/sys:moduleId
/sys:environment
container-config
tomcat xmlns=http://geronimo.apache.org/xml/ns/web/tomcat/config-1.0;
context ogEffectiveWebXml=true useHttpOnly=true
cacheMaxSize=2410 cacheObjectMaxSize=512 cachingAllowed=true
unloadDelay=2000/context
hosttesthost.com/host
valve-chainFirstValve/valve-chain
tomcat-realmTomcatRealm/tomcat-realm
/tomcat
/container-config
/web-app
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-5924) Servlet.service() for servlet WARModules threw exception java.lang.SecurityException
Servlet.service() for servlet WARModules threw exception java.lang.SecurityException - Key: GERONIMO-5924 URL: https://issues.apache.org/jira/browse/GERONIMO-5924 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console, security Affects Versions: 3.0 Environment: 04/19 build, Sun JDK 1.6.0_21+Win7 Reporter: Chi Runhua Priority: Minor After hudson.war was deployed successfully, click WAR on navigation menu. The page failed to render. 2011-04-21 14:16:48,568 ERROR [[WARModules]] Servlet.service() for servlet WARModules threw exception java.lang.SecurityException: Invalid signature file digest for Manifest main attributes at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:221) at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:176) at java.util.jar.JarVerifier.processEntry(JarVerifier.java:245) at java.util.jar.JarVerifier.update(JarVerifier.java:199) at java.util.jar.JarFile.initializeVerifier(JarFile.java:323) at java.util.jar.JarFile.getInputStream(JarFile.java:388) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.loadConfigurationInfo(RepositoryConfigurationStore.java:497) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.listConfigurations(RepositoryConfigurationStore.java:455) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.listConfigurations(SimpleConfigurationManager.java:221) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.listConfigurations(SimpleConfigurationManager.java:193) at org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:225) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348) at javax.portlet.GenericPortlet.render(GenericPortlet.java:253) at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340) at org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117) at org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157) at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165) at jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:927) at jsp.WEB_002dINF.themes.portlets_002donly_jsp._jspx_meth_c_005fforEach_005f0(portlets_002donly_jsp.java:135) at jsp.WEB_002dINF.themes.portlets_002donly_jsp._jspService(portlets_002donly_jsp.java:69) at
[jira] [Updated] (GERONIMO-5924) Servlet.service() for servlet WARModules threw exception java.lang.SecurityException
[ https://issues.apache.org/jira/browse/GERONIMO-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5924: - Attachment: hudson-realm.xml hudson_DD.xml Servlet.service() for servlet WARModules threw exception java.lang.SecurityException - Key: GERONIMO-5924 URL: https://issues.apache.org/jira/browse/GERONIMO-5924 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, security Affects Versions: 3.0 Environment: 04/19 build, Sun JDK 1.6.0_21+Win7 Reporter: Chi Runhua Priority: Minor Attachments: hudson-realm.xml, hudson_DD.xml After hudson.war was deployed successfully, click WAR on navigation menu. The page failed to render. 2011-04-21 14:16:48,568 ERROR [[WARModules]] Servlet.service() for servlet WARModules threw exception java.lang.SecurityException: Invalid signature file digest for Manifest main attributes at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:221) at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:176) at java.util.jar.JarVerifier.processEntry(JarVerifier.java:245) at java.util.jar.JarVerifier.update(JarVerifier.java:199) at java.util.jar.JarFile.initializeVerifier(JarFile.java:323) at java.util.jar.JarFile.getInputStream(JarFile.java:388) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.loadConfigurationInfo(RepositoryConfigurationStore.java:497) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.listConfigurations(RepositoryConfigurationStore.java:455) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.listConfigurations(SimpleConfigurationManager.java:221) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.listConfigurations(SimpleConfigurationManager.java:193) at org.apache.geronimo.console.configmanager.ConfigManagerPortlet.doView(ConfigManagerPortlet.java:225) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:348) at javax.portlet.GenericPortlet.render(GenericPortlet.java:253) at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:163) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:91) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:105) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:340) at org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:117) at org.apache.pluto.container.impl.PortletContainerImpl.doRender(PortletContainerImpl.java:157) at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:165) at jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:927) at
[jira] [Created] (GERONIMO-5929) org.apache.geronimo.kernel.config.LiefcycleException when starting Hudson.war on G3.0
org.apache.geronimo.kernel.config.LiefcycleException when starting Hudson.war on G3.0 - Key: GERONIMO-5929 URL: https://issues.apache.org/jira/browse/GERONIMO-5929 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 3.0 Environment: Sun JDK 1.6.0_21, GBuild 04/19 Reporter: Chi Runhua Hudson.war can be deployed successfully, however, it fails to start because of the following exception: 2011-04-22 10:26:13,093 ERROR [DeploymentPortlet] The application was not successfully started. start of hudson/hudson/1.384/war failed org.apache.geronimo.kernel.config.LifecycleException: start of hudson/hudson/1.384/war failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:718) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:681) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:521) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:226) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:702) ... 3 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration hudson/hudson/1.384/war failed to start due to the following reasons: The service J2EEApplication=null,j2eeType=WebModule,name=hudson/hudson/1.384/war did not start because ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.io.IOException: Context did not start for an unknown reason java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.io.IOException: Context did not start for an unknown reason at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:816) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:787) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:310) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:569) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:975) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:301) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:301) at
[jira] [Updated] (GERONIMODEVTOOLS-736) Review GEP code according to Eclipse UI guideline and do necessary updates
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMODEVTOOLS-736: Attachment: 736.patch The patch focus on three problems mainly: 1. Capitalization problems 2. Hard coded messages in .Java files 3. Style problems Review GEP code according to Eclipse UI guideline and do necessary updates -- Key: GERONIMODEVTOOLS-736 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-736 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Attachments: 736.patch The guidelines doc is at http://wiki.eclipse.org/User_Interface_Guidelines -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (GERONIMODEVTOOLS-736) Review GEP code according to Eclipse UI guideline and do necessary updates
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021930#comment-13021930 ] Chi Runhua edited comment on GERONIMODEVTOOLS-736 at 4/20/11 3:06 AM: -- The patch focuses on three problems mainly: 1. Capitalization problems 2. Hard coded messages in .Java files 3. Style problems was (Author: chi runhua): The patch focus on three problems mainly: 1. Capitalization problems 2. Hard coded messages in .Java files 3. Style problems Review GEP code according to Eclipse UI guideline and do necessary updates -- Key: GERONIMODEVTOOLS-736 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-736 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Attachments: 736.patch The guidelines doc is at http://wiki.eclipse.org/User_Interface_Guidelines -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-736) Review GEP code according to Eclipse UI guideline and do necessary updates
Review GEP code according to Eclipse UI guideline and do necessary updates -- Key: GERONIMODEVTOOLS-736 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-736 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Chi Runhua Priority: Minor The guidelines doc is at http://wiki.eclipse.org/User_Interface_Guidelines -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5889) Avoid macros confusion with Tuscany templates
[ https://issues.apache.org/jira/browse/GERONIMO-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5889: - Attachment: 5899.patch 5899.patch Provide a patch for https://svn.apache.org/repos/asf/geronimo/site/trunk Avoid macros confusion with Tuscany templates - Key: GERONIMO-5889 URL: https://issues.apache.org/jira/browse/GERONIMO-5889 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation, website Affects Versions: 2.1, 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Attachments: 5899.patch, 5899.patch Update macros with a prefix 'gmo' within auto-export templates and fix some copyright year problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5892) An error window pops up when clicking on JNDI viewer
[ https://issues.apache.org/jira/browse/GERONIMO-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5892: - Description: 2011-04-08 13:29:11,955 WARN [BaseCallMarshaller] --Erroring: batchId[1] message[org.apache.geronimo.kernel.NoSuchAttributeException: Unknown attribute componentContext in gbean org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car?EJBModule=org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car,J2EEApplication=null,j2eeType=StatelessSessionBean,name=ejb/mgmt/MEJB] An error window pops up when clicking on JNDI viewer Key: GERONIMO-5892 URL: https://issues.apache.org/jira/browse/GERONIMO-5892 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Environment: 2011-04-07 Tomcat build Reporter: Chi Runhua Priority: Minor Attachments: JNDI_Viewer_Error.png 2011-04-08 13:29:11,955 WARN [BaseCallMarshaller] --Erroring: batchId[1] message[org.apache.geronimo.kernel.NoSuchAttributeException: Unknown attribute componentContext in gbean org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car?EJBModule=org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car,J2EEApplication=null,j2eeType=StatelessSessionBean,name=ejb/mgmt/MEJB] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-5889) Avoid macros confusion with Tuscany templates
Avoid macros confusion with Tuscany templates - Key: GERONIMO-5889 URL: https://issues.apache.org/jira/browse/GERONIMO-5889 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: documentation, website Affects Versions: 2.1, 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Update macros with a prefix 'gmo' within auto-export templates and fix some copyright year problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5880) NPE during installation of blog EBA
[ https://issues.apache.org/jira/browse/GERONIMO-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5880: - Attachment: blog-datasource.xml The plan file to create the datasource. NPE during installation of blog EBA --- Key: GERONIMO-5880 URL: https://issues.apache.org/jira/browse/GERONIMO-5880 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Environment: Sun JDK 1.6.0_23 GBuild 2011-03-25 Aries 0.2 sample application - blog Reporter: Chi Runhua Priority: Minor Attachments: blog-datasource.xml 1. Deploy the datasource via Deployer 2. Install blog.datasource bundle 3. Deploy blog-jpa.EBA 4. Open localhost:8080/blog and HTTP 404 error shows up. Look into geronimo.log and I can see NPE during installation of EBA. 2011-03-25 11:23:48,424 ERROR [WebBeansAnnotatedTypeUtil] Error is occured while getting injection points for the Java EE component instance class, class org.apache.catalina.core.StandardWrapper java.lang.NullPointerException at org.apache.webbeans.portable.AnnotatedTypeImpl.init(AnnotatedTypeImpl.java:77) at org.apache.webbeans.portable.AnnotatedTypeImpl.getFields(AnnotatedTypeImpl.java:174) at org.apache.webbeans.util.WebBeansAnnotatedTypeUtil.defineInjectedFields(WebBeansAnnotatedTypeUtil.java:340) at org.apache.webbeans.component.creation.AbstractInjectedTargetBeanCreator.defineInjectedFields(AbstractInjectedTargetBeanCreator.java:80) at org.apache.webbeans.util.WebBeansAnnotatedTypeUtil.getJavaEeComponentInstanceInjectionPoints(WebBeansAnnotatedTypeUtil.java:724) at org.apache.webbeans.inject.OWBInjector.inject(OWBInjector.java:126) at org.apache.webbeans.inject.OWBInjector.inject(OWBInjector.java:93) at org.apache.geronimo.j2ee.annotation.Holder.newInstance(Holder.java:185) at org.apache.geronimo.tomcat.TomcatInstanceManager.newInstance(TomcatInstanceManager.java:74) at org.apache.geronimo.tomcat.GeronimoStandardContext.createWrapper(GeronimoStandardContext.java:364) at org.apache.catalina.core.ApplicationContext.addServlet(ApplicationContext.java:) at org.apache.catalina.core.ApplicationContext.addServlet(ApplicationContext.java:1041) at org.apache.catalina.core.ApplicationContextFacade.addServlet(ApplicationContextFacade.java:509) at org.apache.geronimo.web.assembler.Assembler.addServlet(Assembler.java:74) at org.apache.geronimo.web.assembler.Assembler.assemble(Assembler.java:44) at org.apache.geronimo.tomcat.BaseGeronimoContextConfig.configureStart(BaseGeronimoContextConfig.java:91) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:317) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4881) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:106) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:688) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48) at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) at org.apache.geronimo.tomcat.GeronimoStandardContext.startInternal(GeronimoStandardContext.java:470) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:812) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:787) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:310) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:569) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:975) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at
[jira] Assigned: (GERONIMO-5857) A mistake of the sample wsdl in JAX-RPC doc
[ https://issues.apache.org/jira/browse/GERONIMO-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5857: Assignee: Chi Runhua A mistake of the sample wsdl in JAX-RPC doc --- Key: GERONIMO-5857 URL: https://issues.apache.org/jira/browse/GERONIMO-5857 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.7, 2.2.1, 3.0-M1 Reporter: Rex Wang Assignee: Chi Runhua Attachments: jaxrpc-converter-sample.zip in https://cwiki.apache.org/GMOxDOC21/developing-jax-rpc-web-services.html there is a mistake in the converter.wsdl all the soap:body use=literal / should be soap:body use=literal namespace=http://org.apache.geronimo.samples.jaxrpc// otherwise either our tool: jaxws-tools.bat wsimport -s C:\WSDL http://localhost:8080/jaxws-conveter/converter?wsdl and sun's tool wscomiple will report the same error: input message of binding operation greetMe must specify a value for the namespace attribute Ref: the warning message in eclipse of this line WS-I: (BP2020) A rpc-literal binding contains soapbind:body element(s) that either does not have a namespace attribute, or has a namespace attribute value that is not an absolute URI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-724) Remove those redundant periods on GEP configuration UI
Remove those redundant periods on GEP configuration UI -- Key: GERONIMODEVTOOLS-724 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-724 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.7, 2.2.1, 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMODEVTOOLS-724) Remove those redundant periods on GEP configuration UI
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMODEVTOOLS-724: Attachment: GERONIMODEVTOOLS-724.patch Remove those redundant periods on GEP configuration UI -- Key: GERONIMODEVTOOLS-724 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-724 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.1, 2.1.7, 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Attachments: GERONIMODEVTOOLS-724.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-5774) some osgi portlet improvements
[ https://issues.apache.org/jira/browse/GERONIMO-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001246#comment-13001246 ] Chi Runhua commented on GERONIMO-5774: -- Found several problems on OSGi portlet FYR. 1. the layout of buttons should be resized according to the size of the window; 2. *Filter by Symbolic Name* function does not work, at least on my firefox 3.6.13; 3. If I click the *Click here* twice, the portlet freezes for nearly 60 seconds. 4. start level of a newly installed bundle can not be specified, is there any reason the feature is removed? Thanks~! Jeff some osgi portlet improvements -- Key: GERONIMO-5774 URL: https://issues.apache.org/jira/browse/GERONIMO-5774 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 in the admin console there is a portlet for searching the osgi bundles but the search filter is case sensitive and there is no way to turn it off or on -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-5836) Identify migration differences from 2.x to 3.0
Identify migration differences from 2.x to 3.0 -- Key: GERONIMO-5836 URL: https://issues.apache.org/jira/browse/GERONIMO-5836 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Affects Versions: 3.0 Reporter: Chi Runhua Priority: Minor We need to identify the migration differences from 2.X to 3.0 and work out a piece of document for that. As far as I know that inverse-classloading doesn't work in 3.0. There might be more, please update the JIRA if you find any. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-5799) Provide documentation on how to enable OSGi framework debugging
[ https://issues.apache.org/jira/browse/GERONIMO-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5799: Assignee: Chi Runhua (was: Jarek Gawor) Provide documentation on how to enable OSGi framework debugging --- Key: GERONIMO-5799 URL: https://issues.apache.org/jira/browse/GERONIMO-5799 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Chi Runhua Provide documentation on how to enable OSGi framework debugging for Felix and Equinox. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-5799) Provide documentation on how to enable OSGi framework debugging
[ https://issues.apache.org/jira/browse/GERONIMO-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12989015#comment-12989015 ] Chi Runhua commented on GERONIMO-5799: -- The draft is ready at https://cwiki.apache.org/confluence/display/GMOxDOC30/Configuring+the+OSGi+environment please feel free to update. Jeff Provide documentation on how to enable OSGi framework debugging --- Key: GERONIMO-5799 URL: https://issues.apache.org/jira/browse/GERONIMO-5799 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: osgi Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Chi Runhua Provide documentation on how to enable OSGi framework debugging for Felix and Equinox. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-5758) Add a short tutorial on how to create/build a blueprint bundle and deploy it to the server (using GEP)
Add a short tutorial on how to create/build a blueprint bundle and deploy it to the server (using GEP) -- Key: GERONIMO-5758 URL: https://issues.apache.org/jira/browse/GERONIMO-5758 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor As the subject. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5758) Add a short tutorial on how to create/build a blueprint bundle and deploy it to the server (using GEP)
[ https://issues.apache.org/jira/browse/GERONIMO-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12982560#action_12982560 ] Chi Runhua commented on GERONIMO-5758: -- I borrowed the HelloWorld application from Aries for the tutorial. The text part is almost complete. The snapshots will be provided soon. See https://cwiki.apache.org/GMOxDOC30/developing-a-hello-world-blueprint-application.html Add a short tutorial on how to create/build a blueprint bundle and deploy it to the server (using GEP) -- Key: GERONIMO-5758 URL: https://issues.apache.org/jira/browse/GERONIMO-5758 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor As the subject. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5758) Add a short tutorial on how to create/build a blueprint bundle and deploy it to the server (using GEP)
[ https://issues.apache.org/jira/browse/GERONIMO-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5758. -- Resolution: Fixed Fix Version/s: 3.0-M2 The tutorial is ready with both content and screenshots. See https://cwiki.apache.org/GMOxDOC30/developing-a-hello-world-blueprint-application.html Jeff Add a short tutorial on how to create/build a blueprint bundle and deploy it to the server (using GEP) -- Key: GERONIMO-5758 URL: https://issues.apache.org/jira/browse/GERONIMO-5758 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 3.0-M2 As the subject. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5756) insure that the Geronimo website conforms to the current brand and trademark requirements in Apache
[ https://issues.apache.org/jira/browse/GERONIMO-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5756: - Priority: Minor (was: Major) insure that the Geronimo website conforms to the current brand and trademark requirements in Apache --- Key: GERONIMO-5756 URL: https://issues.apache.org/jira/browse/GERONIMO-5756 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: website Affects Versions: 2.1.7, 2.2.1, 3.0-M1 Reporter: Chi Runhua Priority: Minor We need to insure that the Geronimo website conforms to the current brand and trademark requirements as described in http://www.apache.org/foundation/marks/pmcs The scanning result: +++ Project Website complied Project Naming and Description complied Website navigation links complied Trademark attributionswe don't have one on the Geronimo homepage, might need to update the main page? TM on logos and graphics we don't have the TM symbol in the graphic, might need to update the Graphic? Powered By ... Logos didn't find anything on Geronimo website similar to http://www.apache.org/images/apache_pb.gif, so we might just pass this one? Other trademark guideline GShell is written with Groovy, might need to use GShell for Groovy instead of GShell? - the header statement The goal of refers to the Geronimo project, rather than the Apache Geronimo project - theres a requirement for a prominent link to the ASF home page...which the link in the Overview panel may/may not comply with Agree on Trademarks/Powered by/Other guidelines. Guessing there'd be a need to check out the subproject sites as well (noted that the GBuild link in the nav panel looks to be broken). For the details, see http://apache-geronimo.328035.n3.nabble.com/Geronimo-Branding-td1917541.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5756) insure that the Geronimo website conforms to the current brand and trademark requirements in Apache
insure that the Geronimo website conforms to the current brand and trademark requirements in Apache --- Key: GERONIMO-5756 URL: https://issues.apache.org/jira/browse/GERONIMO-5756 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: website Affects Versions: 3.0-M1, 2.2.1, 2.1.7 Reporter: Chi Runhua We need to insure that the Geronimo website conforms to the current brand and trademark requirements as described in http://www.apache.org/foundation/marks/pmcs The scanning result: +++ Project Website complied Project Naming and Description complied Website navigation links complied Trademark attributionswe don't have one on the Geronimo homepage, might need to update the main page? TM on logos and graphics we don't have the TM symbol in the graphic, might need to update the Graphic? Powered By ... Logos didn't find anything on Geronimo website similar to http://www.apache.org/images/apache_pb.gif, so we might just pass this one? Other trademark guideline GShell is written with Groovy, might need to use GShell for Groovy instead of GShell? - the header statement The goal of refers to the Geronimo project, rather than the Apache Geronimo project - theres a requirement for a prominent link to the ASF home page...which the link in the Overview panel may/may not comply with Agree on Trademarks/Powered by/Other guidelines. Guessing there'd be a need to check out the subproject sites as well (noted that the GBuild link in the nav panel looks to be broken). For the details, see http://apache-geronimo.328035.n3.nabble.com/Geronimo-Branding-td1917541.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5732) html pages for G2.2 schema files
html pages for G2.2 schema files Key: GERONIMO-5732 URL: https://issues.apache.org/jira/browse/GERONIMO-5732 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: website Affects Versions: 2.2.1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor The patch provides the .html format pages for schema files in G2.2.1 as Geronimo did for previous releases. The .zip file includes all schema diagrams used by the html files, please unzip them under /docs/schema-2.2/docs/schemaDiagrams directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5732) html pages for G2.2 schema files
[ https://issues.apache.org/jira/browse/GERONIMO-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5732: - Attachment: 5732.patch schemaDiagrams.zip zip file with schema diagrams html pages for G2.2 schema files Key: GERONIMO-5732 URL: https://issues.apache.org/jira/browse/GERONIMO-5732 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: website Affects Versions: 2.2.1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 2.2.1 Attachments: 5732.patch, schemaDiagrams.zip The patch provides the .html format pages for schema files in G2.2.1 as Geronimo did for previous releases. The .zip file includes all schema diagrams used by the html files, please unzip them under /docs/schema-2.2/docs/schemaDiagrams directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5732) html pages for G2.2 schema files
[ https://issues.apache.org/jira/browse/GERONIMO-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5732. -- Resolution: Fixed Fix Version/s: 2.2.1 html pages for G2.2 schema files Key: GERONIMO-5732 URL: https://issues.apache.org/jira/browse/GERONIMO-5732 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: website Affects Versions: 2.2.1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 2.2.1 Attachments: 5732.patch, schemaDiagrams.zip The patch provides the .html format pages for schema files in G2.2.1 as Geronimo did for previous releases. The .zip file includes all schema diagrams used by the html files, please unzip them under /docs/schema-2.2/docs/schemaDiagrams directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5727) [Doc] Update doc about section: Monitoring components on Geronimo Server
[ https://issues.apache.org/jira/browse/GERONIMO-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5727. -- Resolution: Fixed Fix Version/s: (was: 2.1.7) (was: 2.2) 2.2.1 2.1.8 Doc of G2.1/G2.2 updated accordingly 1) https://cwiki.apache.org/GMOxDOC21/monitoring.html 2) https://cwiki.apache.org/GMOxDOC22/monitoring-components-on-geronimo-server.html Jeff C [Doc] Update doc about section: Monitoring components on Geronimo Server -- Key: GERONIMO-5727 URL: https://issues.apache.org/jira/browse/GERONIMO-5727 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.7, 2.2 Reporter: viola.lu Assignee: Chi Runhua Priority: Minor Fix For: 2.1.8, 2.2.1 Now default protocol is JMX, and if change JMX to EJB, should change module agent-car-ejb from load=false to true in config.xml , so should update doc: https://cwiki.apache.org/GMOxDOC22/monitoring-components-on-geronimo-server.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5707) Document the usage of dery authentication and possible problems during updgrade
[ https://issues.apache.org/jira/browse/GERONIMO-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5707. -- Resolution: Fixed Fix Version/s: 2.2.1 2.1.7 Doc updated for G2.1.7 at https://cwiki.apache.org/GMOxDOC21/administering-users-and-groups.html https://cwiki.apache.org/GMOxDOC21/configuring-a-derby-datasource.html For G2.2.1 doc, see https://cwiki.apache.org/GMOxDOC22/administering-users-and-groups.html https://cwiki.apache.org/GMOxDOC22/configuring-a-derby-datasource.html Document the usage of dery authentication and possible problems during updgrade --- Key: GERONIMO-5707 URL: https://issues.apache.org/jira/browse/GERONIMO-5707 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.7, 2.2.1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 2.1.7, 2.2.1 Refer to GERONIMO-5689, GERONIMO-4296, users need provide credentials to access embedded derby databases starting from 2.1.7/2.2.1. We should have the document on 1. how to turn on/off the authentication 2. how to change the password of new derby admin 3. how to access user-defined databases when using previous versions 4. how to run sql statements when the derby authentication ss turned on 5. what happens to the datasource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5707) Document the usage of derby authentication and possible problems during updgrade
[ https://issues.apache.org/jira/browse/GERONIMO-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5707: - Summary: Document the usage of derby authentication and possible problems during updgrade (was: Document the usage of dery authentication and possible problems during updgrade) Document the usage of derby authentication and possible problems during updgrade Key: GERONIMO-5707 URL: https://issues.apache.org/jira/browse/GERONIMO-5707 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.7, 2.2.1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 2.1.7, 2.2.1 Refer to GERONIMO-5689, GERONIMO-4296, users need provide credentials to access embedded derby databases starting from 2.1.7/2.2.1. We should have the document on 1. how to turn on/off the authentication 2. how to change the password of new derby admin 3. how to access user-defined databases when using previous versions 4. how to run sql statements when the derby authentication ss turned on 5. what happens to the datasource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5707) Document the usage of dery authentication and possible problems during updgrade
Document the usage of dery authentication and possible problems during updgrade --- Key: GERONIMO-5707 URL: https://issues.apache.org/jira/browse/GERONIMO-5707 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.7, 2.2.1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Refer to GERONIMO-5689, GERONIMO-4296, users need provide credentials to access embedded derby databases starting from 2.1.7/2.2.1. We should have the document on 1. how to turn on/off the authentication 2. how to change the password of new derby admin 3. how to access user-defined databases when using previous versions 4. how to run sql statements when the derby authentication ss turned on 5. what happens to the datasource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5615) Failed to deploy war files after putting server directory under C:\Documents and Settings\myDir
[ https://issues.apache.org/jira/browse/GERONIMO-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5615: Assignee: Chi Runhua Failed to deploy war files after putting server directory under C:\Documents and Settings\myDir - Key: GERONIMO-5615 URL: https://issues.apache.org/jira/browse/GERONIMO-5615 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0 Environment: OS: Windows XP SP3 Reporter: Chris Zhang Assignee: Chi Runhua Priority: Minor Fix For: 3.0 The steps to recur are: (1) Create a directory called myDir under C:\Documents and Settings (2) Put the geronimo server directory under C:\Documents and Settings\myDir. Now the server root directory is C:\Documents and Settings\myDir\g. (3) Start the server and login to the admin console. (4) Deploy a war file and some exceptions thrown. The exception information is: 2010-09-20 16:33:48,329 ERROR [DeploymentPortlet] The application was not deployed. Unable to create configuration for deployment: dependencies: null org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment: dependencies: null at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:208) at org.apache.geronimo.deployment.DeploymentContext.initializeConfiguration(DeploymentContext.java:188) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:615) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:736) Caused by: org.osgi.framework.BundleException: An error occurred trying to read the bundle at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:94) at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:922) at org.eclipse.osgi.framework.internal.core.Framework$1.run(Framework.java:838) at java.security.AccessController.doPrivileged(AccessController.java:251) at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:889) at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:833) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:167) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java) at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:200) ... 15 more Caused by: java.io.FileNotFoundException: C:\Documents%20and%20Settings\myDir\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-fileutils3448848740305009830.tmpfile at org.eclipse.osgi.framework.internal.protocol.reference.ReferenceURLConnection.connect(ReferenceURLConnection.java:46) at org.eclipse.osgi.framework.internal.protocol.reference.ReferenceURLConnection.getInputStream(ReferenceURLConnection.java:61) at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:56) ... 23 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5615) Failed to deploy war files after putting server directory under C:\Documents and Settings\myDir
[ https://issues.apache.org/jira/browse/GERONIMO-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5615: - Component/s: (was: deployment) documentation Update the component to document and we'll have a troubleshooting item for this one. Users should avoid using the path with whitespaces. Jeff Failed to deploy war files after putting server directory under C:\Documents and Settings\myDir - Key: GERONIMO-5615 URL: https://issues.apache.org/jira/browse/GERONIMO-5615 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0 Environment: OS: Windows XP SP3 Reporter: Chris Zhang Assignee: Chi Runhua Priority: Minor Fix For: 3.0 The steps to recur are: (1) Create a directory called myDir under C:\Documents and Settings (2) Put the geronimo server directory under C:\Documents and Settings\myDir. Now the server root directory is C:\Documents and Settings\myDir\g. (3) Start the server and login to the admin console. (4) Deploy a war file and some exceptions thrown. The exception information is: 2010-09-20 16:33:48,329 ERROR [DeploymentPortlet] The application was not deployed. Unable to create configuration for deployment: dependencies: null org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment: dependencies: null at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:208) at org.apache.geronimo.deployment.DeploymentContext.initializeConfiguration(DeploymentContext.java:188) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:615) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:250) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:736) Caused by: org.osgi.framework.BundleException: An error occurred trying to read the bundle at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:94) at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:922) at org.eclipse.osgi.framework.internal.core.Framework$1.run(Framework.java:838) at java.security.AccessController.doPrivileged(AccessController.java:251) at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:889) at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:833) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:167) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java) at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:200) ... 15 more Caused by: java.io.FileNotFoundException: C:\Documents%20and%20Settings\myDir\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-fileutils3448848740305009830.tmpfile at org.eclipse.osgi.framework.internal.protocol.reference.ReferenceURLConnection.connect(ReferenceURLConnection.java:46) at org.eclipse.osgi.framework.internal.protocol.reference.ReferenceURLConnection.getInputStream(ReferenceURLConnection.java:61) at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:56) ... 23 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5484) Create a document for JavaEE 6 sample application - EJBTimer
[ https://issues.apache.org/jira/browse/GERONIMO-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5484. -- Resolution: Fixed Fix Version/s: 3.0 Doc is ready at https://cwiki.apache.org/GMOxDOC30/ejbtimer-javaee6-a-simple-ejb-timer-service-application.html Create a document for JavaEE 6 sample application - EJBTimer - Key: GERONIMO-5484 URL: https://issues.apache.org/jira/browse/GERONIMO-5484 Project: Geronimo Issue Type: Wish Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Fix For: 3.0 The document should be as followed: # Application overview # Application content # Application implementation # Get the source code # Build the application # Deploy the application # Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5413) Documentation of Generic Header based authentication support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5413. -- Resolution: Fixed Doc is ready at https://cwiki.apache.org/GMOxDOC21/configuring-http-header-based-authentication.html Documentation of Generic Header based authentication support in geronimo Key: GERONIMO-5413 URL: https://issues.apache.org/jira/browse/GERONIMO-5413 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Reporter: Amit Puri Assignee: Chi Runhua Fix For: 2.1.7 Geronimo should include documentation regarding Generic Header based authentication. It is related to generic header authentication login module which should be able to validate the authentication results passed as http request headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5661) Geronimo fails to start when there is a whitespace in Geronimo_HOME
[ https://issues.apache.org/jira/browse/GERONIMO-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua closed GERONIMO-5661. Resolution: Fixed Fix Version/s: 3.0 The problem is fixed now. thanks a lot. Geronimo fails to start when there is a whitespace in Geronimo_HOME --- Key: GERONIMO-5661 URL: https://issues.apache.org/jira/browse/GERONIMO-5661 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 3.0 Environment: Ubuntu 9.04+Sun JDK 1.6.0_18 Reporter: Chi Runhua Assignee: viola.lu Fix For: 3.0 Attachments: G5661.patch, G5661_ALL.patch Geronimo 2.2.1 works fine when there is a whitespace within GERONIMO_HOME while G3.0 fails to start. + jeff...@ubuntu:~/Documents/Geronimo/test/Document and setting/g30/bin$ ./geronimo run Using GERONIMO_HOME: /home/jeffchi/Documents/Geronimo/test/Document and setting/g30 Using GERONIMO_TMPDIR: var/temp Using JRE_HOME:/opt/sun/jdk1.6.0_18/jre Exception in thread main java.lang.NoClassDefFoundError: and Caused by: java.lang.ClassNotFoundException: and at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Could not find the main class: and. Program will exit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5574) Update console related docs for geronimo-4950 change
[ https://issues.apache.org/jira/browse/GERONIMO-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua closed GERONIMO-5574. Resolution: Fixed Fix Version/s: 3.0 We have documented the following improvements in 3.0. 1. Basic and advance sets of navigation items; 2. Quick search bar; The doc is at https://cwiki.apache.org/confluence/display/GMOxDOC30/Introducing+Geronimo+Administration+Console Update console related docs for geronimo-4950 change Key: GERONIMO-5574 URL: https://issues.apache.org/jira/browse/GERONIMO-5574 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Chi Runhua Assignee: Chi Runhua Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4950) Improve usability of Geronimo Console
[
https://issues.apache.org/jira/browse/GERONIMO-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chi Runhua closed GERONIMO-4950.
Resolution: Fixed
Fix Version/s: 3.0
All sub-tasks are completed. I believe the JIRA could be closed now.
Improve usability of Geronimo Console
-
Key: GERONIMO-4950
URL: https://issues.apache.org/jira/browse/GERONIMO-4950
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 3.0
Reporter: Chi Runhua
Assignee: Chi Runhua
Priority: Minor
Fix For: 3.0
Attachments: 4950.patch, New navigation group.png
1. re-structure the navigation tree to make it collapsible, the tree level
should be less than 3;
2. re-organize the available tree items into new groups, here is a sample
list for implementation:
* Application Server
** Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
** Web Server
** JMS Server
** EJB Server
** Derby server
** New server assembly
* Applications
** Deploy New (Suggest to merge in the plan creator, so that users can
either choose to use an existing plan file, or create a new one using the
wizard)
** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?)
** Plugins
* Resources
** DB pools
** JMS Resources
** J2EE Connectors
** Jar aliases
** Repository
* Security
** Users and Groups
** Keystores
** Certificate Authority
** Security Realms
* Monitoring and Troubleshooting
** Monitoring
** Logs(Include server logs and Derby log)
** Debug Views
*** JMX Viewer
*** Classloader Viewer
*** JNDI Viewer
*** Dependency Viewer
3. re-construct the available portlets to improve embedded assistance
information, for example, show breadcrum when user is working on a task;
reduce in-line text on the current UI, and use hover-help or pop-up help page
only when necessary etc...
4. for the long list on the current UI such as system modules, only show the
most frequently used ones, use locate/find to display more
{color:red}*Risks*{color} to be noticed for UI changes:
1. Doc
2. Testsuite especially for Selenium test script, if any.
For more details, see
hhttp://apache-geronimo.328035.n3.nabble.com/DISCUSS-Reorg-of-Admin-Console-for-2-2-td400707.html#a400707
Further discussion on navigation items, see
http://apache-geronimo.328035.n3.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2-2-td370812.html#a370812
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5661) Geronimo fails to start when there is a whitespace in Geronimo_HOME
Geronimo fails to start when there is a whitespace in Geronimo_HOME --- Key: GERONIMO-5661 URL: https://issues.apache.org/jira/browse/GERONIMO-5661 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: commands Affects Versions: 3.0 Environment: Ubuntu 9.04+Sun JDK 1.6.0_18 Reporter: Chi Runhua Geronimo 2.2.1 works fine when there is a whitespace within GERONIMO_HOME while G3.0 fails to start. + jeff...@ubuntu:~/Documents/Geronimo/test/Document and setting/g30/bin$ ./geronimo run Using GERONIMO_HOME: /home/jeffchi/Documents/Geronimo/test/Document and setting/g30 Using GERONIMO_TMPDIR: var/temp Using JRE_HOME:/opt/sun/jdk1.6.0_18/jre Exception in thread main java.lang.NoClassDefFoundError: and Caused by: java.lang.ClassNotFoundException: and at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Could not find the main class: and. Program will exit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5525) Geronimo launch failed for Multiple Geronimo Instances
[ https://issues.apache.org/jira/browse/GERONIMO-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5525: Assignee: Chi Runhua Geronimo launch failed for Multiple Geronimo Instances --- Key: GERONIMO-5525 URL: https://issues.apache.org/jira/browse/GERONIMO-5525 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 3.0 Reporter: Delos Dai Assignee: Chi Runhua According to the configuration https://cwiki.apache.org/GMOxDOC22/running-multiple-geronimo-instances.html, I configure Geronimo 3.0 trunk build, but it can't start in case of multi instances. Here is the error message after geronimo run, Error launching framework: java.lang.NullPointerException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5525) Geronimo launch failed for Multiple Geronimo Instances
[ https://issues.apache.org/jira/browse/GERONIMO-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922021#action_12922021 ] Chi Runhua commented on GERONIMO-5525: -- Thanks Shawn for the information, I updated G3.0 doc accordingly at https://cwiki.apache.org/confluence/display/GMOxDOC30/Running+multiple+Geronimo+instances Jeff Chi Geronimo launch failed for Multiple Geronimo Instances --- Key: GERONIMO-5525 URL: https://issues.apache.org/jira/browse/GERONIMO-5525 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 3.0 Reporter: Delos Dai Assignee: Chi Runhua According to the configuration https://cwiki.apache.org/GMOxDOC22/running-multiple-geronimo-instances.html, I configure Geronimo 3.0 trunk build, but it can't start in case of multi instances. Here is the error message after geronimo run, Error launching framework: java.lang.NullPointerException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5448) Update news for Geronimo 2.1.6 and 3.0M1 on Geronimo website
[ https://issues.apache.org/jira/browse/GERONIMO-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua closed GERONIMO-5448. Resolution: Fixed Fix Version/s: 2.1.6 3.0-M1 The news page was updated and published by Rick. So closing. Update news for Geronimo 2.1.6 and 3.0M1 on Geronimo website Key: GERONIMO-5448 URL: https://issues.apache.org/jira/browse/GERONIMO-5448 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.6, 3.0-M1 Reporter: Chi Runhua Assignee: Rick McGuire Fix For: 3.0-M1, 2.1.6 Geronimo 2.1.6 and 3.0M1 have been released for some time, but the news on GMOxSITE is still showing the latest version is 2.1.5 I think we should update the news. See http://geronimo.apache.org/index.html http://geronimo.apache.org/news-archive.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5580) Document Update: Migrating from Tomcat to Geronimo, geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5580: - Affects Version/s: 2.2.2 Document Update: Migrating from Tomcat to Geronimo, geronimo-web.xml - Key: GERONIMO-5580 URL: https://issues.apache.org/jira/browse/GERONIMO-5580 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.2.2, 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Once the patch is checked-in, we should update Geronimo document accordingly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5580) Document Update: Migrating from Tomcat to Geronimo, geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5580: Assignee: Chi Runhua Document Update: Migrating from Tomcat to Geronimo, geronimo-web.xml - Key: GERONIMO-5580 URL: https://issues.apache.org/jira/browse/GERONIMO-5580 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.2.2, 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Once the patch is checked-in, we should update Geronimo document accordingly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5413) Documentation of Generic Header based authentication support in geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5413: Assignee: Chi Runhua Documentation of Generic Header based authentication support in geronimo Key: GERONIMO-5413 URL: https://issues.apache.org/jira/browse/GERONIMO-5413 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Reporter: Amit Puri Assignee: Chi Runhua Fix For: 2.1.7 Geronimo should include documentation regarding Generic Header based authentication. It is related to generic header authentication login module which should be able to validate the authentication results passed as http request headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5589) Display basic set of navigation items in a list instead of a true
Display basic set of navigation items in a list instead of a true - Key: GERONIMO-5589 URL: https://issues.apache.org/jira/browse/GERONIMO-5589 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: Chi Runhua -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5590) startup script does not consume --help option
startup script does not consume --help option - Key: GERONIMO-5590 URL: https://issues.apache.org/jira/browse/GERONIMO-5590 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: commands Affects Versions: 2.2, 2.1.4, 3.0 Reporter: Chi Runhua Priority: Trivial When I initiated a *startup -h* or *startup -help* on a linux platform, the server will start in background instead of showing the help information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5589) Display basic set of navigation items in a list instead of a tree
[ https://issues.apache.org/jira/browse/GERONIMO-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5589: - Summary: Display basic set of navigation items in a list instead of a tree (was: Display basic set of navigation items in a list instead of a true) Affects Version/s: 2.2.2 3.0 Priority: Minor (was: Major) Component/s: console Display basic set of navigation items in a list instead of a tree - Key: GERONIMO-5589 URL: https://issues.apache.org/jira/browse/GERONIMO-5589 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: console Affects Versions: 2.2.2, 3.0 Reporter: Chi Runhua Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5584) identify basic set of navigation items
[ https://issues.apache.org/jira/browse/GERONIMO-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5584: - Attachment: 5584.patch Sort out the basic set of navigation items, which includes: 1. welcome 2. WAR 3. EAR 4. EBA And in the patch, I also added EBA portlet into jetty build. Please review and commit the patch. Thanks~!. Jeff identify basic set of navigation items -- Key: GERONIMO-5584 URL: https://issues.apache.org/jira/browse/GERONIMO-5584 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Trivial Attachments: 5584.patch Based on Geronimo-5516, we can set 2 groups of navigation items in G3.0. Basic for the frequently used ones and Advance for the full set. We should identify the items in the basic set, which might be from my perspective: 0/Welcome 1-1-1/Application Server/System Information/Server Information 2-1/Applications/Deployer 2-2-1/Applications/User Assets/Web App WARs Any other comments? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-5584) identify basic set of navigation items
[ https://issues.apache.org/jira/browse/GERONIMO-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12907857#action_12907857 ] Chi Runhua edited comment on GERONIMO-5584 at 9/9/10 9:43 PM: -- Sort out the basic set of navigation items, which includes: 1. welcome 2. Deployer 3. WAR 4. EAR 5. EBA And in the patch, I also added EBA portlet into jetty build. Please review and commit the patch. Thanks~!. Jeff was (Author: chi runhua): Sort out the basic set of navigation items, which includes: 1. welcome 2. WAR 3. EAR 4. EBA And in the patch, I also added EBA portlet into jetty build. Please review and commit the patch. Thanks~!. Jeff identify basic set of navigation items -- Key: GERONIMO-5584 URL: https://issues.apache.org/jira/browse/GERONIMO-5584 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: console Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Trivial Attachments: 5584.patch Based on Geronimo-5516, we can set 2 groups of navigation items in G3.0. Basic for the frequently used ones and Advance for the full set. We should identify the items in the basic set, which might be from my perspective: 0/Welcome 1-1-1/Application Server/System Information/Server Information 2-1/Applications/Deployer 2-2-1/Applications/User Assets/Web App WARs Any other comments? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5580) Document Update: Migrating from Tomcat to Geronimo, geronimo-web.xml
Document Update: Migrating from Tomcat to Geronimo, geronimo-web.xml - Key: GERONIMO-5580 URL: https://issues.apache.org/jira/browse/GERONIMO-5580 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: documentation Affects Versions: 3.0 Reporter: Chi Runhua Priority: Minor Once the patch is checked-in, we should update Geronimo document accordingly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5584) identify basic set of navigation items
identify basic set of navigation items -- Key: GERONIMO-5584 URL: https://issues.apache.org/jira/browse/GERONIMO-5584 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Trivial Based on Geronimo-5516, we can set 2 groups of navigation items in G3.0. Basic for the frequently used ones and Advance for the full set. We should identify the items in the basic set, which might be from my perspective: 0/Welcome 1-1-1/Application Server/System Information/Server Information 2-1/Applications/Deployer 2-2-1/Applications/User Assets/Web App WARs Any other comments? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5573) Fix console-testsuite for Geroniom-4950 change
Fix console-testsuite for Geroniom-4950 change -- Key: GERONIMO-5573 URL: https://issues.apache.org/jira/browse/GERONIMO-5573 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: testsuite Affects Versions: 2.2.2, 3.0-M1 Reporter: Chi Runhua Priority: Minor The navigation items were re-grouped and we have to update console-testsuite accordingly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5574) Update console related docs for geronimo-4950 change
Update console related docs for geronimo-4950 change Key: GERONIMO-5574 URL: https://issues.apache.org/jira/browse/GERONIMO-5574 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: Chi Runhua Assignee: Chi Runhua -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4950) Improve usability of Geronimo Console
[
https://issues.apache.org/jira/browse/GERONIMO-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901717#action_12901717
]
Chi Runhua commented on GERONIMO-4950:
--
I tried console-testsuite on trunk/tomcat-7-web assembly and there are 16
pases and 24 failures.
8 of failed testcases are because that those portlets are not available in
web-profile assembly such as JMS, DB manager etc.
For the rest of failed testcases, I'll open a JIRA when 4950-patch is accepted.
As for doc, I'll open another one after that.
Jeff
Improve usability of Geronimo Console
-
Key: GERONIMO-4950
URL: https://issues.apache.org/jira/browse/GERONIMO-4950
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 3.0
Reporter: Chi Runhua
Assignee: Chi Runhua
Priority: Minor
Attachments: 4950.patch, New navigation group.png
1. re-structure the navigation tree to make it collapsible, the tree level
should be less than 3;
2. re-organize the available tree items into new groups, here is a sample
list for implementation:
* Application Server
** Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
** Web Server
** JMS Server
** EJB Server
** Derby server
** New server assembly
* Applications
** Deploy New (Suggest to merge in the plan creator, so that users can
either choose to use an existing plan file, or create a new one using the
wizard)
** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?)
** Plugins
* Resources
** DB pools
** JMS Resources
** J2EE Connectors
** Jar aliases
** Repository
* Security
** Users and Groups
** Keystores
** Certificate Authority
** Security Realms
* Monitoring and Troubleshooting
** Monitoring
** Logs(Include server logs and Derby log)
** Debug Views
*** JMX Viewer
*** Classloader Viewer
*** JNDI Viewer
*** Dependency Viewer
3. re-construct the available portlets to improve embedded assistance
information, for example, show breadcrum when user is working on a task;
reduce in-line text on the current UI, and use hover-help or pop-up help page
only when necessary etc...
4. for the long list on the current UI such as system modules, only show the
most frequently used ones, use locate/find to display more
{color:red}*Risks*{color} to be noticed for UI changes:
1. Doc
2. Testsuite especially for Selenium test script, if any.
For more details, see
hhttp://apache-geronimo.328035.n3.nabble.com/DISCUSS-Reorg-of-Admin-Console-for-2-2-td400707.html#a400707
Further discussion on navigation items, see
http://apache-geronimo.328035.n3.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2-2-td370812.html#a370812
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5516) Add isAdvanced properties to AdminConsoleExtensionGBean
[ https://issues.apache.org/jira/browse/GERONIMO-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5516: - Affects Version/s: 2.2.2 Add isAdvanced properties to AdminConsoleExtensionGBean --- Key: GERONIMO-5516 URL: https://issues.apache.org/jira/browse/GERONIMO-5516 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console Affects Versions: 2.2.2, 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Add a boolean property for AdminConsoleExtensionGBean and in this way, we can control whether the portlet should be displayed on Admin Console or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4950) Improve usability of Geronimo Console
[
https://issues.apache.org/jira/browse/GERONIMO-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12900195#action_12900195
]
Chi Runhua commented on GERONIMO-4950:
--
Well, I think I've got this task done and attaching a patch for review. So far
I can only assemble a Web Profile file and you may find the actual layout in
the attached screeshot.
For the pages not shown right now, I also updated in the patch so that they
could instantly integrated when they are assembled in.
Any comments, please let me know.
Jeff
Improve usability of Geronimo Console
-
Key: GERONIMO-4950
URL: https://issues.apache.org/jira/browse/GERONIMO-4950
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 3.0
Reporter: Chi Runhua
Assignee: Chi Runhua
Priority: Minor
1. re-structure the navigation tree to make it collapsible, the tree level
should be less than 3;
2. re-organize the available tree items into new groups, here is a sample
list for implementation:
* Application Server
** Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
** Web Server
** JMS Server
** EJB Server
** Derby server
** New server assembly
* Applications
** Deploy New (Suggest to merge in the plan creator, so that users can
either choose to use an existing plan file, or create a new one using the
wizard)
** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?)
** Plugins
* Resources
** DB pools
** JMS Resources
** J2EE Connectors
** Jar aliases
** Repository
* Security
** Users and Groups
** Keystores
** Certificate Authority
** Security Realms
* Monitoring and Troubleshooting
** Monitoring
** Logs(Include server logs and Derby log)
** Debug Views
*** JMX Viewer
*** Classloader Viewer
*** JNDI Viewer
*** Dependency Viewer
3. re-construct the available portlets to improve embedded assistance
information, for example, show breadcrum when user is working on a task;
reduce in-line text on the current UI, and use hover-help or pop-up help page
only when necessary etc...
4. for the long list on the current UI such as system modules, only show the
most frequently used ones, use locate/find to display more
{color:red}*Risks*{color} to be noticed for UI changes:
1. Doc
2. Testsuite especially for Selenium test script, if any.
For more details, see
hhttp://apache-geronimo.328035.n3.nabble.com/DISCUSS-Reorg-of-Admin-Console-for-2-2-td400707.html#a400707
Further discussion on navigation items, see
http://apache-geronimo.328035.n3.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2-2-td370812.html#a370812
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4950) Improve usability of Geronimo Console
[
https://issues.apache.org/jira/browse/GERONIMO-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chi Runhua updated GERONIMO-4950:
-
Attachment: 4950.patch
New navigation group.png
patch for trunk/2.2 branch.
screenshot for demonstration.
Improve usability of Geronimo Console
-
Key: GERONIMO-4950
URL: https://issues.apache.org/jira/browse/GERONIMO-4950
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 3.0
Reporter: Chi Runhua
Assignee: Chi Runhua
Priority: Minor
Attachments: 4950.patch, New navigation group.png
1. re-structure the navigation tree to make it collapsible, the tree level
should be less than 3;
2. re-organize the available tree items into new groups, here is a sample
list for implementation:
* Application Server
** Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
** Web Server
** JMS Server
** EJB Server
** Derby server
** New server assembly
* Applications
** Deploy New (Suggest to merge in the plan creator, so that users can
either choose to use an existing plan file, or create a new one using the
wizard)
** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?)
** Plugins
* Resources
** DB pools
** JMS Resources
** J2EE Connectors
** Jar aliases
** Repository
* Security
** Users and Groups
** Keystores
** Certificate Authority
** Security Realms
* Monitoring and Troubleshooting
** Monitoring
** Logs(Include server logs and Derby log)
** Debug Views
*** JMX Viewer
*** Classloader Viewer
*** JNDI Viewer
*** Dependency Viewer
3. re-construct the available portlets to improve embedded assistance
information, for example, show breadcrum when user is working on a task;
reduce in-line text on the current UI, and use hover-help or pop-up help page
only when necessary etc...
4. for the long list on the current UI such as system modules, only show the
most frequently used ones, use locate/find to display more
{color:red}*Risks*{color} to be noticed for UI changes:
1. Doc
2. Testsuite especially for Selenium test script, if any.
For more details, see
hhttp://apache-geronimo.328035.n3.nabble.com/DISCUSS-Reorg-of-Admin-Console-for-2-2-td400707.html#a400707
Further discussion on navigation items, see
http://apache-geronimo.328035.n3.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2-2-td370812.html#a370812
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5516) Add isAdvanced properties to AdminConsoleExtensionGBean
Add isAdvanced properties to AdminConsoleExtensionGBean --- Key: GERONIMO-5516 URL: https://issues.apache.org/jira/browse/GERONIMO-5516 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Add a boolean property for AdminConsoleExtensionGBean and in this way, we can control whether the portlet should be displayed on Admin Console or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4950) Improve usability of Geronimo Console
[
https://issues.apache.org/jira/browse/GERONIMO-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chi Runhua reassigned GERONIMO-4950:
Assignee: Chi Runhua
Improve usability of Geronimo Console
-
Key: GERONIMO-4950
URL: https://issues.apache.org/jira/browse/GERONIMO-4950
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 3.0
Reporter: Chi Runhua
Assignee: Chi Runhua
Priority: Minor
1. re-structure the navigation tree to make it collapsible, the tree level
should be less than 3;
2. re-organize the available tree items into new groups, here is a sample
list for implementation:
* Application Server
** Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
** Web Server
** JMS Server
** EJB Server
** Derby server
** New server assembly
* Applications
** Deploy New (Suggest to merge in the plan creator, so that users can
either choose to use an existing plan file, or create a new one using the
wizard)
** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?)
** Plugins
* Resources
** DB pools
** JMS Resources
** J2EE Connectors
** Jar aliases
** Repository
* Security
** Users and Groups
** Keystores
** Certificate Authority
** Security Realms
* Monitoring and Troubleshooting
** Monitoring
** Logs(Include server logs and Derby log)
** Debug Views
*** JMX Viewer
*** Classloader Viewer
*** JNDI Viewer
*** Dependency Viewer
3. re-construct the available portlets to improve embedded assistance
information, for example, show breadcrum when user is working on a task;
reduce in-line text on the current UI, and use hover-help or pop-up help page
only when necessary etc...
4. for the long list on the current UI such as system modules, only show the
most frequently used ones, use locate/find to display more
{color:red}*Risks*{color} to be noticed for UI changes:
1. Doc
2. Testsuite especially for Selenium test script, if any.
For more details, see
hhttp://apache-geronimo.328035.n3.nabble.com/DISCUSS-Reorg-of-Admin-Console-for-2-2-td400707.html#a400707
Further discussion on navigation items, see
http://apache-geronimo.328035.n3.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2-2-td370812.html#a370812
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4950) Improve usability of Geronimo Console
[
https://issues.apache.org/jira/browse/GERONIMO-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chi Runhua updated GERONIMO-4950:
-
Description:
1. re-structure the navigation tree to make it collapsible, the tree level
should be less than 3;
2. re-organize the available tree items into new groups, here is a sample list
for implementation:
* Application Server
** Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
** Web Server
** JMS Server
** EJB Server
** Derby server
** New server assembly
* Applications
** Deploy New (Suggest to merge in the plan creator, so that users can either
choose to use an existing plan file, or create a new one using the wizard)
** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?)
** Plugins
* Resources
** DB pools
** JMS Resources
** J2EE Connectors
** Jar aliases
** Repository
* Security
** Users and Groups
** Keystores
** Certificate Authority
** Security Realms
* Monitoring and Troubleshooting
** Monitoring
** Logs(Include server logs and Derby log)
** Debug Views
*** JMX Viewer
*** Classloader Viewer
*** JNDI Viewer
*** Dependency Viewer
3. re-construct the available portlets to improve embedded assistance
information, for example, show breadcrum when user is working on a task; reduce
in-line text on the current UI, and use hover-help or pop-up help page only
when necessary etc...
4. for the long list on the current UI such as system modules, only show the
most frequently used ones, use locate/find to display more
{color:red}*Risks*{color} to be noticed for UI changes:
1. Doc
2. Testsuite especially for Selenium test script, if any.
For more details, see
hhttp://apache-geronimo.328035.n3.nabble.com/DISCUSS-Reorg-of-Admin-Console-for-2-2-td400707.html#a400707
Further discussion on navigation items, see
http://apache-geronimo.328035.n3.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2-2-td370812.html#a370812
was:
1. re-structure the navigation tree to make it collapsible, the tree level
should be less than 3;
2. re-organize the available tree items into new groups, here is a sample list
for implementation:
* Application Server
** Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
** Web Server
** JMS Server
** EJB Server
** Derby server
** New server assembly
* Applications
** Deploy New (Suggest to merge in the plan creator, so that users can either
choose to use an existing plan file, or create a new one using the wizard)
** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?)
** Plugins
* Resources
** DB pools
** JMS Resources
** J2EE Connectors
** Jar aliases
** Repository
* Security
** Users and Groups
** Keystores
** Certificate Authority
** Security Realms
* Monitoring and Troubleshooting
** Monitoring
** Logs(Include server logs and Derby log)
** Debug Views
*** JMX Viewer
*** Classloader Viewer
*** JNDI Viewer
*** Dependency Viewer
3. re-construct the available portlets to improve embedded assistance
information, for example, show breadcrum when user is working on a task; reduce
in-line text on the current UI, and use hover-help or pop-up help page only
when necessary etc...
4. for the long list on the current UI such as system modules, only show the
most frequently used ones, use locate/find to display more
{color:red}*Risks*{color} to be noticed for UI changes:
1. Doc
2. Testsuite especially for Selenium test script, if any.
For more details, see
http://old.nabble.com/-Discussion-Re-org-admin-console-ts26217086s134.html
Further discussion on navigation items, see
http://old.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2.2-to26438212s134.html
Improve usability of Geronimo Console
-
Key: GERONIMO-4950
URL: https://issues.apache.org/jira/browse/GERONIMO-4950
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: console
Affects Versions: 3.0
Reporter: Chi Runhua
Priority: Minor
1. re-structure the navigation tree to make it collapsible, the tree level
should be less than 3;
2. re-organize the available tree items into new groups, here is a sample
list for implementation:
* Application Server
** Geronimo Kernel (put Information, Java System Info, Thread Pool and
Shutdown portlets in the same page here)
** Web Server
** JMS Server
** EJB Server
** Derby server
** New server assembly
* Applications
** Deploy New (Suggest to merge in the plan creator, so that users can
either choose to use an existing plan file, or create a new one using the
wizard)
** User applications (merge WAR, EAR and Client, maybe bundles
[jira] Assigned: (GERONIMO-5485) Create a document for JavaEE 6 sample application - singletonejb
[ https://issues.apache.org/jira/browse/GERONIMO-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5485: Assignee: Chi Runhua Create a document for JavaEE 6 sample application - singletonejb Key: GERONIMO-5485 URL: https://issues.apache.org/jira/browse/GERONIMO-5485 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua The document should be as followed: # Application overview # Application content # Application implementation # Get the source code # Build the application # Deploy the application # Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5493) Rename files' name in singletonejb-javaee6 Sample
[ https://issues.apache.org/jira/browse/GERONIMO-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12894798#action_12894798 ] Chi Runhua commented on GERONIMO-5493: -- I just noticed that there is another singletonejb implementation code within javeee6-testsuite[1] other than the one in sample trunk[2]. IIUC, both provides the same functionalities. However, the one in javeee6-testsuite is much more clear and straightforward for users to understand. I'd like to suggest to replace the current singletonejb-javaee6 sample code with the one in testsuite. [1]. https://svn.apache.org/repos/asf/geronimo/server/trunk/testsuite/javaee6-testsuite/ejb3.1lite-test/ [2]. https://svn.apache.org/repos/asf/geronimo/samples/trunk/samples/javaee6/singletonejb-javaee6/ Any comments? Jeff Rename files' name in singletonejb-javaee6 Sample - Key: GERONIMO-5493 URL: https://issues.apache.org/jira/browse/GERONIMO-5493 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: sample apps Affects Versions: 3.0 Reporter: LiWenQin Priority: Minor Fix For: 3.0 Sample singletonejb-javaee6 used singleton session bean, but the file name is StatefulCalculator.java. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5484) Create a document for JavaEE 6 sample application - EJBTimer
Create a document for JavaEE 6 sample application - EJBTimer - Key: GERONIMO-5484 URL: https://issues.apache.org/jira/browse/GERONIMO-5484 Project: Geronimo Issue Type: Wish Security Level: public (Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor The document should be as followed: # Application overview # Application content # Application implementation # Get the source code # Build the application # Deploy the application # Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5485) Create a document for JavaEE 6 sample application - singletonejb
Create a document for JavaEE 6 sample application - singletonejb Key: GERONIMO-5485 URL: https://issues.apache.org/jira/browse/GERONIMO-5485 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 3.0-M1 Reporter: Chi Runhua The document should be as followed: # Application overview # Application content # Application implementation # Get the source code # Build the application # Deploy the application # Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5443) Doc: update component versions page for 2.1.6 release
[ https://issues.apache.org/jira/browse/GERONIMO-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-5443. -- Resolution: Fixed Doc: update component versions page for 2.1.6 release - Key: GERONIMO-5443 URL: https://issues.apache.org/jira/browse/GERONIMO-5443 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.6 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor The component versions for each release should be identified clearly. Following page will be updated accordingly: [1]. https://cwiki.apache.org/GMOxDOC21/what-is-changed-in-21.html#Whatischangedin2.1-Componentversions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5448) Update news for Geronimo 2.1.6 and 3.0M1 on Geronimo website
[ https://issues.apache.org/jira/browse/GERONIMO-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua reassigned GERONIMO-5448: Assignee: Rick McGuire Rick, since you were the release manager of 2.1.6 and 3.0.M1, you might want to update the news on Geronimo website. Thanks. Update news for Geronimo 2.1.6 and 3.0M1 on Geronimo website Key: GERONIMO-5448 URL: https://issues.apache.org/jira/browse/GERONIMO-5448 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.6, 3.0-M1 Reporter: Chi Runhua Assignee: Rick McGuire Geronimo 2.1.6 and 3.0M1 have been released for some time, but the news on GMOxSITE is still showing the latest version is 2.1.5 I think we should update the news. See http://geronimo.apache.org/index.html http://geronimo.apache.org/news-archive.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5448) Update news for Geronimo 2.1.6 and 3.0M1 on Geronimo website
Update news for Geronimo 2.1.6 and 3.0M1 on Geronimo website Key: GERONIMO-5448 URL: https://issues.apache.org/jira/browse/GERONIMO-5448 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.6, 3.0-M1 Reporter: Chi Runhua Geronimo 2.1.6 and 3.0M1 have been released for some time, but the news on GMOxSITE is still showing the latest version is 2.1.5 I think we should update the news. See http://geronimo.apache.org/index.html http://geronimo.apache.org/news-archive.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5443) Doc: update component versions page for 2.1.6 and 2.2.1 releases
[ https://issues.apache.org/jira/browse/GERONIMO-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12887263#action_12887263 ] Chi Runhua commented on GERONIMO-5443: -- Done for 2.1.6 release. See https://cwiki.apache.org/GMOxDOC21/what-is-changed-in-21.html#Whatischangedin2.1-Componentversions Doc: update component versions page for 2.1.6 and 2.2.1 releases Key: GERONIMO-5443 URL: https://issues.apache.org/jira/browse/GERONIMO-5443 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.6 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor The component versions for each release should be identified clearly. Following 2 pages will be updated accordingly: [1]. https://cwiki.apache.org/GMOxDOC21/what-is-changed-in-21.html#Whatischangedin2.1-Componentversions [2]. https://cwiki.apache.org/GMOxDOC22/component-versions.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5443) Doc: update component versions page for 2.1.6 release
[ https://issues.apache.org/jira/browse/GERONIMO-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5443: - Summary: Doc: update component versions page for 2.1.6 release (was: Doc: update component versions page for 2.1.6 and 2.2.1 releases) Affects Version/s: (was: 2.2.1) Description: The component versions for each release should be identified clearly. Following page will be updated accordingly: [1]. https://cwiki.apache.org/GMOxDOC21/what-is-changed-in-21.html#Whatischangedin2.1-Componentversions was: The component versions for each release should be identified clearly. Following 2 pages will be updated accordingly: [1]. https://cwiki.apache.org/GMOxDOC21/what-is-changed-in-21.html#Whatischangedin2.1-Componentversions [2]. https://cwiki.apache.org/GMOxDOC22/component-versions.html Doc: update component versions page for 2.1.6 release - Key: GERONIMO-5443 URL: https://issues.apache.org/jira/browse/GERONIMO-5443 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1.6 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor The component versions for each release should be identified clearly. Following page will be updated accordingly: [1]. https://cwiki.apache.org/GMOxDOC21/what-is-changed-in-21.html#Whatischangedin2.1-Componentversions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5442) links to download release notes are all broken.
links to download release notes are all broken. --- Key: GERONIMO-5442 URL: https://issues.apache.org/jira/browse/GERONIMO-5442 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.6, 2.2.1 Reporter: Chi Runhua Priority: Minor As title, the problem exists for both 2.1.6 and 2.2.1 releases. you may verify the following links [1] http://www.apache.org/dyn/closer.cgi/geronimo/2.1.6/RELEASE_NOTES-2.1.6.txt [2] http://www.apache.org/dyn/closer.cgi/geronimo/2.2/RELEASE_NOTES-2.2.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5421) create new gogo command deploy:unlockKeystore
[ https://issues.apache.org/jira/browse/GERONIMO-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5421: - Attachment: 5421.patch Implement the unlockkeystore command, please help review. create new gogo command deploy:unlockKeystore -- Key: GERONIMO-5421 URL: https://issues.apache.org/jira/browse/GERONIMO-5421 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor Attachments: 5421.patch I'll provide a patch to migrate deploy/unlockKeystore into gogo command. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5425) Need description for oracel driver when creating a database pool
Need description for oracel driver when creating a database pool Key: GERONIMO-5425 URL: https://issues.apache.org/jira/browse/GERONIMO-5425 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: console Affects Versions: 2.2, 2.1.5 Reporter: Chi Runhua Priority: Minor some of fields don't have description as others. TNS Entry Name, DataSource Name. etc -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5420) gogo comand deploy:install-plugin not working properly
gogo comand deploy:install-plugin not working properly
--
Key: GERONIMO-5420
URL: https://issues.apache.org/jira/browse/GERONIMO-5420
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: commands
Affects Versions: 3.0-M1
Environment: Ubtun 9.0.4+JDK 1.6.0
Reporter: Chi Runhua
Priority: Minor
{code}
geronimo install-plugin
/home/jeffchi/plugins/hello-tomcat/target/helloworld.car
Checking for status every 1000ms:
2010-07-01 16:13:17,593 ERROR [PluginInstallerGBean] Invalid Configuration
Archive /home/jeffchi/Geronimo/geronimo-tomcat7-javaee6-3.0-M1/bin no plugin
metadata found
Installation FAILED: Invalid Configuration Archive
/home/jeffchi/Geronimo/geronimo-tomcat7-javaee6-3.0-M1/bin no plugin metadata
found
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5421) create new gogo command deploy:unlockKeystore
create new gogo command deploy:unlockKeystore -- Key: GERONIMO-5421 URL: https://issues.apache.org/jira/browse/GERONIMO-5421 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: commands Affects Versions: 3.0-M1 Reporter: Chi Runhua Assignee: Chi Runhua Priority: Minor I'll provide a patch to migrate deploy/unlockKeystore into gogo command. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5393) create new gogo command deploy:encrypt
create new gogo command deploy:encrypt --- Key: GERONIMO-5393 URL: https://issues.apache.org/jira/browse/GERONIMO-5393 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: commands Affects Versions: 3.0-M1 Reporter: Chi Runhua Geronimo should provide deploy:encrypt command in Felix shell. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5394) create new gogo command deploy:list-targets
create new gogo command deploy:list-targets --- Key: GERONIMO-5394 URL: https://issues.apache.org/jira/browse/GERONIMO-5394 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: commands Affects Versions: 3.0-M1 Reporter: Chi Runhua Geronimo should provide list-target command in Felix shell. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5393) create new gogo command deploy:encrypt
[ https://issues.apache.org/jira/browse/GERONIMO-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua closed GERONIMO-5393. Fix Version/s: 3.0-M1 Resolution: Invalid Sorry, the deploy:encrypt command is available in 3.0-M1 release. create new gogo command deploy:encrypt --- Key: GERONIMO-5393 URL: https://issues.apache.org/jira/browse/GERONIMO-5393 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands Affects Versions: 3.0-M1 Reporter: Chi Runhua Fix For: 3.0-M1 Geronimo should provide deploy:encrypt command in Felix shell. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5394) create new gogo command deploy:list-targets
[ https://issues.apache.org/jira/browse/GERONIMO-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua closed GERONIMO-5394. Resolution: Invalid Sorry, the command is already in 3.0-M1 release. create new gogo command deploy:list-targets --- Key: GERONIMO-5394 URL: https://issues.apache.org/jira/browse/GERONIMO-5394 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: commands Affects Versions: 3.0-M1 Reporter: Chi Runhua Geronimo should provide list-target command in Felix shell. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5323) Chinese and Japanese Translation for JIRA 5055
[ https://issues.apache.org/jira/browse/GERONIMO-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-5323: - Attachment: 5323_zh.patch UI translation of Informix extra attributes for Simp. Chinese Chinese and Japanese Translation for JIRA 5055 -- Key: GERONIMO-5323 URL: https://issues.apache.org/jira/browse/GERONIMO-5323 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2.1 Environment: Windows XP Reporter: LiWenQin Priority: Minor Fix For: 2.2.2 Attachments: 5323_zh.patch, screenshot-1.jpg, screenshot-2.jpg The console will display English (it should display Chinese/English) in a few lines with Using Informix tranql XA in g221 , if the browse language is set to Chinese/Japanese. Who can help translate and modify the files below? plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_zh.properties plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_ja.properties Thanks! PS: Refer to https://issues.apache.org/jira/browse/GERONIMO-5055, plugins/system-database/sysdb-portlets/src/main/i18n-resources/systemdatabase_en.properties has been modified. You can modify systemdatabase_zh.properties systemdatabase_ja.properties accordingly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5363) Classloader viewer not working
Classloader viewer not working -- Key: GERONIMO-5363 URL: https://issues.apache.org/jira/browse/GERONIMO-5363 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Environment: Firefox+Ubuntu+Tomcat assembly Reporter: Chi Runhua Fix For: 2.2.1 Click ClassLoader viewer from console, a message pops up showing Error Check the log file, I find the following information for reference. 2010-06-03 16:15:55,078 WARN [BaseCallMarshaller] --Erroring: batchId[1] message[java.util.NoSuchElementException] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
