[jira] [Commented] (GERONIMO-6352) session configuration info is not serialized correctly
[ https://issues.apache.org/jira/browse/GERONIMO-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277656#comment-13277656 ] Ivan commented on GERONIMO-6352: Commit changes to trunk at rev.1339513 > session configuration info is not serialized correctly > -- > > Key: GERONIMO-6352 > URL: https://issues.apache.org/jira/browse/GERONIMO-6352 > 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 > > > While creating the WebAppInfo, those information from session config in the > web.xml is not serialized correctly, so those configurations will never take > effect. -- 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-6352) session configuration info is not serialized correctly
[ https://issues.apache.org/jira/browse/GERONIMO-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6352. Resolution: Fixed Fix Version/s: 3.0 > session configuration info is not serialized correctly > -- > > Key: GERONIMO-6352 > URL: https://issues.apache.org/jira/browse/GERONIMO-6352 > 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 > > > While creating the WebAppInfo, those information from session config in the > web.xml is not serialized correctly, so those configurations will never take > effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6353) Add "DynamicImport-Package: *" when using install-bundle command to transform a jar into a bundle
Forrest Xia created GERONIMO-6353: - Summary: Add "DynamicImport-Package: *" when using install-bundle command to transform a jar into a bundle Key: GERONIMO-6353 URL: https://issues.apache.org/jira/browse/GERONIMO-6353 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0-beta-1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Fix For: 3.0 Think this scenario: User has a custom Tomcat Valve class to be defined via server.xml, first he generated a jar from an IDE, then use install-bundle command to install into the server, then the user defines the valve in the server.xml to use. This scenario introduces a cycle dependencies relationship between the user bundle and Tomcat bundles. 1. To resolve the user bundle, the Tomcat bundles need to be resolved first 2. To start Geronimo Tomcat module, the user bundle needs to be resolved first. Currently, the install-bundle command add "resolution:=optional" properties to the installed user bundle, though the user bundle could be started when server boot, but if the there are packages cannot be resolved with "resolution:=optional", those packages won't be resolved anymore. An improvement is to add "DynamicImport-Package: *" header to the generated menifest. -- 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-6353) Add "DynamicImport-Package: *" when using install-bundle command to transform a jar into a bundle
[ https://issues.apache.org/jira/browse/GERONIMO-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6353. --- Resolution: Fixed > Add "DynamicImport-Package: *" when using install-bundle command to transform > a jar into a bundle > - > > Key: GERONIMO-6353 > URL: https://issues.apache.org/jira/browse/GERONIMO-6353 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0, 3.0-beta-1 >Reporter: Forrest Xia >Assignee: Forrest Xia >Priority: Minor > Fix For: 3.0 > > > Think this scenario: > User has a custom Tomcat Valve class to be defined via server.xml, first he > generated a jar from an IDE, then use install-bundle command to install into > the server, then the user defines the valve in the server.xml to use. > This scenario introduces a cycle dependencies relationship between the user > bundle and Tomcat bundles. > 1. To resolve the user bundle, the Tomcat bundles need to be resolved first > 2. To start Geronimo Tomcat module, the user bundle needs to be resolved > first. > Currently, the install-bundle command add "resolution:=optional" properties > to the installed user bundle, though the user bundle could be started when > server boot, but if the there are packages cannot be resolved with > "resolution:=optional", those packages won't be resolved anymore. > An improvement is to add "DynamicImport-Package: *" header to the generated > menifest. -- 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-6349) Follow Axis2 version convention in Geronimo Axis2 bundle
[ https://issues.apache.org/jira/browse/GERONIMO-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-6349. Resolution: Fixed Fix Version/s: 3.0-beta-2 Assignee: Ivan Commit changes to axis2 bundle at rev.1339960 > Follow Axis2 version convention in Geronimo Axis2 bundle > > > Key: GERONIMO-6349 > URL: https://issues.apache.org/jira/browse/GERONIMO-6349 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan >Priority: Minor > Fix For: 3.0-beta-2 > > > 2012-05-14 21:17:24,651 ERROR [ModuleDeployer] The axis2-1.6.1_1.jar module, > which is not valid, caused For input string: "1_1" > org.apache.axis2.deployment.DeploymentException: For input string: "1_1" > at > org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleArchive(ArchiveReader.java:527) > at > org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:77) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:813) > at > org.apache.axis2.deployment.RepositoryListener.loadClassPathModules(RepositoryListener.java:222) > at > org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:71) > at > org.apache.axis2.deployment.RepositoryListener.(RepositoryListener.java:64) > at > org.apache.axis2.deployment.DeploymentEngine.loadFromClassPath(DeploymentEngine.java:175) > at > org.apache.geronimo.axis2.GeronimoConfigurator.getAxisConfiguration(GeronimoConfigurator.java:47) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) > at > org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.createConfigurationContext(Axis2ClientConfigurationFactory.java:104) > at > org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.getConfigurationContext(Axis2ClientConfigurationFactory.java:64) > at > org.apache.geronimo.axis2.client.Axis2ClientConfigurationFactory.getClientConfigurationContext(Axis2ClientConfigurationFactory.java:57) > at > org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:92) > at > org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:79) > at > org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(DescriptionFactory.java:78) > at org.apache.axis2.jaxws.spi.ServiceDelegate.(ServiceDelegate.java:218) > at > org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:83) > at > org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:79) > at javax.xml.ws.Service.(Service.java:35) > at > *** > at > net.sf.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40) > at > org.apache.geronimo.jaxws.client.JAXWSServiceReference.createServiceProxy(JAXWSServiceReference.java:218) > at > org.apache.geronimo.jaxws.client.JAXWSServiceReference.getContent(JAXWSServiceReference.java:153) > at > org.apache.geronimo.axis2.client.Axis2ServiceReference.getContent(Axis2ServiceReference.java:74) > at > org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:116) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) > at > org.apache.geronimo.client.AppClientContainer.main(AppClientContainer.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at > org.apache.geronimo.system.main.CommandLine.doInvokeMainGBean(CommandLine.java:112) > at > org.apache.ger
[jira] [Created] (GERONIMO-6354) web.xml in geronimo server does not work
Saphen Qiu created GERONIMO-6354: Summary: web.xml in geronimo server does not work Key: GERONIMO-6354 URL: https://issues.apache.org/jira/browse/GERONIMO-6354 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Affects Versions: 3.0-beta-1 Reporter: Saphen Qiu web.xml in var\catalina\conf\ does not work in version 3.x, but works in previous version 2.x. Steps: 1. shutdown server 2. modify var\catalina\conf\web.xml and change session-out value to 1 3. start server 4. open admin console and wait for 1min then check if needs log in again. -- 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
