[jira] [Resolved] (GERONIMO-6292) Share the japser servlet between jasper plugin and web-container plugin.
[ https://issues.apache.org/jira/browse/GERONIMO-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6292. Resolution: Fixed Assignee: Ivan Commit changes to trunk at rev.r1296271 Share the japser servlet between jasper plugin and web-container plugin. Key: GERONIMO-6292 URL: https://issues.apache.org/jira/browse/GERONIMO-6292 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: web Affects Versions: 3.0-beta-1 Reporter: Ivan Assignee: Ivan Fix For: 3.0, 3.0-beta-2 Now, if users would like to turn on jsp debug, they may need to update config.xml in two modules, one is jasper, and another is webcontainer deployer. Think that it is not user-friendly. Think that it is better to have the jsp servlet configuration in the jasper plugin, and webcontainer plugins could share it from there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6266) The jndi prefix URL could not work before the web application is totally started
[ https://issues.apache.org/jira/browse/GERONIMO-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6266. Resolution: Fixed Fix Version/s: 3.0-beta-2 3.0 Assignee: Ivan The jndi prefix URL could not work before the web application is totally started Key: GERONIMO-6266 URL: https://issues.apache.org/jira/browse/GERONIMO-6266 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0, 3.0-beta-1 Reporter: Ivan Assignee: Ivan Fix For: 3.0, 3.0-beta-2 If the those load-on-startup servlets use the servletContext.getResource method to get a jndi prefix URL, they could not get the contents by URL.openStream method, as the resources are only binded to the web application classloader while the TomcatWebApp GBean is started. Although we have binded the resources with the current thread, it seems to be ignored in Tomcat codes. I opened a bug entry in Tomcat community, https://issues.apache.org/bugzilla/show_bug.cgi?id=52563 If they did not accept it or we have no chance to include the change in the 3.0-beta-2 release, there should be workaround codes to make it work in Geronimo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6204) Decouple OpenWebBeans dependency from web containers
[ https://issues.apache.org/jira/browse/GERONIMO-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6204. Resolution: Fixed Fix Version/s: 3.0-beta-2 3.0 Decouple OpenWebBeans dependency from web containers Key: GERONIMO-6204 URL: https://issues.apache.org/jira/browse/GERONIMO-6204 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0-beta-1 Reporter: Ivan Assignee: Ivan Fix For: 3.0, 3.0-beta-2 Attachments: 0003-GERONIMO-6204-Decouple-OpenWebBeans-from-web-contain.patch Now, even for a simple web application, Geronimo also creates a webbeans context, and it really affect the performance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6194) Sort gbeans while stopping the configuration
[ https://issues.apache.org/jira/browse/GERONIMO-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6194. Resolution: Fixed Fix Version/s: 3.0-beta-2 Sort gbeans while stopping the configuration Key: GERONIMO-6194 URL: https://issues.apache.org/jira/browse/GERONIMO-6194 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: kernel Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0, 3.0-beta-2 Usually, the order of the gbeans in the configuration is not an issue while starting the gbeans, as there will be listeners added for the gbean if its required dependencies are not started, and it will be retried in the later. But while stopping the gbeans, the order is important, e.g. if gbean A is dependent on gbean b, and b is stopped before a, then there will an exception thrown from GBeanDependency, and the doFail method will be invoked, not the the doStop method. Although doStop and doFail have the same logic in most of gbeans, it is better to avoid this. I am planning to sort the gbeans by their dependency relations in one configuration while stopping the configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6169) Recursive lookup while the default comp entry is configured
[ https://issues.apache.org/jira/browse/GERONIMO-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6169. Resolution: Fixed Think that this should be fixed now. Recursive lookup while the default comp entry is configured --- Key: GERONIMO-6169 URL: https://issues.apache.org/jira/browse/GERONIMO-6169 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0 If there is an resource entry like java:comp/EJBContext configured in the DD or added by other modules, and the responsible module has not processed it, AdminObjectRefBuilder will add a JndiReference in the binding map, which will cause the infinite lookup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6180) Persistence ref info should not processed by EJBBuilder
[ https://issues.apache.org/jira/browse/GERONIMO-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6180. Resolution: Fixed Fix Version/s: 3.0-beta-2 Think that this should be fixed. Persistence ref info should not processed by EJBBuilder --- Key: GERONIMO-6180 URL: https://issues.apache.org/jira/browse/GERONIMO-6180 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 3.0-M1 Reporter: Ivan Assignee: Ivan Fix For: 3.0, 3.0-beta-2 For those persistence reference information in the spec DD, they should not be processed by EJB builder, as they will be handled by JPA builder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-4379) Default to get from JVM's JAAS Configuration if it is not found in Geronimo's own implementation
[ https://issues.apache.org/jira/browse/GERONIMO-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4379. Resolution: Won't Fix Seem that there is no scenario to require this function. Default to get from JVM's JAAS Configuration if it is not found in Geronimo's own implementation - Key: GERONIMO-4379 URL: https://issues.apache.org/jira/browse/GERONIMO-4379 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 2.2 Environment: JDK 1.5/Windows XP Reporter: Ivan Priority: Minor Fix For: Wish List Attachments: Geronimo-4379.patch While configuring the JAAS Login in the Geronimo, I just found that we use GeronimoLoginConfiguration to replace the JVM's ConfigurationFile, shall we give an opportunity to let the user to get the config from JVM's Configuration. For example, first, we could check from Gronimo's setting, if null is returned, we could invoke oldConguration.getAppConfigurationEntry(name). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6283) Duplicate contextID regiestered!
[ https://issues.apache.org/jira/browse/GERONIMO-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6283. Resolution: Fixed Fix Version/s: 3.0-beta-2 Commit changes to trunk at rev.1292668 and 3.0-beta2 branch at rev.1292669 Duplicate contextID regiestered! Key: GERONIMO-6283 URL: https://issues.apache.org/jira/browse/GERONIMO-6283 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0-beta-1 Reporter: xiezhi Labels: axis,builder,context Fix For: 3.0-beta-2 Original Estimate: 12h Remaining Estimate: 12h Recurring steps refer to GERONIMO-6225, deploy it to G server, you will see an exception in server.log. 2012-02-21 10:41:08,115 ERROR [EjbModuleBuilder] AxisModuleBuilderExtension.initContext() failed: Duplicate contextID registered! ejee/DonateEAR/1.0/car?EJBModule=DonateEJB.jar,J2EEApplication=ejee/DonateEAR/1.0/car,j2eeType=StatelessSessionBean,name=DonateBean org.apache.geronimo.common.DeploymentException: Duplicate contextID registered! ejee/DonateEAR/1.0/car?EJBModule=DonateEJB.jar,J2EEApplication=ejee/DonateEAR/1.0/car,j2eeType=StatelessSessionBean,name=DonateBean at org.apache.geronimo.j2ee.deployment.EARContext.addSecurityContext(EARContext.java:182) at org.apache.geronimo.axis.builder.AxisModuleBuilderExtension.initContext(AxisModuleBuilderExtension.java:178) at org.apache.geronimo.openejb.deployment.EjbModuleBuilder.doInitContext(EjbModuleBuilder.java:835) at org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext(EjbModuleBuilder.java:758) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:686) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) 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:883) 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6256) SortUtils does not behavior correctly while both after/before others and before/after are configured
[ https://issues.apache.org/jira/browse/GERONIMO-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6256. Resolution: Invalid I made a mistaken, seems that the codes work well on this scenario. SortUtils does not behavior correctly while both after/before others and before/after are configured Key: GERONIMO-6256 URL: https://issues.apache.org/jira/browse/GERONIMO-6256 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: web Affects Versions: 3.0-beta-1 Reporter: Ivan Assignee: Ivan Fix For: 3.0, 3.0-beta-2 SortUtils does not behavior correctly while both after/before others and before/after are configured -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5839) Workaround for WSDL path in EAR package
[ https://issues.apache.org/jira/browse/GERONIMO-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-5839. Resolution: Fixed Fix Version/s: (was: 3.0) 3.0-beta-1 Workaround for WSDL path in EAR package --- Key: GERONIMO-5839 URL: https://issues.apache.org/jira/browse/GERONIMO-5839 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment, webservices Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0-beta-1 Due to one single bundle is used for EAR package, and all the sub web applications share the same classloader, all the WSDL paths are required to add the web module name prefix. Use this JIRA to track all the workaround changes, so we could easily revert the changes in case multiple bundles for EAR are supported in the future. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6228) Jar resource and getRealPath cache should not be cleaned while uninstalling embedded WAB in EBA
[ https://issues.apache.org/jira/browse/GERONIMO-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6228. Resolution: Fixed Fix Version/s: 3.0 Assignee: Ivan Jar resource and getRealPath cache should not be cleaned while uninstalling embedded WAB in EBA --- Key: GERONIMO-6228 URL: https://issues.apache.org/jira/browse/GERONIMO-6228 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0-beta-1 Reporter: Ivan Assignee: Ivan Fix For: 3.0, 3.0-beta-2 Jar resource and getRealPath cache should not be cleaned while uninstalling embedded WAB in EBA, those cache directories should be cleaned up while uninstalling the EBA. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
