Re: BVal and searchWiredBudles=false
commit At revision: 1161387 Please check if that is what you want. -Rex 2011/8/25 David Blevins > Checked in a potential fix for the bean validation tests that fail with the > following issue: > >java.lang.NullPointerException >at > javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:626) >at > org.apache.bval.jsr303.xml.ValidationParser.getSchema(ValidationParser.java:144) > > Fixed version does no classpath scanning for the schema: > > > https://svn.apache.org/repos/asf/geronimo/bundles/trunk/bval-jsr303/src/main/java/org/apache/bval/jsr303/xml/ValidationParser.java > > I don't think I setup the bundle correctly as it pulls in all the > transitive dependencies, which is definitely not right. If someone can take > a peek, that would be great. > > -David > > -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Updated] (GERONIMO-6122) Support Stateless and Statefull EJB as JAX-RS root resource classes, providers and Application subclasses
[ https://issues.apache.org/jira/browse/GERONIMO-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-6122: --- Fix Version/s: (was: 3.0) > Support Stateless and Statefull EJB as JAX-RS root resource classes, > providers and Application subclasses > - > > Key: GERONIMO-6122 > URL: https://issues.apache.org/jira/browse/GERONIMO-6122 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: viola.lu >Assignee: Ivan >Priority: Minor > Fix For: 3.0.1 > > > From JAX-RS spec 1.1 > In a product that also supports EJB, an implementation MUST support use of > stateless and singleton > session beans as root resource classes, providers and Application subclasses. > JAX-RS annotations > MAY be applied to a bean's local interface or directly to a no-interface > bean. If an Exception- > Mapper for a EJBException or subclass is not included with an application > then exceptions thrown > by an EJB resource class or provider method MUST be treated as EJB > application exceptions: the > embedded cause of the EJBException MUST be unwrapped and processed as > described in section > 3.3.4. > Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless > EJB, so failed to get Uriinfo > Run Restfulorder samples can give more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5096) Integrate Wink JAX-RS implementation into Geronimo.
[ https://issues.apache.org/jira/browse/GERONIMO-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan closed GERONIMO-5096. -- The initial wink integration should be OK now, track those optional functions in other JIRAs > Integrate Wink JAX-RS implementation into Geronimo. > > > Key: GERONIMO-5096 > URL: https://issues.apache.org/jira/browse/GERONIMO-5096 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, webservices >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: Shawn Jiang > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMO-6122) Support Stateless and Statefull EJB as JAX-RS root resource classes, providers and Application subclasses
[ https://issues.apache.org/jira/browse/GERONIMO-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reopened GERONIMO-6122: Assignee: Ivan Use this JIRA to track the optional features. > Support Stateless and Statefull EJB as JAX-RS root resource classes, > providers and Application subclasses > - > > Key: GERONIMO-6122 > URL: https://issues.apache.org/jira/browse/GERONIMO-6122 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: viola.lu >Assignee: Ivan >Priority: Minor > Fix For: 3.0, 3.0.1 > > > From JAX-RS spec 1.1 > In a product that also supports EJB, an implementation MUST support use of > stateless and singleton > session beans as root resource classes, providers and Application subclasses. > JAX-RS annotations > MAY be applied to a bean's local interface or directly to a no-interface > bean. If an Exception- > Mapper for a EJBException or subclass is not included with an application > then exceptions thrown > by an EJB resource class or provider method MUST be treated as EJB > application exceptions: the > embedded cause of the EJBException MUST be unwrapped and processed as > described in section > 3.3.4. > Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless > EJB, so failed to get Uriinfo > Run Restfulorder samples can give more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5096) Integrate Wink JAX-RS implementation into Geronimo.
[ https://issues.apache.org/jira/browse/GERONIMO-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-5096. Resolution: Fixed > Integrate Wink JAX-RS implementation into Geronimo. > > > Key: GERONIMO-5096 > URL: https://issues.apache.org/jira/browse/GERONIMO-5096 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, webservices >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: Shawn Jiang > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6122) Support Stateless and Statefull EJB as JAX-RS root resource classes, providers and Application subclasses
[ https://issues.apache.org/jira/browse/GERONIMO-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-6122. -- Resolution: Duplicate Duplicate with https://issues.apache.org/jira/browse/GERONIMO-5096 > Support Stateless and Statefull EJB as JAX-RS root resource classes, > providers and Application subclasses > - > > Key: GERONIMO-6122 > URL: https://issues.apache.org/jira/browse/GERONIMO-6122 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: viola.lu >Priority: Minor > Fix For: 3.0, 3.0.1 > > > From JAX-RS spec 1.1 > In a product that also supports EJB, an implementation MUST support use of > stateless and singleton > session beans as root resource classes, providers and Application subclasses. > JAX-RS annotations > MAY be applied to a bean's local interface or directly to a no-interface > bean. If an Exception- > Mapper for a EJBException or subclass is not included with an application > then exceptions thrown > by an EJB resource class or provider method MUST be treated as EJB > application exceptions: the > embedded cause of the EJBException MUST be unwrapped and processed as > described in section > 3.3.4. > Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless > EJB, so failed to get Uriinfo > Run Restfulorder samples can give more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
BVal and searchWiredBudles=false
Checked in a potential fix for the bean validation tests that fail with the following issue: java.lang.NullPointerException at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:626) at org.apache.bval.jsr303.xml.ValidationParser.getSchema(ValidationParser.java:144) Fixed version does no classpath scanning for the schema: https://svn.apache.org/repos/asf/geronimo/bundles/trunk/bval-jsr303/src/main/java/org/apache/bval/jsr303/xml/ValidationParser.java I don't think I setup the bundle correctly as it pulls in all the transitive dependencies, which is definitely not right. If someone can take a peek, that would be great. -David
[jira] [Closed] (GERONIMO-5088) Support OSGi as a Geronimo programming model
[ https://issues.apache.org/jira/browse/GERONIMO-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5088. -- Resolution: Fixed has been fixed, so close it. > Support OSGi as a Geronimo programming model > > > Key: GERONIMO-5088 > URL: https://issues.apache.org/jira/browse/GERONIMO-5088 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > This is for enhancements to the Geronimo deployment and management models for > supporting OSGi bundles as application bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Geronimo 3.0-beta Release Status
I just closed most of the Jiras opened by Rick. We still have 100+ opened jiras... Devs, please continue clean your Jiras! -Rex 2011/8/24 Shawn Jiang > Thanks, Rex ! > > tck is in good shape now. I think Most of the JIRAs opened by Rick to > track the Java EE 6 spec impl could be closed now. > > On Wed, Aug 24, 2011 at 5:11 PM, Rex Wang wrote: > >> Hi devs, >> >> I created a page in our wiki to record Geronimo 3.0-beta Release Status: >> >> https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+3.0-beta+Release+Status >> >> Now, we have a lot of OLD Jiras opened, which has been fixed or won't fix, >> so could you please clean your Jira status? You could see the all the >> un-resolved jiras in the #3.1 of the above page. >> >> thanks, >> >> -- >> Lei Wang (Rex) >> rwonly AT apache.org >> > > > > -- > Shawn > -- Lei Wang (Rex) rwonly AT apache.org
[jira] [Closed] (GERONIMO-5941) JSR-299 Policy Available test failure
[ https://issues.apache.org/jira/browse/GERONIMO-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5941. -- Resolution: Fixed has been fixed, so close it. > JSR-299 Policy Available test failure > - > > Key: GERONIMO-5941 > URL: https://issues.apache.org/jira/browse/GERONIMO-5941 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Kevan Miller > Fix For: 3.0 > > > We're getting the following test failure running JSR-299 CTS: > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 43.646 sec > <<< FAILURE! > testEnabledPolicyAvailable(org.jboss.jsr299.tck.tests.policy.enterprise.SessionBeanPolicyTest) > Time elapsed: 1.895 sec <<< FAILURE! > java.lang.AssertionError > at > org.jboss.jsr299.tck.tests.policy.enterprise.SessionBeanPolicyTest.testEnabledPolicyAvailable(SessionBeanPolicyTest.java:41) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5940) JSR-299 PersistenceContextInjectionTests are failing
[
https://issues.apache.org/jira/browse/GERONIMO-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang closed GERONIMO-5940.
--
Resolution: Fixed
has been fixed, so close it.
> JSR-299 PersistenceContextInjectionTests are failing
>
>
> Key: GERONIMO-5940
> URL: https://issues.apache.org/jira/browse/GERONIMO-5940
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 3.0
>Reporter: Kevan Miller
> Fix For: 3.0
>
> Attachments:
> org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest.war
>
>
> The tests:
> {code}
> Failed tests:
>
> testPassivationOfPersistenceContext(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest)
>
> testPassivationOfPersistenceUnit(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest)
>
> testBeanTypesAndBindingTypesOfPersistenceContext(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest)
>
> testInjectionOfPersistenceUnit(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest)
>
> testInjectionOfPersistenceContext(org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest)
> {code}
> are failing because of the following deployment error:
> {code}
> org.apache.geronimo.common.DeploymentException: No default PersistenceUnit
> specified, and none located
> at
> org.apache.geronimo.persistence.builder.PersistenceRefBuilder.findPersistenceUnitQuery(PersistenceRefBuilder.java:215)
> at
> org.apache.geronimo.persistence.builder.PersistenceRefBuilder.buildNaming(PersistenceRefBuilder.java:165)
> at
> org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:70)
> at
> org.apache.geronimo.j2ee.deployment.NamingBuilderCollection.buildNaming(NamingBuilderCollection.java:70)
> at
> org.apache.geronimo.openwebbeans.deployment.OpenWebBeansModuleBuilderExtension.addGBeans(OpenWebBeansModuleBuilderExtension.java:154)
> at
> org.apache.geronimo.jetty8.deployment.JettyModuleBuilder.addGBeans(JettyModuleBuilder.java:538)
> at
> org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174)
> at
> org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:724)
> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:252)
> at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
> at
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
> at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
> at
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245)
> at
> org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
> at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
> at
> javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
>
[jira] [Closed] (GERONIMO-5898) ClassCastException during deployment of some JCDI TCK
[
https://issues.apache.org/jira/browse/GERONIMO-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang closed GERONIMO-5898.
--
Resolution: Fixed
has been fixed, so close it.
> ClassCastException during deployment of some JCDI TCK
> -
>
> Key: GERONIMO-5898
> URL: https://issues.apache.org/jira/browse/GERONIMO-5898
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenWebBeans
>Reporter: Kevan Miller
> Fix For: 3.0
>
>
> Final JCDI TCK issue (I hope). During deployment of some apps, we're getting
> the following exception (this is with an updated
> WebBeansConfigurationListener.java). So, will need to resolve wrt.
> GERONIMO-5896
> Here's the exception we get:
> {code}
> 2011-04-10 20:28:22,185 ERROR [DecoratorInvocationTest]] Exception sending
> context initialized event to listener instance of class
> org.apache.geronimo.openwebbeans.WebBeansConfigurationListener
> java.lang.ClassCastException: javax.servlet.ServletContextEvent cannot be
> cast to org.apache.openejb.cdi.StartupObject
> at
> org.apache.openejb.cdi.OpenEJBLifecycle.startApplication(OpenEJBLifecycle.java:110)
> at
> org.apache.geronimo.openwebbeans.WebBeansConfigurationListener.contextInitialized(WebBeansConfigurationListener.java:86)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4521)
> at
> org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5004)
> at
> org.apache.catalina.core.StandardContext$1.call(StandardContext.java:4999)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> {code}
> This appears to be the cause of the remaining test failures. So, this might
> be the final fix needed to clear up the JSR-299 tests...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5896) ContextNotActiveException running JCDI TCK
[
https://issues.apache.org/jira/browse/GERONIMO-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang closed GERONIMO-5896.
--
Resolution: Fixed
has been fixed, so close it.
> ContextNotActiveException running JCDI TCK
> --
>
> Key: GERONIMO-5896
> URL: https://issues.apache.org/jira/browse/GERONIMO-5896
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenWebBeans
>Reporter: Kevan Miller
> Fix For: 3.0
>
> Attachments: owb-lifecycle.patch
>
>
> Running the JCDI tck can result in some exceptions like the following:
> {code}
> 2011-04-09 23:53:45,964 ERROR [ApplicationContextTest]] Exception sending
> context initialized event to listener instance of class
> org.jboss.jsr299.tck.test\
> s.context.application.TestServletContextListener
> javax.enterprise.context.ContextNotActiveException: WebBeans context with
> scope type annotation @ApplicationScoped does not exist within current thread
> at
> org.apache.webbeans.container.BeanManagerImpl.getContext(BeanManagerImpl.java:341)
> at
> org.apache.webbeans.container.InjectableBeanManager.getContext(InjectableBeanManager.java:115)
> at
> org.jboss.jsr299.tck.tests.context.application.TestServletContextListener.contextInitialized(TestServletContextListener.java:38)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4521)
> at
> org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5004)
> at
> org.apache.catalina.core.StandardContext$1.call(StandardContext.java:4999)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> 2011-04-09 23:53:45,965 ERROR [StandardContext] Error listenerStart
> {code}
> This is because the OpenWebBeans application initialization is not being
> driven. Geronimo's WebBeansConfigurationListener
> (plugins/openwebbeans/geronimo-openwebbeans/src/main/java/org/apache/geronimo/openwebbeans/WebBeansConfigurationListener.java)
> is (has become?) somewhat different from OpenWebBeans
> WebBeansConfigurationListener). Namely, in
> contextInitialized(ServletConextEvent) we don't have:
> {code}
>this.lifeCycle.startApplication(event);
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5436) ClassCastException in Deployer
[ https://issues.apache.org/jira/browse/GERONIMO-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5436. -- Resolution: Fixed has been fixed, so close it. > ClassCastException in Deployer > -- > > Key: GERONIMO-5436 > URL: https://issues.apache.org/jira/browse/GERONIMO-5436 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 >Reporter: Mark Struberg >Assignee: David Jencks > Fix For: 3.0 > > Attachments: GERONIMO-5436.patch > > > While deploying a EAR I get a ClassCastException in MergeHelper#347 > webFragment = (WebFragment) xmlObject; > but xmlObject is actually of type > org.apache.xmlbeans.impl.values.XmlAnyTypeImpl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5212) Do we need Karaf when starting Geronimo?
[ https://issues.apache.org/jira/browse/GERONIMO-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5212. -- Resolution: Won't Fix > Do we need Karaf when starting Geronimo? > > > Key: GERONIMO-5212 > URL: https://issues.apache.org/jira/browse/GERONIMO-5212 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Kevan Miller > Fix For: 3.0 > > > Starting up Karaf seems to consume a fair amount of time as a Geronimo server > is started. Is it needed? I think we should consider slimming down the server > startup. I'm not sure what it's buying us, at the moment... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5775) JCDI tck failures
[ https://issues.apache.org/jira/browse/GERONIMO-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5775. -- Resolution: Fixed has been fixed, so close it. > JCDI tck failures > - > > Key: GERONIMO-5775 > URL: https://issues.apache.org/jira/browse/GERONIMO-5775 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > Attachments: jcdi.zip > > > We're still getting some JCDI failures while running the TCK. Since we don't > have a official TCK run from the test machines because of some other > problems, I'm attaching the results of a local run on my machine on this > Jira. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5135) Blueprint and gbeans need synchronization
[ https://issues.apache.org/jira/browse/GERONIMO-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5135. -- Resolution: Fixed has been fixed, so close it. > Blueprint and gbeans need synchronization > - > > Key: GERONIMO-5135 > URL: https://issues.apache.org/jira/browse/GERONIMO-5135 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 3.0 > > > Geronimo plugins start synchronously in the starting thread whereas blueprint > plans start asynchronously. This can lead to a situation where a gbean that > depends on a blueprint bean having started gets started before the blueprint > plan is processed or the blueprint bean started. > A simple way to deal with this is with a WaitForBlueprint gbean that > registers as a BlueprintListener and blocks until it receives notification > that the blueprint stuff either started ok or failed to start. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090733#comment-13090733 ] Yi Xiao commented on GERONIMODEVTOOLS-759: -- I find some other cases will lead to publish errors, I will consider it more carefully and provide a new patch. > Using the new APIs to manage the bundles status both in GEP and Server side > > > Key: GERONIMODEVTOOLS-759 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6, > Eclipse3.6SR1&SR2 >Reporter: Yi Xiao >Assignee: Jarek Gawor > Labels: OSGI, bundle > Fix For: 3.0 > > Attachments: OSGIBundleDeploy.patch, > OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch, > OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch > > > This improvement depends on the server's modules, so, if the server side does > not update timely, it may cause the GEP compile failure! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6122) Support Stateless and Statefull EJB as JAX-RS root resource classes, providers and Application subclasses
[ https://issues.apache.org/jira/browse/GERONIMO-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090732#comment-13090732 ] Rex Wang commented on GERONIMO-6122: I think this is duplicate with GERONIMO-5096? > Support Stateless and Statefull EJB as JAX-RS root resource classes, > providers and Application subclasses > - > > Key: GERONIMO-6122 > URL: https://issues.apache.org/jira/browse/GERONIMO-6122 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: viola.lu >Priority: Minor > Fix For: 3.0, 3.0.1 > > > From JAX-RS spec 1.1 > In a product that also supports EJB, an implementation MUST support use of > stateless and singleton > session beans as root resource classes, providers and Application subclasses. > JAX-RS annotations > MAY be applied to a bean's local interface or directly to a no-interface > bean. If an Exception- > Mapper for a EJBException or subclass is not included with an application > then exceptions thrown > by an EJB resource class or provider method MUST be treated as EJB > application exceptions: the > embedded cause of the EJBException MUST be unwrapped and processed as > described in section > 3.3.4. > Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless > EJB, so failed to get Uriinfo > Run Restfulorder samples can give more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6122) Support Stateless and Statefull EJB as JAX-RS root resource classes, providers and Application subclasses
[ https://issues.apache.org/jira/browse/GERONIMO-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu updated GERONIMO-6122: --- Description: >From JAX-RS spec 1.1 In a product that also supports EJB, an implementation MUST support use of stateless and singleton session beans as root resource classes, providers and Application subclasses. JAX-RS annotations MAY be applied to a bean's local interface or directly to a no-interface bean. If an Exception- Mapper for a EJBException or subclass is not included with an application then exceptions thrown by an EJB resource class or provider method MUST be treated as EJB application exceptions: the embedded cause of the EJBException MUST be unwrapped and processed as described in section 3.3.4. Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless EJB, so failed to get Uriinfo Run Restfulorder samples can give more details. was: >From JAX-WS spec 1.1 In a product that also supports EJB, an implementation MUST support use of stateless and singleton session beans as root resource classes, providers and Application subclasses. JAX-RS annotations MAY be applied to a bean's local interface or directly to a no-interface bean. If an Exception- Mapper for a EJBException or subclass is not included with an application then exceptions thrown by an EJB resource class or provider method MUST be treated as EJB application exceptions: the embedded cause of the EJBException MUST be unwrapped and processed as described in section 3.3.4. Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless EJB, so failed to get Uriinfo Run Restfulorder samples can give more details. Summary: Support Stateless and Statefull EJB as JAX-RS root resource classes, providers and Application subclasses (was: Support Stateless and Statefull EJB as JAX-WS root resource classes, providers and Application subclasses) > Support Stateless and Statefull EJB as JAX-RS root resource classes, > providers and Application subclasses > - > > Key: GERONIMO-6122 > URL: https://issues.apache.org/jira/browse/GERONIMO-6122 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: viola.lu >Priority: Minor > Fix For: 3.0, 3.0.1 > > > From JAX-RS spec 1.1 > In a product that also supports EJB, an implementation MUST support use of > stateless and singleton > session beans as root resource classes, providers and Application subclasses. > JAX-RS annotations > MAY be applied to a bean's local interface or directly to a no-interface > bean. If an Exception- > Mapper for a EJBException or subclass is not included with an application > then exceptions thrown > by an EJB resource class or provider method MUST be treated as EJB > application exceptions: the > embedded cause of the EJBException MUST be unwrapped and processed as > described in section > 3.3.4. > Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless > EJB, so failed to get Uriinfo > Run Restfulorder samples can give more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6122) Support Stateless and Statefull EJB as JAX-WS root resource classes, providers and Application subclasses
Support Stateless and Statefull EJB as JAX-WS root resource classes, providers and Application subclasses - Key: GERONIMO-6122 URL: https://issues.apache.org/jira/browse/GERONIMO-6122 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: javaee6 Affects Versions: 3.0 Reporter: viola.lu Priority: Minor Fix For: 3.0, 3.0.1 >From JAX-WS spec 1.1 In a product that also supports EJB, an implementation MUST support use of stateless and singleton session beans as root resource classes, providers and Application subclasses. JAX-RS annotations MAY be applied to a bean's local interface or directly to a no-interface bean. If an Exception- Mapper for a EJBException or subclass is not included with an application then exceptions thrown by an EJB resource class or provider method MUST be treated as EJB application exceptions: the embedded cause of the EJBException MUST be unwrapped and processed as described in section 3.3.4. Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless EJB, so failed to get Uriinfo Run Restfulorder samples can give more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6028) Nothing prompted when hotdeploy a re-named eba application
[ https://issues.apache.org/jira/browse/GERONIMO-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li closed GERONIMO-6028. - Verified on Aug 23's build. > Nothing prompted when hotdeploy a re-named eba application > -- > > Key: GERONIMO-6028 > URL: https://issues.apache.org/jira/browse/GERONIMO-6028 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment, osgi >Affects Versions: 3.0 > Environment: OS:win2008r2x64 > JDK:IBM jdk Java60 SR9 FP1 >Reporter: Tina Li >Assignee: Rex Wang > Fix For: 3.0 > > Attachments: geronimo.log > > > 1.Hotdeploy eba application:blueprint-eba-3.0-SNAPSHOT.eba successfully > 2.Rename blueprint-eba-3.0-SNAPSHOT.eba to blueprint-eba1-3.0-SNAPSHOT.eba > 3.Hotdeploy blueprint-eba1-3.0-SNAPSHOT.eba without uninstall > blueprint-eba-3.0-SNAPSHOT.eba > 4.Found nothing changed.But according to GERONIMO-5832 of Rex's comments: > "hot deploy a XXX.eba and then put in a XXX2.eba, (the XXX2.bea is made by > rename the XXX.bea) This scenario supposes to redeploy the eba with the same > config id, and after the XXX2.eba's deployment, the XXX.eba should be > deleted." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5173) activation spec unit tests fail when compiled with java 6.
[ https://issues.apache.org/jira/browse/GERONIMO-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5173. -- Resolution: Fixed has been resolved. close it. > activation spec unit tests fail when compiled with java 6. > --- > > Key: GERONIMO-5173 > URL: https://issues.apache.org/jira/browse/GERONIMO-5173 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > The JAF classes are included in the Java 6 JDK, which means that they are > getting picked up during the testing phase of the geronimo-activation spec > jar. It appears there are some bugs in the JAF RI, which is causing some > unit test failures. These tests really need to be run with the > geronimo-activation jar file in the endorsed dirs path so it can override the > JDK native one. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090725#comment-13090725 ] Han Hong Fang commented on GERONIMODEVTOOLS-764: Good catch! Thanks Jarek. > Control the OSGI bundle's start level in GEP > > > Key: GERONIMODEVTOOLS-764 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6, > Eclipse3.6SR1&SR2 >Reporter: Yi Xiao >Assignee: Yi Xiao > Labels: OSGI, startLevel > Fix For: 3.0 > > Attachments: controlBundleStartLevel_764.patch, > controlBundleStartLevel_764_1.patch, defaultStartLevel.jpg, > singleStartLevel.jpg > > > 1 Provide a UI interface to control all the bundles' start level > 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5080) Contexts and Dependency Injection 1.0 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5080. -- Resolution: Fixed has been resolved. close it. > Contexts and Dependency Injection 1.0 enhancements > -- > > Key: GERONIMO-5080 > URL: https://issues.apache.org/jira/browse/GERONIMO-5080 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Add support for the CDI 1.0 specification (JSR 299) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5061) Servlet 3.0 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5061. -- Resolution: Fixed has been resolved. close it. > Servlet 3.0 enhancements > > > Key: GERONIMO-5061 > URL: https://issues.apache.org/jira/browse/GERONIMO-5061 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade Geronimo to support the servlet 3.0 (JSR 315) specification. This > item includes both Tomcat and Jetty subtasks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-4952) Figure out how to use User Admin service in Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-4952. -- Resolution: Won't Fix We won't use this way. so close it > Figure out how to use User Admin service in Geronimo 3.0 > > > Key: GERONIMO-4952 > URL: https://issues.apache.org/jira/browse/GERONIMO-4952 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi, security >Affects Versions: 3.0 >Reporter: Ivan > Fix For: 3.0 > > Attachments: GERONIMO-4952.patch > > > In OSGI world, User Admin service is used for authentication and > authorization, while in classic Java environment, JACC is used, should figure > out how we could use it in new Geronimo 3.0. From my view, for > authentication, we might define a login module which delegates to user admin > service. For authorization, did not have clear idea now, -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-5245) Version property variables should be used for all configuration versions in the framework startup.properties file.
[ https://issues.apache.org/jira/browse/GERONIMO-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang reassigned GERONIMO-5245: -- Assignee: Rex Wang > Version property variables should be used for all configuration versions in > the framework startup.properties file. > --- > > Key: GERONIMO-5245 > URL: https://issues.apache.org/jira/browse/GERONIMO-5245 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: Rex Wang > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5245) Version property variables should be used for all configuration versions in the framework startup.properties file.
[ https://issues.apache.org/jira/browse/GERONIMO-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-5245: --- Affects Version/s: 3.0 Fix Version/s: 3.0 > Version property variables should be used for all configuration versions in > the framework startup.properties file. > --- > > Key: GERONIMO-5245 > URL: https://issues.apache.org/jira/browse/GERONIMO-5245 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: Rex Wang > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5085) CORBA/Yoko OSGi enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5085. -- Resolution: Fixed has been resolved. close it. > CORBA/Yoko OSGi enhancements > > > Key: GERONIMO-5085 > URL: https://issues.apache.org/jira/browse/GERONIMO-5085 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, osgi >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Get CORBA/Yoko working in an OSGi environment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5082) JAX-WS 2.2 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5082. -- Resolution: Fixed has been resolved. close it. > JAX-WS 2.2 enhancements > --- > > Key: GERONIMO-5082 > URL: https://issues.apache.org/jira/browse/GERONIMO-5082 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Additions for the JAX-WS 2.2 enhancements. This includes work for both Axis2 > and CXF imtegration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5103) Upgrade to JAX-WS compliant Axis2 implementation.
[ https://issues.apache.org/jira/browse/GERONIMO-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5103. -- Resolution: Fixed Fix Version/s: 3.0 has been resolved. close it. > Upgrade to JAX-WS compliant Axis2 implementation. > -- > > Key: GERONIMO-5103 > URL: https://issues.apache.org/jira/browse/GERONIMO-5103 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Rick McGuire > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5081) Web Services for EE 1.3-MR2 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5081. -- Resolution: Fixed has been resolved. close it. > Web Services for EE 1.3-MR2 enhancements > > > Key: GERONIMO-5081 > URL: https://issues.apache.org/jira/browse/GERONIMO-5081 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Implement the enhancements in the WSEE 1.3-MR2 released (JSR 109) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5219) Java EE Injection annotation scanning for 299 beans
[ https://issues.apache.org/jira/browse/GERONIMO-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5219. -- Resolution: Fixed Fix Version/s: 3.0 has been resolved. close it. > Java EE Injection annotation scanning for 299 beans > --- > > Key: GERONIMO-5219 > URL: https://issues.apache.org/jira/browse/GERONIMO-5219 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Shawn Jiang > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5225) Implement Bean Manager References (Java EE 6 spec section EE.5.19)
[ https://issues.apache.org/jira/browse/GERONIMO-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5225. -- Resolution: Fixed Fix Version/s: 3.0 has been resolved. close it. > Implement Bean Manager References (Java EE 6 spec section EE.5.19) > -- > > Key: GERONIMO-5225 > URL: https://issues.apache.org/jira/browse/GERONIMO-5225 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Rick McGuire > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5078) Managed Bean 1.0 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5078. -- Resolution: Fixed has been resolved. close it. > Managed Bean 1.0 enhancements > - > > Key: GERONIMO-5078 > URL: https://issues.apache.org/jira/browse/GERONIMO-5078 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Add support for Managed Beans 1.0 (JSR 318) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5079) Dependency Injection 1.0 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5079. -- Resolution: Fixed has been resolved. close it. > Dependency Injection 1.0 enhancements > - > > Key: GERONIMO-5079 > URL: https://issues.apache.org/jira/browse/GERONIMO-5079 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Add support for the DI 1.0 specification (JSR 330) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5115) Integrate ManagedBean support with the JSF implementation.
[ https://issues.apache.org/jira/browse/GERONIMO-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5115. -- Resolution: Fixed has been resolved. close it. > Integrate ManagedBean support with the JSF implementation. > --- > > Key: GERONIMO-5115 > URL: https://issues.apache.org/jira/browse/GERONIMO-5115 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, myfaces, OpenWebBeans >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5076) Interceptor 1.1 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5076. -- Resolution: Fixed has been resolved. close it. > Interceptor 1.1 enhancements > > > Key: GERONIMO-5076 > URL: https://issues.apache.org/jira/browse/GERONIMO-5076 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade to the Interceptor 1.1 specification level (JSR 318) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5140) Build EJB 3.1 Lite plugin
[ https://issues.apache.org/jira/browse/GERONIMO-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5140. -- Resolution: Fixed has been resolved. close it. > Build EJB 3.1 Lite plugin > - > > Key: GERONIMO-5140 > URL: https://issues.apache.org/jira/browse/GERONIMO-5140 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > A plugin that supports just the features of the EJB 3.1 Lite profile needs to > be added to Geronimo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5119) Allow more granular selection of configured EJB features.
[ https://issues.apache.org/jira/browse/GERONIMO-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5119. -- Resolution: Fixed has been resolved. close it. > Allow more granular selection of configured EJB features. > -- > > Key: GERONIMO-5119 > URL: https://issues.apache.org/jira/browse/GERONIMO-5119 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, OpenEJB >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > The EJB Lite configuration needed by the Web Profile can be more easily > implemented if the OpenEJB support is split into individually selectable > profiles that can then be assembled into a Lite and Full versions. This > would also allow custom assemblies to specify which EJB features they require > rather than the previous all-or-nothing approach used in prior released. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5074) EJB 3.1 Lite enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5074. -- Resolution: Fixed has been resolved. close it. > EJB 3.1 Lite enhancements > - > > Key: GERONIMO-5074 > URL: https://issues.apache.org/jira/browse/GERONIMO-5074 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, OpenEJB, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Add a plugin version for the EJB 3.1 Lite specification level that can be > used for the web profile assembly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5073) EJB 3.1 Enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5073. -- Resolution: Fixed has been resolved. close it. > EJB 3.1 Enhancements > > > Key: GERONIMO-5073 > URL: https://issues.apache.org/jira/browse/GERONIMO-5073 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, OpenEJB >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade to the EJB 3.1 specification level (JSR 3.1.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5120) Integrate new EJB features into geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5120. -- Resolution: Fixed > Integrate new EJB features into geronimo > > > Key: GERONIMO-5120 > URL: https://issues.apache.org/jira/browse/GERONIMO-5120 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, OpenEJB >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5120) Integrate new EJB features into geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090699#comment-13090699 ] Rex Wang commented on GERONIMO-5120: has been resolved. close it. > Integrate new EJB features into geronimo > > > Key: GERONIMO-5120 > URL: https://issues.apache.org/jira/browse/GERONIMO-5120 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, OpenEJB >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5072) Common Annotations 1.1 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5072. -- Resolution: Fixed has been resolved. close it. > Common Annotations 1.1 enhancements > --- > > Key: GERONIMO-5072 > URL: https://issues.apache.org/jira/browse/GERONIMO-5072 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade to the Common Annotations 1.1 level (JSR 250) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5071) JASPIC 1.0 Enhancement
[ https://issues.apache.org/jira/browse/GERONIMO-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5071. -- Resolution: Fixed has been resolved. close it. > JASPIC 1.0 Enhancement > --- > > Key: GERONIMO-5071 > URL: https://issues.apache.org/jira/browse/GERONIMO-5071 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Implement JASPIC 1.0 (JSR 196) for Geronimo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5069) Java Connector Architecture 1.6 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5069. -- Resolution: Fixed has been resolved. close it. > Java Connector Architecture 1.6 enhancements > > > Key: GERONIMO-5069 > URL: https://issues.apache.org/jira/browse/GERONIMO-5069 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: David Jencks > Fix For: 3.0 > > > Upgrade to JCA 1.6 (JSR 322) specification level. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5070) JACC 1.4 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5070. -- Resolution: Fixed has been resolved. close it. > JACC 1.4 enhancements > - > > Key: GERONIMO-5070 > URL: https://issues.apache.org/jira/browse/GERONIMO-5070 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade to JACC 1.4 (JSR 115) specification level. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5068) JPA 2.0 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5068. -- Resolution: Fixed has been resolved. close it. > JPA 2.0 enhancements > > > Key: GERONIMO-5068 > URL: https://issues.apache.org/jira/browse/GERONIMO-5068 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade the persistence support to JPA 2.0 (JSR 317) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5025) New module/app/global jndi contexts in javaee 6 spec
[ https://issues.apache.org/jira/browse/GERONIMO-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5025. -- Resolution: Fixed has been resolved. close it. > New module/app/global jndi contexts in javaee 6 spec > > > Key: GERONIMO-5025 > URL: https://issues.apache.org/jira/browse/GERONIMO-5025 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: deployment, naming >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 3.0 > > > Javaee platform spec describes some new jndi java: contexts that are more > shared between components. > java:comp (existing) > java:module > java:app > java:global > My first idea for implementing this: > 1. in RootContext, have the thread local represent java: rather than > java:comp. So all the namespaces will be in the Context object. > 2. Construct this Context by federating objects for each scope. We'll have > to maintain a global context somewhere. The others can presumably be > constructed during deployment and set up in the existing gbeans for the app > components. > 3. Modify the naming builders to put stuff into the right namespace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5064) Java Server Faces 2.0 enhancement
[ https://issues.apache.org/jira/browse/GERONIMO-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5064. -- Resolution: Fixed has been resolved. close it. > Java Server Faces 2.0 enhancement > - > > Key: GERONIMO-5064 > URL: https://issues.apache.org/jira/browse/GERONIMO-5064 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade the Geronimo JSF level to 2.0 (JSR 314) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5066) Java EE 6 Global JNDI enhancments
[ https://issues.apache.org/jira/browse/GERONIMO-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5066. -- Resolution: Fixed has been resolved. close it. > Java EE 6 Global JNDI enhancments > - > > Key: GERONIMO-5066 > URL: https://issues.apache.org/jira/browse/GERONIMO-5066 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: David Jencks > Fix For: 3.0 > > > Enhancements for the java ee 6 global JNDI additions specified by JSR 316, -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5062) JSP 2.2 Enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5062. -- Resolution: Fixed has been resolved. close it. > JSP 2.2 Enhancements > > > Key: GERONIMO-5062 > URL: https://issues.apache.org/jira/browse/GERONIMO-5062 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade Geronimo to support JSP 2.2 (JSR 245) for both Tomcat and Jetty web > containers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5063) Expression Language 2.2 enhancements
[ https://issues.apache.org/jira/browse/GERONIMO-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5063. -- Resolution: Fixed has been resolved. close it. > Expression Language 2.2 enhancements > > > Key: GERONIMO-5063 > URL: https://issues.apache.org/jira/browse/GERONIMO-5063 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Upgrade to expression language 2.2 (JSR 245) for both Tomcat and Jetty. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5049) Add bean validation (JSR 303) to Geronimo 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5049. -- Resolution: Fixed has been resolved. close it. > Add bean validation (JSR 303) to Geronimo 3.0 > - > > Key: GERONIMO-5049 > URL: https://issues.apache.org/jira/browse/GERONIMO-5049 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5050) Integrate OpenWebBeans into Geronimo 3.0.
[ https://issues.apache.org/jira/browse/GERONIMO-5050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5050. -- Resolution: Fixed has been resolved. close it. > Integrate OpenWebBeans into Geronimo 3.0. > -- > > Key: GERONIMO-5050 > URL: https://issues.apache.org/jira/browse/GERONIMO-5050 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: javaee6, OpenWebBeans >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: David Jencks > Fix For: 3.0 > > Attachments: openwebbeans.patch > > > A JSR 299 and 330 implementation is required for Java EE6 and the Java EE 6 > web profile. OpenWebBeans is the most feasible candidate for providing these > features. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5048) Create an EJB Lite plugin for 3.0 Web Profile usage.
[ https://issues.apache.org/jira/browse/GERONIMO-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5048. -- > Create an EJB Lite plugin for 3.0 Web Profile usage. > - > > Key: GERONIMO-5048 > URL: https://issues.apache.org/jira/browse/GERONIMO-5048 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: javaee6, OpenEJB >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Currently, the Geronimo OpenEJB plugin is an "all or nothing" configuration > that brings in all of OpenEJB. There should also be a plugin that only pulls > in the features required for the Java EE6 web profile. It might also be nice > if additional EJB features could be added to the profile via custom > assemblies, but that might require a larger refactoring of the openejb > plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5004) axis 1 osgi integration
[ https://issues.apache.org/jira/browse/GERONIMO-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-5004. Resolution: Fixed > axis 1 osgi integration > --- > > Key: GERONIMO-5004 > URL: https://issues.apache.org/jira/browse/GERONIMO-5004 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 3.0 > > > get the axis 1 plugin working. > This requires scout and juddi. Scout looks OK, Juddi needs to apply patch > for JUDD-299. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5048) Create an EJB Lite plugin for 3.0 Web Profile usage.
[ https://issues.apache.org/jira/browse/GERONIMO-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090682#comment-13090682 ] Rex Wang commented on GERONIMO-5048: has been resolved. close it. > Create an EJB Lite plugin for 3.0 Web Profile usage. > - > > Key: GERONIMO-5048 > URL: https://issues.apache.org/jira/browse/GERONIMO-5048 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: javaee6, OpenEJB >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Currently, the Geronimo OpenEJB plugin is an "all or nothing" configuration > that brings in all of OpenEJB. There should also be a plugin that only pulls > in the features required for the Java EE6 web profile. It might also be nice > if additional EJB features could be added to the profile via custom > assemblies, but that might require a larger refactoring of the openejb > plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5004) axis 1 osgi integration
[ https://issues.apache.org/jira/browse/GERONIMO-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5004. -- > axis 1 osgi integration > --- > > Key: GERONIMO-5004 > URL: https://issues.apache.org/jira/browse/GERONIMO-5004 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 3.0 > > > get the axis 1 plugin working. > This requires scout and juddi. Scout looks OK, Juddi needs to apply patch > for JUDD-299. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5048) Create an EJB Lite plugin for 3.0 Web Profile usage.
[ https://issues.apache.org/jira/browse/GERONIMO-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-5048. Resolution: Fixed > Create an EJB Lite plugin for 3.0 Web Profile usage. > - > > Key: GERONIMO-5048 > URL: https://issues.apache.org/jira/browse/GERONIMO-5048 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: javaee6, OpenEJB >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Currently, the Geronimo OpenEJB plugin is an "all or nothing" configuration > that brings in all of OpenEJB. There should also be a plugin that only pulls > in the features required for the Java EE6 web profile. It might also be nice > if additional EJB features could be added to the profile via custom > assemblies, but that might require a larger refactoring of the openejb > plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5004) axis 1 osgi integration
[ https://issues.apache.org/jira/browse/GERONIMO-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090681#comment-13090681 ] Rex Wang commented on GERONIMO-5004: has been resolved. close it. > axis 1 osgi integration > --- > > Key: GERONIMO-5004 > URL: https://issues.apache.org/jira/browse/GERONIMO-5004 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 3.0 > > > get the axis 1 plugin working. > This requires scout and juddi. Scout looks OK, Juddi needs to apply patch > for JUDD-299. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-4996) myfaces 2 osgi integration
[ https://issues.apache.org/jira/browse/GERONIMO-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-4996. -- has been resolved. close it. > myfaces 2 osgi integration > -- > > Key: GERONIMO-4996 > URL: https://issues.apache.org/jira/browse/GERONIMO-4996 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: Jarek Gawor > Fix For: 3.0 > > > Tracking of integrating myfaces 2 integration into geronimo under osgi. > first problem is to get myfaces to fix their osgi metadata to allow use of > servlet 3 api jars and other javaee6 spec bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-4996) myfaces 2 osgi integration
[ https://issues.apache.org/jira/browse/GERONIMO-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4996. Resolution: Fixed > myfaces 2 osgi integration > -- > > Key: GERONIMO-4996 > URL: https://issues.apache.org/jira/browse/GERONIMO-4996 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: Jarek Gawor > Fix For: 3.0 > > > Tracking of integrating myfaces 2 integration into geronimo under osgi. > first problem is to get myfaces to fix their osgi metadata to allow use of > servlet 3 api jars and other javaee6 spec bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-4971) Recognize Aries applications in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4971. Resolution: Fixed I think this has been resolved. > Recognize Aries applications in Geronimo > > > Key: GERONIMO-4971 > URL: https://issues.apache.org/jira/browse/GERONIMO-4971 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Aries, osgi >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > Attachments: GERONIMO-4971-aries.diff > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090668#comment-13090668 ] Yi Xiao commented on GERONIMODEVTOOLS-759: -- I know you mean, Jarek. In my patch:OSGIBundleDeploy_759_persistence.patch, I modify the SynchronizeProjectOnServerTask, and when synchronizing with server, the bundle id will be updated, so I persist it. I still think save bundle id can save lots of time compare to look up bundle id every time from server, the SynchronizeProjectOnServerTask can guarantee the bundle id's correction, so I think just need to do a little modification in it we can use bundle id correctly. > Using the new APIs to manage the bundles status both in GEP and Server side > > > Key: GERONIMODEVTOOLS-759 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6, > Eclipse3.6SR1&SR2 >Reporter: Yi Xiao >Assignee: Jarek Gawor > Labels: OSGI, bundle > Fix For: 3.0 > > Attachments: OSGIBundleDeploy.patch, > OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch, > OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch > > > This improvement depends on the server's modules, so, if the server side does > not update timely, it may cause the GEP compile failure! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-4936) OpenJPA2 plugin needs to replace use of Configuration.getConfigurationClassLoader()
[
https://issues.apache.org/jira/browse/GERONIMO-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang resolved GERONIMO-4936.
Resolution: Fixed
> OpenJPA2 plugin needs to replace use of
> Configuration.getConfigurationClassLoader()
> ---
>
> Key: GERONIMO-4936
> URL: https://issues.apache.org/jira/browse/GERONIMO-4936
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: osgi
>Affects Versions: 3.0
>Reporter: Donald Woods
>Assignee: Rick McGuire
> Fix For: 3.0
>
>
> As pointed out by the TODO added in r830529 by Rick McGuire -
> plugins/openjpa2/geronimo-openjpa2/src/main/java/org/apache/geronimo/openjpa/ConfigurationMonitorGBean.java
> {code}
> private void configurationRunning(AbstractName name) {
> try {
> Configuration config = (Configuration)kernel.getGBean(name);
> -classLoaderMap.put(name, config.getConfigurationClassLoader());
> +// TODO: This needs to be resolved as to what class loader should be
> registered
> +// classLoaderMap.put(name, config.getConfigurationClassLoader());
> } catch (GBeanNotFoundException gnfe) {
> log.warn("Could not retrieve GBean for artifact: " +
> name.toString(), gnfe);
> }
> }
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-4936) OpenJPA2 plugin needs to replace use of Configuration.getConfigurationClassLoader()
[
https://issues.apache.org/jira/browse/GERONIMO-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang closed GERONIMO-4936.
--
Assignee: Rex Wang (was: Rick McGuire)
fixed, so close it.
private void configurationRunning(AbstractName name) {
try {
Configuration config = (Configuration)kernel.getGBean(name);
bundleMap.put(name, config.getBundle());
} catch (GBeanNotFoundException gnfe) {
log.warn("Could not retrieve GBean for artifact: " +
name.toString(), gnfe);
}
}
> OpenJPA2 plugin needs to replace use of
> Configuration.getConfigurationClassLoader()
> ---
>
> Key: GERONIMO-4936
> URL: https://issues.apache.org/jira/browse/GERONIMO-4936
> Project: Geronimo
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: osgi
>Affects Versions: 3.0
>Reporter: Donald Woods
>Assignee: Rex Wang
> Fix For: 3.0
>
>
> As pointed out by the TODO added in r830529 by Rick McGuire -
> plugins/openjpa2/geronimo-openjpa2/src/main/java/org/apache/geronimo/openjpa/ConfigurationMonitorGBean.java
> {code}
> private void configurationRunning(AbstractName name) {
> try {
> Configuration config = (Configuration)kernel.getGBean(name);
> -classLoaderMap.put(name, config.getConfigurationClassLoader());
> +// TODO: This needs to be resolved as to what class loader should be
> registered
> +// classLoaderMap.put(name, config.getConfigurationClassLoader());
> } catch (GBeanNotFoundException gnfe) {
> log.warn("Could not retrieve GBean for artifact: " +
> name.toString(), gnfe);
> }
> }
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-4935) WsdlGenerator needs to replace use of Configuration.addClassPath()
[ https://issues.apache.org/jira/browse/GERONIMO-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4935. Resolution: Fixed > WsdlGenerator needs to replace use of Configuration.addClassPath() > -- > > Key: GERONIMO-4935 > URL: https://issues.apache.org/jira/browse/GERONIMO-4935 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, osgi, webservices >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > A lot of the wsdl/jaxws code uses direct references to jars in the different > class loaders to generate a classpath string. This doesn't really work that > well when dealing with bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-4935) WsdlGenerator needs to replace use of Configuration.addClassPath()
[ https://issues.apache.org/jira/browse/GERONIMO-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-4935. -- resolved, so close it. > WsdlGenerator needs to replace use of Configuration.addClassPath() > -- > > Key: GERONIMO-4935 > URL: https://issues.apache.org/jira/browse/GERONIMO-4935 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, osgi, webservices >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > A lot of the wsdl/jaxws code uses direct references to jars in the different > class loaders to generate a classpath string. This doesn't really work that > well when dealing with bundles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-4920) Convert Tomcat plugin to bundlized version.
[ https://issues.apache.org/jira/browse/GERONIMO-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-4920. -- resolved, so close it. > Convert Tomcat plugin to bundlized version. > > > Key: GERONIMO-4920 > URL: https://issues.apache.org/jira/browse/GERONIMO-4920 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Placeholder for the Tomcat cleanup work. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-4920) Convert Tomcat plugin to bundlized version.
[ https://issues.apache.org/jira/browse/GERONIMO-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4920. Resolution: Fixed > Convert Tomcat plugin to bundlized version. > > > Key: GERONIMO-4920 > URL: https://issues.apache.org/jira/browse/GERONIMO-4920 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Rick McGuire > Fix For: 3.0 > > > Placeholder for the Tomcat cleanup work. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] branches/2.2: Failed for Revision: 1161315
Geronimo Revision: 1161315 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110824/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110824/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
Re: Geronimo 3.0-beta Release Status
Thank you David for letting us know, I will do 1.3 release as-is. Forrest On Thu, Aug 25, 2011 at 4:45 AM, David Jencks wrote: > Hi Forrest, > > I haven't quite figured out how to write a unit test, but trying some > things in a debugger I think the multidimensional array support is OK. So I > think I'm OK with releasing YOKO 1.3 as-is. > > thanks > david jencks > > On Aug 24, 2011, at 9:43 AM, Forrest Xia wrote: > > Thanks Rex for this status page. > > For YOKO 1.3, I am not sure if David Jencks has more fixes on > multidimension arrays support... > > Forrest > > On Wed, Aug 24, 2011 at 5:41 PM, Shawn Jiang wrote: > >> Thanks, Rex ! >> >> tck is in good shape now. I think Most of the JIRAs opened by Rick to >> track the Java EE 6 spec impl could be closed now. >> >> On Wed, Aug 24, 2011 at 5:11 PM, Rex Wang wrote: >> >>> Hi devs, >>> >>> I created a page in our wiki to record Geronimo 3.0-beta Release Status: >>> >>> https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+3.0-beta+Release+Status >>> >>> Now, we have a lot of OLD Jiras opened, which has been fixed or won't >>> fix, so could you please clean your Jira status? You could see the all the >>> un-resolved jiras in the #3.1 of the above page. >>> >>> thanks, >>> >>> -- >>> Lei Wang (Rex) >>> rwonly AT apache.org >>> >> >> >> >> -- >> Shawn >> > > >
Re: svn commit: r1160106 - /geronimo/server/trunk/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/cdi/OpenWebBeansWebInitializer.java
This issue has already received a lot of discussion at
https://hibernate.onjira.com/browse/BVTCK-11 but it looks like no one followed
up enough to force them to exclude the test. I think we should. I'll try to
find the proposed solution and comment
thanks
david jencks
On Aug 22, 2011, at 1:51 PM, David Blevins wrote:
>
> On Aug 22, 2011, at 9:25 AM, Kevan Miller wrote:
>
>>
>> On Aug 22, 2011, at 12:45 AM, dblev...@apache.org wrote:
>>
>>> Author: dblevins
>>> Date: Mon Aug 22 04:45:07 2011
>>> New Revision: 1160106
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1160106&view=rev
>>> Log:
>>> GERONIMO-6117: OpenWebBeansPlugin load optimization
>>>
>>> Modified:
>>>
>>> geronimo/server/trunk/plugins/openejb/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/cdi/OpenWebBeansWebInitializer.java
>>
>>
>> Cool. With this change and setting
>> BundleResourceHelper.searchWiredBundles=false (e.g.
>> GERONIMO_OPTS=-Dorg.apache.xbean.osgi.bundle.util.BundleResourceHelper.searchWiredBundles=false
>> ./geronimo run), my server starts without a problem and startup is pretty
>> good. Tthe timed portion (so doesn't count the initial karaf loading) is
>> 9-10 seconds:
>>
>> ...
>> Module 63/63 org.apache.geronimo.configs/wink-deployer/3.0-SNAPSHOT/car
>> started in .015s
>> Startup completed in 9.105s seconds
>> Listening on Ports:
>> ...
>>
>> Which is great, given that we're not doing any lazy startup. However, I'm
>> seeing some bean-validation tck failures with searchWiredBundles=false (jcdi
>> tck looks fine and I didn't try any other tck tests). Anybody able to take a
>> look at this?
>
> Looked into it a bit.
>
> Most the BVal tests seem to be failing due to classLoader.getResource() calls
> in Apache BVal looking for schemas. Probably there's some way we could work
> around that as we already have logic for this in BValModuleBuilderExtension.
>
> There is one failure however that will not pass with
> BundleResourceHelper.searchWiredBundles=false ... at least not the way it's
> implemented. ValidationProviderResolverTest is implementing its own provider
> search and verifying it works. Better said they're executing:
>
>classloader.getResources("META-INF/services/" +
> ValidationProvider.class.getName());
>
> And verifying that there is at least one provider found. Our version of that
> API has been extended to support more OSGi friendly search mechanisms -- the
> code Rick wrote.
>
> The options as I see them:
>
> 1. challenge the test
> 2. Don't use BundleResourceHelper.searchWiredBundles=false and live with the
> performance we have
> 3. Make the BundleResourceHelper.searchWiredBundles functionality more
> configurable so validation API can be exempt from limited search
> 4. Physically add a
> META-INF/services/javax.validation.spi.ValidationProvider file to apps
> 5. Somehow intercept calls to getResources(foo) and do like we did with the
> ServiceLoader searching of OWB and supply known implementations up front.
> Not sure if that is even possible in this situation.
>
> Open to ideas.
>
> -David
>
Re: Geronimo 3.0-beta Release Status
Hi Forrest, I haven't quite figured out how to write a unit test, but trying some things in a debugger I think the multidimensional array support is OK. So I think I'm OK with releasing YOKO 1.3 as-is. thanks david jencks On Aug 24, 2011, at 9:43 AM, Forrest Xia wrote: > Thanks Rex for this status page. > > For YOKO 1.3, I am not sure if David Jencks has more fixes on multidimension > arrays support... > > Forrest > > On Wed, Aug 24, 2011 at 5:41 PM, Shawn Jiang wrote: > Thanks, Rex ! > > tck is in good shape now. I think Most of the JIRAs opened by Rick to track > the Java EE 6 spec impl could be closed now. > > On Wed, Aug 24, 2011 at 5:11 PM, Rex Wang wrote: > Hi devs, > > I created a page in our wiki to record Geronimo 3.0-beta Release Status: > https://cwiki.apache.org/confluence/display/GMOxPMGT/Geronimo+3.0-beta+Release+Status > > Now, we have a lot of OLD Jiras opened, which has been fixed or won't fix, so > could you please clean your Jira status? You could see the all the > un-resolved jiras in the #3.1 of the above page. > > thanks, > > -- > Lei Wang (Rex) > rwonly AT apache.org > > > > -- > Shawn >
[BUILD] branches/2.2: Failed for Revision: 1161205
Geronimo Revision: 1161205 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110824/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110824/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:592) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] [Closed] (GERONIMO-5407) XSSXSRFFilter error in G 3.0-M1 jetty build when trying to list plugins in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5407. - > XSSXSRFFilter error in G 3.0-M1 jetty build when trying to list plugins in > admin console > > > Key: GERONIMO-5407 > URL: https://issues.apache.org/jira/browse/GERONIMO-5407 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0-M1, 3.0 >Reporter: Forrest Xia >Assignee: Shawn Jiang > Fix For: 3.0 > > > Steps: > 1. start jetty java ee build > 2. try to list plugins in local repository > the error shows in console output: > 2010-06-27 09:57:48,188 WARN [XSRFHandler] Blocked due to missing > HttpServletRequest parameter. > 2010-06-27 09:57:48,188 ERROR [XSSXSRFFilter] XSSXSRFFilter blocked > HttpServletRequest due to invalid FORM content. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5233) Geronimo 3.0 Samples
[ https://issues.apache.org/jira/browse/GERONIMO-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5233. - > Geronimo 3.0 Samples > > > Key: GERONIMO-5233 > URL: https://issues.apache.org/jira/browse/GERONIMO-5233 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: sample apps >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: viola.lu > Fix For: 3.0 > > > We shall prepare some samples for Geronimo 3.0 new features and do some > restructuring work, so that we can present a clear view to our user where to > look for java ee 5 samples, where is java ee 6 samples, where is osgi support > demo. > The stuffs shall include but not limited as following: > 1. Add some samples to demo Java EE 6 support > 2. Add some samples to demo OSGi support > 3. Restructure existing samples as Java EE 5 > 4. Move daytrader back for consistent maintanence > Some sub-jiras will be opened to track the progress of each aspect above. > Any comments/ideas about samples, welcome comment on this jira or post to > mailing list at thread > http://n3.nabble.com/About-G3-0-Java-EE-6-Samples-tp699382p699382.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5352) Bundlize jaxb-xjc and align its version with jaxb-impl
[ https://issues.apache.org/jira/browse/GERONIMO-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5352. - > Bundlize jaxb-xjc and align its version with jaxb-impl > -- > > Key: GERONIMO-5352 > URL: https://issues.apache.org/jira/browse/GERONIMO-5352 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 3.0 > > > Check the mailing list thread for details: > http://apache-geronimo.328035.n3.nabble.com/jaxb-xjc-and-jaxb-impl-should-have-the-same-version-number-in-G-trunk-and-3-0-M1-branch-td843920.html#a843920 > I would do as following: > 1. Bundlize the jaxb-xjc > 2. Release the bundle > 3. Update 3.0-M1 and trunk -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5233) Geronimo 3.0 Samples
[ https://issues.apache.org/jira/browse/GERONIMO-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5233. --- Resolution: Fixed Fix Version/s: 3.0 Assignee: viola.lu (was: Forrest Xia) > Geronimo 3.0 Samples > > > Key: GERONIMO-5233 > URL: https://issues.apache.org/jira/browse/GERONIMO-5233 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: sample apps >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: viola.lu > Fix For: 3.0 > > > We shall prepare some samples for Geronimo 3.0 new features and do some > restructuring work, so that we can present a clear view to our user where to > look for java ee 5 samples, where is java ee 6 samples, where is osgi support > demo. > The stuffs shall include but not limited as following: > 1. Add some samples to demo Java EE 6 support > 2. Add some samples to demo OSGi support > 3. Restructure existing samples as Java EE 5 > 4. Move daytrader back for consistent maintanence > Some sub-jiras will be opened to track the progress of each aspect above. > Any comments/ideas about samples, welcome comment on this jira or post to > mailing list at thread > http://n3.nabble.com/About-G3-0-Java-EE-6-Samples-tp699382p699382.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5352) Bundlize jaxb-xjc and align its version with jaxb-impl
[ https://issues.apache.org/jira/browse/GERONIMO-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5352: -- Fix Version/s: 3.0 > Bundlize jaxb-xjc and align its version with jaxb-impl > -- > > Key: GERONIMO-5352 > URL: https://issues.apache.org/jira/browse/GERONIMO-5352 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 3.0 > > > Check the mailing list thread for details: > http://apache-geronimo.328035.n3.nabble.com/jaxb-xjc-and-jaxb-impl-should-have-the-same-version-number-in-G-trunk-and-3-0-M1-branch-td843920.html#a843920 > I would do as following: > 1. Bundlize the jaxb-xjc > 2. Release the bundle > 3. Update 3.0-M1 and trunk -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5352) Bundlize jaxb-xjc and align its version with jaxb-impl
[ https://issues.apache.org/jira/browse/GERONIMO-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-5352. --- Resolution: Fixed > Bundlize jaxb-xjc and align its version with jaxb-impl > -- > > Key: GERONIMO-5352 > URL: https://issues.apache.org/jira/browse/GERONIMO-5352 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Forrest Xia > > Check the mailing list thread for details: > http://apache-geronimo.328035.n3.nabble.com/jaxb-xjc-and-jaxb-impl-should-have-the-same-version-number-in-G-trunk-and-3-0-M1-branch-td843920.html#a843920 > I would do as following: > 1. Bundlize the jaxb-xjc > 2. Release the bundle > 3. Update 3.0-M1 and trunk -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-5698) Add db2 for iSeries tranql xa connector to server 3.0 when it's ready
[ https://issues.apache.org/jira/browse/GERONIMO-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reassigned GERONIMO-5698: - Assignee: Forrest Xia > Add db2 for iSeries tranql xa connector to server 3.0 when it's ready > - > > Key: GERONIMO-5698 > URL: https://issues.apache.org/jira/browse/GERONIMO-5698 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: databases >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Forrest Xia >Priority: Minor > Fix For: 3.0 > > > Refer to the parent jira for information. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (GERONIMO-5510) Make a daytrader assembly for Java EE 6 web profile server
[ https://issues.apache.org/jira/browse/GERONIMO-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia deleted GERONIMO-5510: -- > Make a daytrader assembly for Java EE 6 web profile server > -- > > Key: GERONIMO-5510 > URL: https://issues.apache.org/jira/browse/GERONIMO-5510 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > > Daytrader performance benchmark app has no proper assembly for Java EE 6 web > profile server, we need to make a new assembly for this purpose. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5698) Add db2 for iSeries tranql xa connector to server 3.0 when it's ready
[ https://issues.apache.org/jira/browse/GERONIMO-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5698. - Resolution: Fixed Fix Version/s: 3.0 > Add db2 for iSeries tranql xa connector to server 3.0 when it's ready > - > > Key: GERONIMO-5698 > URL: https://issues.apache.org/jira/browse/GERONIMO-5698 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: databases >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Forrest Xia >Priority: Minor > Fix For: 3.0 > > > Refer to the parent jira for information. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5599) Reenable monitoring admin console portlets
[ https://issues.apache.org/jira/browse/GERONIMO-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5599. - > Reenable monitoring admin console portlets > -- > > Key: GERONIMO-5599 > URL: https://issues.apache.org/jira/browse/GERONIMO-5599 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Shenghao Fang > Attachments: GERONIMO-5599-20110629.patch, > GERONIMO-5599-20110712-1.patch, GERONIMO-5599-20110712.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5600) Reenable EJB server admin console portlets
[ https://issues.apache.org/jira/browse/GERONIMO-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5600. - > Reenable EJB server admin console portlets > -- > > Key: GERONIMO-5600 > URL: https://issues.apache.org/jira/browse/GERONIMO-5600 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Shenghao Fang > Fix For: 3.0 > > Attachments: GERONIMO-5600.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5597) Reenable database-related admin console portlets
[ https://issues.apache.org/jira/browse/GERONIMO-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5597. - > Reenable database-related admin console portlets > > > Key: GERONIMO-5597 > URL: https://issues.apache.org/jira/browse/GERONIMO-5597 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Shenghao Fang > Fix For: 3.0 > > Attachments: GERONIMO-5597-01.patch, GERONIMO-5597.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5476) @EJB does not injected in servlet class
[ https://issues.apache.org/jira/browse/GERONIMO-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5476. - > @EJB does not injected in servlet class > --- > > Key: GERONIMO-5476 > URL: https://issues.apache.org/jira/browse/GERONIMO-5476 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: OpenEJB >Affects Versions: 3.0-M1, 3.0 > Environment: ubuntu 8.04.4 > sun jdk 1.6.0_20 > Geronimo 3.0-M1 tomcat assembly >Reporter: Forrest Xia >Assignee: Jarek Gawor > Fix For: 3.0 > > > Steps: > 1. check out geronimo trunk source code > 2. build server code until success > 3. go to testsuite/javaee6-testsuite/ejb3.1lite-test > 4. run command: mvn install -Pit > The test will fail with an NPE exception. Check the geronimo.out, the > exception like this: > 2010-07-27 21:28:14,419 WARN [Parameters] Parameters: Invalid chunk '' > ignored. > java.lang.NullPointerException > at > org.apache.geronimo.testsuite.javaee6.ejbtest.Servlets.CalculatorServlet.processRequest(CalculatorServlet.java:56) > at > org.apache.geronimo.testsuite.javaee6.ejbtest.Servlets.CalculatorServlet.doGet(CalculatorServlet.java:76) > 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:303) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:666) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) > at > org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:146) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:108) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:402) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:254) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:267) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:245) > at > org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:260) > at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) > at > org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > 2010-07-27 21:28:43,600 ERROR [[CalculatorServlet]] Servlet.service() for > servlet CalculatorServlet threw exception > java.lang.NullPointerException > at > org.apache.geronimo.testsuite.javaee6.ejbtest.Servlets.CalculatorServlet.processRequest(CalculatorServlet.java:56) > at > org.apache.geronimo.testsuite.javaee6.ejbtest.Servlets.CalculatorServlet.doGet(CalculatorServlet.java:76) > 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:303) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:666) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) > at > org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:146) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:108) > at > org.a
[jira] [Closed] (GERONIMO-5596) Reenable plan creator admin console portlet
[ https://issues.apache.org/jira/browse/GERONIMO-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5596. - > Reenable plan creator admin console portlet > --- > > Key: GERONIMO-5596 > URL: https://issues.apache.org/jira/browse/GERONIMO-5596 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Shenghao Fang > Fix For: 3.0 > > Attachments: GERONIMO-5596-01.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5521) NoClassDefFoundError when deploying a datasource with non-OSGi jdbc lib dependencies
[ https://issues.apache.org/jira/browse/GERONIMO-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5521. - > NoClassDefFoundError when deploying a datasource with non-OSGi jdbc lib > dependencies > > > Key: GERONIMO-5521 > URL: https://issues.apache.org/jira/browse/GERONIMO-5521 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: connector >Affects Versions: 3.0 > Environment: ubuntu 8.04 x86-32 > sun java 1.6.0_20 >Reporter: Forrest Xia >Assignee: Rex Wang > Fix For: 3.0 > > > Steps: > 1. start geronimo tomcat we profile assembly > 2. install jdbc library via deploy install-library command. The jdbc > libraries are not bundlized yet > 3. define a datasource deployment plan with dependencies on the jdbc libraries > 4. deploy the datasource via proper tranql adapter > An exception throws like this: > 2010-08-11 09:02:59,585 ERROR [GBeanInstanceState] Error while starting; > GBean is now in the FAILED state: > abstractName="org.apache.geronimo.samples.daytrader.plugins/daytrader-db2-datasource/3.0-M1/car?J2EEApplication=null,JCAConnectionFactory=jdbc/TradeDataSource,JCAResource=tranql-connector-db2-xa-1.5,ResourceAdapter=tranql-connector-db2-xa-1.5,ResourceAdapterModule=org.apache.geronimo.samples.daytrader.plugins/daytrader-db2-datasource/3.0-M1/car,j2eeType=JCAManagedConnectionFactory,name=jdbc/TradeDataSource" > java.lang.NoClassDefFoundError: com.ibm.db2.jcc.DB2XADataSource > at org.tranql.connector.db2.XAMCF.(XAMCF.java:51) > at java.lang.J9VMInternals.newInstanceImpl(Native Method) > at java.lang.Class.newInstance(Class.java:1325) > at > org.apache.geronimo.connector.wrapper.outbound.ManagedConnectionFactoryWrapper.(ManagedConnectionFactoryWrapper.java:115) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:44) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) > at java.lang.reflect.Constructor.newInstance(Constructor.java:516) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:952) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:933) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:560) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:460) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:224) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:698) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:677) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > 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.kernel.KernelGBean.invoke(KernelGBean.java:344) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.M
[jira] [Closed] (GERONIMO-5586) Provide a way to transform traditional jar to OSGi bundle when user install the jar into G repository.
[ https://issues.apache.org/jira/browse/GERONIMO-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5586. - > Provide a way to transform traditional jar to OSGi bundle when user install > the jar into G repository. > -- > > Key: GERONIMO-5586 > URL: https://issues.apache.org/jira/browse/GERONIMO-5586 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Rex Wang > Fix For: 3.0 > > > As G server fundamentally turn into an OSGi based java ee application server, > all libraries are required to be a OSGi bundle. But this may not work > friendly to popular Java EE user. > Let's say a simple scenario that deploys a data source to G server: > 1. User uses install-library command or admin console to install the jdbc > driver into G repository > 2. User prepare a datasource deployment plan that depends on the installed > jdbc driver > 3. User uses deploy command or admin console to deploy the datasource > The deployer will report a ClassNotFound exception saying jdbc driver class > is not found. Java EE user may confuse around here, since they know they've > installed the jdbc libraries into the repository, but why encounter the CNF > exception? > From user-friendly aspect, G server is better to provide a way to transform > traditional jar into a OSGi bundle transparently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5637) deploy install-plugin command does not report failure when plugin is failed to install
[ https://issues.apache.org/jira/browse/GERONIMO-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5637. - > deploy install-plugin command does not report failure when plugin is failed > to install > -- > > Key: GERONIMO-5637 > URL: https://issues.apache.org/jira/browse/GERONIMO-5637 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 > Environment: sun jdk 1.6.0_20 > ubuntu 10.04 x86 > G 3.0 snapshot build on 2010.10.12-09:22:17.418+0800 >Reporter: Forrest Xia >Assignee: viola.lu > Attachments: G5637.patch, > daytrader-derby-datasource-3.0-M1-SNAPSHOT.car > > > Steps: > 1. build the latest code from trunk > 2. get tomcat7 assembly running at the default port > 3. use deploy install-plugin command to install the attached plugin sample > Problem: > 1. the command shows installation complete without any error like this: > $ bin/deploy install-plugin > ~/Desktop/daytrader-derby-datasource-3.0-M1-SNAPSHOT.car > Using GERONIMO_HOME: > /home/forrestxm/temp/geronimo-tomcat7-javaee6-3.0-SNAPSHOT > Using GERONIMO_TMPDIR: var/temp > Using JRE_HOME:/home/forrestxm/softwares/jdk/jdk1.6.0_20/jre > Checking for status every 1000ms: > Starting > org.apache.geronimo.samples.daytrader.plugins/daytrader-derby-datasource/3.0-M1-SNAPSHOT/car > Installation Complete! > Downloaded 111 kB in 1s (111 kB/s) > 2. but on the server console output, there are exceptions showup like this: > 2010-10-12 11:02:30,515 ERROR [GBeanInstanceState] Error while starting; > GBean is now in the FAILED state: > abstractName="org.apache.geronimo.samples.daytrader.plugins/daytrader-derby-datasource/3.0-M1-SNAPSHOT/car?configurationName=org.apache.geronimo.samples.daytrader.plugins/daytrader-derby-datasource/3.0-M1-SNAPSHOT/car" > org.apache.geronimo.kernel.config.InvalidConfigException: Unable to > deserialize GBeanState in classloader: > org.apache.geronimo.samples.daytrader.plugins.daytrader-derby-datasource_3.0.0.M1-SNAPSHOT > [294] > at > org.apache.geronimo.kernel.config.SerializedGBeanState.loadGBeans(SerializedGBeanState.java:138) > at > org.apache.geronimo.kernel.config.SerializedGBeanState.getGBeans(SerializedGBeanState.java:65) > at > org.apache.geronimo.kernel.config.ConfigurationData.getGBeans(ConfigurationData.java:186) > at > org.apache.geronimo.kernel.config.Configuration.(Configuration.java:214) > at sun.reflect.GeneratedConstructorAccessor43.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:952) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:933) > 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.kernel.basic.BasicKernel.startGBean(BasicKernel.java:368) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:190) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:354) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:327) > at > org.apache.geronimo.kernel.osgi.ConfigurationActivator.start(ConfigurationActivator.java:62) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783) > at java.security.AccessController.doPrivileged(Native Method) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755) > at > org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352) > at > org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280) > at > org.apache.geronimo.kernel.config.SimpleCon
[jira] [Closed] (GERONIMO-5594) Reenable hot deploy on G 3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5594. - > Reenable hot deploy on G 3.0 > > > Key: GERONIMO-5594 > URL: https://issues.apache.org/jira/browse/GERONIMO-5594 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Ivan > Fix For: 3.0 > > > Hot deployment function shall be enabled for G 3.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5598) Reenable debug views admin console portlets
[ https://issues.apache.org/jira/browse/GERONIMO-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5598. - > Reenable debug views admin console portlets > --- > > Key: GERONIMO-5598 > URL: https://issues.apache.org/jira/browse/GERONIMO-5598 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Shenghao Fang > Fix For: 3.0 > > Attachments: GERONIMO-5598.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5796) jsf2.0-test is failed
[
https://issues.apache.org/jira/browse/GERONIMO-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forrest Xia closed GERONIMO-5796.
-
> jsf2.0-test is failed
> -
>
> Key: GERONIMO-5796
> URL: https://issues.apache.org/jira/browse/GERONIMO-5796
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: testsuite
>Affects Versions: 3.0
> Environment: ubuntu 10.04
> sun jdk 1.6.0_23
>Reporter: Forrest Xia
>Assignee: Forrest Xia
>Priority: Minor
> Fix For: 3.0
>
> Attachments: 5796-addConfigFile.patch
>
>
> Found an exception in the server log:
> 2011-01-29 16:12:59,018 ERROR [ErrorPageWriter] An exception occurred
> javax.faces.FacesException: javax.el.PropertyNotFoundException:
> /0.0.0.0/converter-javaee6/index.xhtml at line 42 and column 56
> value="#{ConverterBean.value}": Target Unreachable, identifier
> 'ConverterBean' resolved to null
> at
> org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.wrap(ExceptionHandlerImpl.java:241)
> at
> org.apache.myfaces.shared_impl.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:156)
> at
> org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:191)
> at
> org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at
> org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:819)
> at
> org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
> at
> org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:108)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:379)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:242)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:259)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:281)
> at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:243)
> at
> org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:373)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.el.PropertyNotFoundException:
> /0.0.0.0/converter-javaee6/index.xhtml at line 42 and column 56
> value="#{ConverterBean.value}": Target Unreachable, identifier
> 'ConverterBean' resolved to null
> at
> org.apache.myfaces.view.facelets.el.TagValueExpression.getType(TagValueExpression.java:73)
> at
> org.apache.myfaces.shared_impl.renderkit._SharedRendererUtils.findUIOutputConverter(_SharedRendererUtils.java:77)
> at
> org.apache.myfaces.shared_impl.renderkit.RendererUtils.findUIOutputConverter(RendererUtils.java:407)
> at
> org.apache.myfaces.shared_impl.renderkit.RendererUtils.getConvertedUIOutputValue(RendererUtils.java:769)
> at
> org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.getConvertedValue(HtmlTextRendererBase.java:274)
> at javax.faces.component.UIInput.getConvertedValue(UIInput.java:624)
> at javax.faces.component.UIInput.validate(UIInput.java:556)
> at javax.faces.component.UIInput.processValidators(UIInput.java:247)
> at
> org.apache.myfaces.context.servlet.PartialViewContextImpl$PhaseAwareVisitCallback.visit(PartialViewContextImpl.java:531)
> at
> org.apache.myfaces.component.visit.PartialVisitContext.invokeVisitCallback(PartialVisitContext.java:207)
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:773)
> at
> javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:991)
> at javax.faces.component.UIForm.visitTree(UIForm.java:269)
> at javax.faces.component.UIComponent.visit
[jira] [Closed] (GERONIMO-5639) org.osgi.service.blueprint.container.ServiceUnavailableException when shutdown the server
[ https://issues.apache.org/jira/browse/GERONIMO-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5639. - > org.osgi.service.blueprint.container.ServiceUnavailableException when > shutdown the server > - > > Key: GERONIMO-5639 > URL: https://issues.apache.org/jira/browse/GERONIMO-5639 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: startup/shutdown >Affects Versions: 3.0 > Environment: Windows 7 x86 > sun jdk 1.6.0_20 >Reporter: Forrest Xia >Assignee: Shawn Jiang >Priority: Minor > Fix For: 3.0 > > Attachments: G5639.patch, config.xml, geronimo.log > > > Steps: > 1. Get the latest G build > 2. Unzip and boot the default instance > 3. Shutdown it > Everything seems ok, but in the geronimo.log there is always an exception > like this: > 2010-10-12 16:35:04,985 INFO [BeanRecipe] Error invoking destroy method > org.osgi.service.blueprint.container.ServiceUnavailableException: The > Blueprint container is being or has been destroyed > at > org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:183) > at > org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:52) > at > org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:208) > at > org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe$CgLibProxyFactory$1.loadObject(AbstractServiceReferenceRecipe.java:652) > at > org.apache.yoko.osgi.locator.Register$$EnhancerByCGLIB$$2b0d9326.unregisterProvider() > at org.apache.yoko.osgi.locator.ProviderBean.stop(ProviderBean.java:61) > 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.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:221) > at > org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:844) > at > org.apache.aries.blueprint.container.BeanRecipe.destroy(BeanRecipe.java:761) > at > org.apache.aries.blueprint.container.BlueprintRepository.destroy(BlueprintRepository.java:295) > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.destroyComponents(BlueprintContainerImpl.java:665) > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.destroy(BlueprintContainerImpl.java:819) > at > org.apache.aries.blueprint.container.BlueprintExtender.destroyContext(BlueprintExtender.java:204) > at > org.apache.aries.blueprint.container.BlueprintExtender.bundleChanged(BlueprintExtender.java:196) > at > org.apache.aries.blueprint.container.BlueprintExtender$BlueprintBundleTrackerCustomizer.modifiedBundle(BlueprintExtender.java:385) > at > org.apache.aries.util.tracker.InternalRecursiveBundleTracker.modifiedBundle(InternalRecursiveBundleTracker.java:89) > at > org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:453) > at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:237) > at > org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:413) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:919) > at > org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227) > at > org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149) > at > org.eclipse.osgi.framework.internal.core.Framework.publishBundleEventPrivileged(Framework.java:1350) > at > org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Framework.java:1301) > at > org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:470) > at > org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:546) > at > org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1098) > at > org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:593) > at > org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:261) > at > org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:216) > at > org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:266) >
[jira] [Closed] (GERONIMO-5828) javax.naming.NotContextException: jndiname when running a tck case
[ https://issues.apache.org/jira/browse/GERONIMO-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5828. - > javax.naming.NotContextException: jndiname when running a tck case > -- > > Key: GERONIMO-5828 > URL: https://issues.apache.org/jira/browse/GERONIMO-5828 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: OpenEJB >Affects Versions: 3.0 > Environment: ubuntu 10.04 x86 > oracle jdk 1.6.0_23 >Reporter: Forrest Xia >Assignee: Shawn Jiang > Fix For: 3.0 > > > When running a tck case which is related to EJB. I encounter this exception: > 02-22-2011 14:54:58: ERROR: javax.naming.NotContextException: [anjndiname] > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:165) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605) > at > org.apache.openejb.server.ejbd.JndiRequestHandler.doLookup(JndiRequestHandler.java:188) > at > org.apache.openejb.server.ejbd.JndiRequestHandler.processRequest(JndiRequestHandler.java:129) > at > org.apache.openejb.server.ejbd.EjbDaemon.processJndiRequest(EjbDaemon.java:200) > at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:153) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:71) > at > org.apache.openejb.server.ejbd.KeepAliveServer$Session.service(KeepAliveServer.java:213) > at > org.apache.openejb.server.ejbd.KeepAliveServer.service(KeepAliveServer.java:233) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:66) > at org.apache.openejb.server.ServicePool$2.run(ServicePool.java:91) > at org.apache.openejb.server.ServicePool$3.run(ServicePool.java:120) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > This same exception happens in several other EJB related cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
