[jira] [Closed] (GERONIMO-6040) Update DatabaseInitializationGBean, mailGBean in samples deployment plan
[ https://issues.apache.org/jira/browse/GERONIMO-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-6040. -- Resolution: Fixed > Update DatabaseInitializationGBean, mailGBean in samples deployment plan > > > Key: GERONIMO-6040 > URL: https://issues.apache.org/jira/browse/GERONIMO-6040 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: sample apps >Affects Versions: 3.0 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 3.0 > > > Now org.apache.geronimo.connector.DatabaseInitializationGBean and mailGbean > name changed, should update samples deployment plan to make sample deployment > pass -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-763) "Source not found" message when debugging a project
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-763. -- Resolution: Fixed Fix Version/s: 3.0 > "Source not found" message when debugging a project > --- > > Key: GERONIMODEVTOOLS-763 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > > Under certain circumstances one can see "Source not found" message while > debugging a project that exists in the workspace and is deployed to the > server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-763) "Source not found" message when debugging a project
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058211#comment-13058211 ] Jarek Gawor commented on GERONIMODEVTOOLS-763: -- In revision 1141790 I committed some changes that reset the source project lookup list when needed. The way the reset is done is not too great but I couldn't find a better / easier way to do it. > "Source not found" message when debugging a project > --- > > Key: GERONIMODEVTOOLS-763 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > Under certain circumstances one can see "Source not found" message while > debugging a project that exists in the workspace and is deployed to the > server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-763) "Source not found" message when debugging a project
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058207#comment-13058207
]
Jarek Gawor commented on GERONIMODEVTOOLS-763:
--
About 1). No idea why & how that happens but the early source path computation
was triggered by the following code:
URL.setURLStreamHandlerFactory(streamHandlerFactory);
In OSGi this will always throw an Error on this call since the framework itself
sets a default factory (and only one can be set). The call to this function was
in a proper try {} catch block but somehow it still caused Eclipse to fire the
breakpoint hit event.
> "Source not found" message when debugging a project
> ---
>
> Key: GERONIMODEVTOOLS-763
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
>Affects Versions: 3.0
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
>
> Under certain circumstances one can see "Source not found" message while
> debugging a project that exists in the workspace and is deployed to the
> server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6034) testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Blevins reassigned GERONIMO-6034: --- Assignee: David Blevins > testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest) > - > > Key: GERONIMO-6034 > URL: https://issues.apache.org/jira/browse/GERONIMO-6034 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins >Assignee: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6034) testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058165#comment-13058165 ] David Blevins commented on GERONIMO-6034: - Passing in OpenEJB, still haven't identified the cause in Geronimo. Related to the testPassivationOfEjbs() > testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest) > - > > Key: GERONIMO-6034 > URL: https://issues.apache.org/jira/browse/GERONIMO-6034 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6037) testPassivationOfEjbs(org.jboss.jsr299.tck.tests.implementation.simple.resource.ejb.EjbInjectionTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058162#comment-13058162 ] David Blevins commented on GERONIMO-6037: - Passing in OpenEJB, still haven't identified the cause in Geronimo. > testPassivationOfEjbs(org.jboss.jsr299.tck.tests.implementation.simple.resource.ejb.EjbInjectionTest) > - > > Key: GERONIMO-6037 > URL: https://issues.apache.org/jira/browse/GERONIMO-6037 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6037) testPassivationOfEjbs(org.jboss.jsr299.tck.tests.implementation.simple.resource.ejb.EjbInjectionTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Blevins reassigned GERONIMO-6037: --- Assignee: David Blevins > testPassivationOfEjbs(org.jboss.jsr299.tck.tests.implementation.simple.resource.ejb.EjbInjectionTest) > - > > Key: GERONIMO-6037 > URL: https://issues.apache.org/jira/browse/GERONIMO-6037 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins >Assignee: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (GERONIMO-6039) testInjectionIntoWebServiceEndpoint(org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058158#comment-13058158 ] David Blevins edited comment on GERONIMO-6039 at 7/1/11 12:54 AM: -- Fails in both OpenEJB and Geronimo. Should be an easy fix for Geronimo. We simply need to construct and populate a limited version of ManagedBean -- anything that extends AbstractInjectionTargetBean really, populate the injection target information, then call: - injectFields(..) - injectMethods(..) - injectSuperFields(..) - injectSuperMethods(..) was (Author: dblevins): Fails in both OpenEJB and Geronimo. Should be an easy fix for Geronimo. > testInjectionIntoWebServiceEndpoint(org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest) > -- > > Key: GERONIMO-6039 > URL: https://issues.apache.org/jira/browse/GERONIMO-6039 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6039) testInjectionIntoWebServiceEndpoint(org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058158#comment-13058158 ] David Blevins commented on GERONIMO-6039: - Fails in both OpenEJB and Geronimo. Should be an easy fix for Geronimo. > testInjectionIntoWebServiceEndpoint(org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest) > -- > > Key: GERONIMO-6039 > URL: https://issues.apache.org/jira/browse/GERONIMO-6039 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6036) testNonStaticProducerMethodInheritedBySpecializingSubclass(org.jboss.jsr299.tck.tests.implementation.producer.method.definition.enterprise.EnterpriseProducerMethodDe
[ https://issues.apache.org/jira/browse/GERONIMO-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058157#comment-13058157 ] David Blevins commented on GERONIMO-6036: - Fails in both OpenEJB and Geronimo > testNonStaticProducerMethodInheritedBySpecializingSubclass(org.jboss.jsr299.tck.tests.implementation.producer.method.definition.enterprise.EnterpriseProducerMethodDefinitionTest) > -- > > Key: GERONIMO-6036 > URL: https://issues.apache.org/jira/browse/GERONIMO-6036 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6038) testNonContextualSessionBeanReferenceIsIntercepted(org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonCo
[ https://issues.apache.org/jira/browse/GERONIMO-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058155#comment-13058155 ] David Blevins commented on GERONIMO-6038: - This appears to be an issue with scanning CDI beans and the GeronimoResourceInjectionService. It's a bare bean with no other annotations other than @EJB. We currently only scan for beans annotated with @Produces then we scan those classes for @Resource and @EJB, etc. We just need to widen our scope. Not too tricky as the xbean-finder code has been in proved so that we can get a list of all the possible CDI beans. We just need to scan that regardless of if @Produces is used. > testNonContextualSessionBeanReferenceIsIntercepted(org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonContextualEjbReferenceTest) > -- > > Key: GERONIMO-6038 > URL: https://issues.apache.org/jira/browse/GERONIMO-6038 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins >Assignee: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6040) Update DatabaseInitializationGBean, mailGBean in samples deployment plan
Update DatabaseInitializationGBean, mailGBean in samples deployment plan Key: GERONIMO-6040 URL: https://issues.apache.org/jira/browse/GERONIMO-6040 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: sample apps Affects Versions: 3.0 Reporter: viola.lu Assignee: viola.lu Priority: Minor Fix For: 3.0 Now org.apache.geronimo.connector.DatabaseInitializationGBean and mailGbean name changed, should update samples deployment plan to make sample deployment pass -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6032) testRequestScopeDestroyedAfterCallToEjbTimeoutMethod(org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058151#comment-13058151 ] David Blevins commented on GERONIMO-6032: - Have this working in my copy but results in 4 new failures (was 50+ then 20+ now is 4.. still hacking). > testRequestScopeDestroyedAfterCallToEjbTimeoutMethod(org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest) > -- > > Key: GERONIMO-6032 > URL: https://issues.apache.org/jira/browse/GERONIMO-6032 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins >Assignee: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6033) testSettingInjectionTargetReplacesIt(org.jboss.jsr299.tck.tests.extensions.producer.ProducerTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058150#comment-13058150 ] David Blevins commented on GERONIMO-6033: - Works in OpenEJB trunk code with the embedded setup. > testSettingInjectionTargetReplacesIt(org.jboss.jsr299.tck.tests.extensions.producer.ProducerTest) > - > > Key: GERONIMO-6033 > URL: https://issues.apache.org/jira/browse/GERONIMO-6033 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6035) testApplicationCannotCallRemoveMethodOnNonDependentScopedSessionEnterpriseBean(org.jboss.jsr299.tck.tests.implementation.enterprise.remove.EnterpriseBeanRemoveMethodT
[ https://issues.apache.org/jira/browse/GERONIMO-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Blevins reassigned GERONIMO-6035: --- Assignee: David Blevins > testApplicationCannotCallRemoveMethodOnNonDependentScopedSessionEnterpriseBean(org.jboss.jsr299.tck.tests.implementation.enterprise.remove.EnterpriseBeanRemoveMethodTest) > -- > > Key: GERONIMO-6035 > URL: https://issues.apache.org/jira/browse/GERONIMO-6035 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins >Assignee: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6032) testRequestScopeDestroyedAfterCallToEjbTimeoutMethod(org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Blevins reassigned GERONIMO-6032: --- Assignee: David Blevins > testRequestScopeDestroyedAfterCallToEjbTimeoutMethod(org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest) > -- > > Key: GERONIMO-6032 > URL: https://issues.apache.org/jira/browse/GERONIMO-6032 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins >Assignee: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6036) testNonStaticProducerMethodInheritedBySpecializingSubclass(org.jboss.jsr299.tck.tests.implementation.producer.method.definition.enterprise.EnterpriseProducerMethodDefi
testNonStaticProducerMethodInheritedBySpecializingSubclass(org.jboss.jsr299.tck.tests.implementation.producer.method.definition.enterprise.EnterpriseProducerMethodDefinitionTest) -- Key: GERONIMO-6036 URL: https://issues.apache.org/jira/browse/GERONIMO-6036 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6038) testNonContextualSessionBeanReferenceIsIntercepted(org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonCont
testNonContextualSessionBeanReferenceIsIntercepted(org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonContextualEjbReferenceTest) -- Key: GERONIMO-6038 URL: https://issues.apache.org/jira/browse/GERONIMO-6038 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6038) testNonContextualSessionBeanReferenceIsIntercepted(org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonCon
[ https://issues.apache.org/jira/browse/GERONIMO-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Blevins reassigned GERONIMO-6038: --- Assignee: David Blevins > testNonContextualSessionBeanReferenceIsIntercepted(org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonContextualEjbReferenceTest) > -- > > Key: GERONIMO-6038 > URL: https://issues.apache.org/jira/browse/GERONIMO-6038 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins >Assignee: David Blevins > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6039) testInjectionIntoWebServiceEndpoint(org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest)
testInjectionIntoWebServiceEndpoint(org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest) -- Key: GERONIMO-6039 URL: https://issues.apache.org/jira/browse/GERONIMO-6039 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6037) testPassivationOfEjbs(org.jboss.jsr299.tck.tests.implementation.simple.resource.ejb.EjbInjectionTest)
testPassivationOfEjbs(org.jboss.jsr299.tck.tests.implementation.simple.resource.ejb.EjbInjectionTest) - Key: GERONIMO-6037 URL: https://issues.apache.org/jira/browse/GERONIMO-6037 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6032) testRequestScopeDestroyedAfterCallToEjbTimeoutMethod(org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest)
testRequestScopeDestroyedAfterCallToEjbTimeoutMethod(org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest) -- Key: GERONIMO-6032 URL: https://issues.apache.org/jira/browse/GERONIMO-6032 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6033) testSettingInjectionTargetReplacesIt(org.jboss.jsr299.tck.tests.extensions.producer.ProducerTest)
testSettingInjectionTargetReplacesIt(org.jboss.jsr299.tck.tests.extensions.producer.ProducerTest) - Key: GERONIMO-6033 URL: https://issues.apache.org/jira/browse/GERONIMO-6033 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6035) testApplicationCannotCallRemoveMethodOnNonDependentScopedSessionEnterpriseBean(org.jboss.jsr299.tck.tests.implementation.enterprise.remove.EnterpriseBeanRemoveMethodTe
testApplicationCannotCallRemoveMethodOnNonDependentScopedSessionEnterpriseBean(org.jboss.jsr299.tck.tests.implementation.enterprise.remove.EnterpriseBeanRemoveMethodTest) -- Key: GERONIMO-6035 URL: https://issues.apache.org/jira/browse/GERONIMO-6035 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6034) testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest)
testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest) - Key: GERONIMO-6034 URL: https://issues.apache.org/jira/browse/GERONIMO-6034 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6031) Remaining JCDI Failures
Remaining JCDI Failures --- Key: GERONIMO-6031 URL: https://issues.apache.org/jira/browse/GERONIMO-6031 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: David Blevins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-763) "Source not found" message when debugging a project
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058089#comment-13058089 ] Jarek Gawor commented on GERONIMODEVTOOLS-763: -- There are really 2 problems here. 1) The Eclipse can sometimes compute the source paths too early - before the projects are deployed to the server. Here's the call trace Eclipse requests to compute the source paths too early: at rg.apache.geronimo.st.v30.core.GeronimoSourcePathComputerDelegate.computeSourceContainers(GeronimoSourcePathComputerDelegate.java:63) at org.eclipse.debug.internal.core.sourcelookup.SourcePathComputer.computeSourceContainers(SourcePathComputer.java:69) at org.eclipse.debug.core.sourcelookup.containers.DefaultSourceContainer.createSourceContainers(DefaultSourceContainer.java:112) at org.eclipse.debug.core.sourcelookup.containers.CompositeSourceContainer.getSourceContainers(CompositeSourceContainer.java:129) at org.eclipse.debug.core.sourcelookup.containers.CompositeSourceContainer.findSourceElements(CompositeSourceContainer.java:46) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupParticipant.findSourceElements(AbstractSourceLookupParticipant.java:67) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector$SourceLookupQuery.run(AbstractSourceLookupDirector.java:141) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.doSourceLookup(AbstractSourceLookupDirector.java:490) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.getSourceElement(AbstractSourceLookupDirector.java:758) at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.lookup(SourceLookupFacility.java:148) at org.eclipse.debug.ui.DebugUITools.lookupSource(DebugUITools.java:777) at org.eclipse.jdt.internal.debug.ui.JavaDebugOptionsManager.getProblem(JavaDebugOptionsManager.java:577) at org.eclipse.jdt.internal.debug.ui.breakpoints.SuspendOnCompilationErrorListener.breakpointHit(SuspendOnCompilationErrorListener.java:67) at org.eclipse.jdt.internal.debug.core.breakpoints.BreakpointListenerManager$JavaBreakpointListenerProxy.breakpointHit(BreakpointListenerManager.java:135) at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin$HitNotifier.run(JDIDebugPlugin.java:644) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin$AbstractNotifier.notifyListeners(JDIDebugPlugin.java:466) at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin$HitNotifier.notifyHit(JDIDebugPlugin.java:658) at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin.fireBreakpointHit(JDIDebugPlugin.java:407) at org.eclipse.jdt.internal.debug.core.model.JDIThread.handleSuspendForBreakpoint(JDIThread.java:1131) at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.suspend(JavaBreakpoint.java:363) at org.eclipse.jdt.internal.debug.core.breakpoints.JavaExceptionBreakpoint.handleBreakpointEvent(JavaExceptionBreakpoint.java:348) at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.handleEvent(JavaBreakpoint.java:288) at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:155) at org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:104) at org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:250) 2) Once Eclipse computes the source paths, it doesn't seems to re-compute them anymore. That causes a problem when deploying & debugging another project in the same session. > "Source not found" message when debugging a project > --- > > Key: GERONIMODEVTOOLS-763 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > Under certain circumstances one can see "Source not found" message while > debugging a project that exists in the workspace and is deployed to the > server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-763) "Source not found" message when debugging a project
"Source not found" message when debugging a project --- Key: GERONIMODEVTOOLS-763 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-763 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Under certain circumstances one can see "Source not found" message while debugging a project that exists in the workspace and is deployed to the server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reopened GERONIMODEVTOOLS-759: -- There are two big (but related) problems with this code right now: 1) the bundle ids cannot not be cached on disk (since server restart might change them), and 2) the bundle ids need to be re-synchronized each time server starts up. For 1) doing memory only cache should be ok and for 2) need some api to lookup bundle id based on the bundle symbolic name and version. > 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: Yi Xiao > Labels: OSGI, bundle > Fix For: 3.0 > > Attachments: OSGIBundleDeploy.patch, > OSGIBundleDeploy_changeAPI.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-5674) Dojo related improvement.
[ https://issues.apache.org/jira/browse/GERONIMO-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057881#comment-13057881 ] Shawn Jiang commented on GERONIMO-5674: --- This JIRA has been closed, could you open a new JIRA for this issue ? -- Shawn > Dojo related improvement. > - > > Key: GERONIMO-5674 > URL: https://issues.apache.org/jira/browse/GERONIMO-5674 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2.2, 3.0 >Reporter: Shawn Jiang >Assignee: Shawn Jiang > Fix For: 3.0 > > Attachments: dojo.7z, dojoOptmize.patch, dojoOptmize_css_5674.patch, > dojoOptmize_hidenTreeNodeIcon_5674.patch > > > We need to consider > A, to upgrade to dojo 1.5 because dojo 1.5 has remarkably performance > increase. > B, According to instruction in article[1], we could make a dojo customized > build to > B-1, reduce the size current dojo package shipped in geronimo. > B-2, increase the dojo lib loading speed for current geronimo web admin > console. > [1]http://www.ibm.com/developerworks/web/library/wa-aj-custom/index.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5674) Dojo related improvement.
[ https://issues.apache.org/jira/browse/GERONIMO-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMO-5674: -- Attachment: dojoOptmize_hidenTreeNodeIcon_5674.patch Hidden the dojo's default treeLeafNode icon > Dojo related improvement. > - > > Key: GERONIMO-5674 > URL: https://issues.apache.org/jira/browse/GERONIMO-5674 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2.2, 3.0 >Reporter: Shawn Jiang >Assignee: Shawn Jiang > Fix For: 3.0 > > Attachments: dojo.7z, dojoOptmize.patch, dojoOptmize_css_5674.patch, > dojoOptmize_hidenTreeNodeIcon_5674.patch > > > We need to consider > A, to upgrade to dojo 1.5 because dojo 1.5 has remarkably performance > increase. > B, According to instruction in article[1], we could make a dojo customized > build to > B-1, reduce the size current dojo package shipped in geronimo. > B-2, increase the dojo lib loading speed for current geronimo web admin > console. > [1]http://www.ibm.com/developerworks/web/library/wa-aj-custom/index.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Fwd: Travel Assistance applications now open for ApacheCon NA 2011
I'm behind on my community@ email, I guess... FYI. Begin forwarded message: > From: "Gavin McDonald" > Date: June 6, 2011 4:01:40 AM EDT > To: > Subject: Travel Assistance applications now open for ApacheCon NA 2011 > Reply-To: commun...@apache.org > Reply-To: > > The Apache Software Foundation (ASF)'s Travel Assistance Committee (TAC) is > now accepting applications for ApacheCon North America 2011, 7-11 November > in Vancouver BC, Canada. > > The TAC is seeking individuals from the Apache community at-large --users, > developers, educators, students, Committers, and Members-- who would like to > attend ApacheCon, but need some financial support in order to be able to get > there. There are limited places available, and all applicants will be scored > on their individual merit. > > Financial assistance is available to cover flights/trains, accommodation and > entrance fees either in part or in full, depending on circumstances. > However, the support available for those attending only the BarCamp (7-8 > November) is less than that for those attending the entire event (Conference > + BarCamp 7-11 November). The Travel Assistance Committee aims to support > all official ASF events, including cross-project activities; as such, it may > be prudent for those in Asia and Europe to wait for an event geographically > closer to them. > > More information can be found at http://www.apache.org/travel/index.html > including a link to the online application and detailed instructions for > submitting. > > Applications will close on 8 July 2011 at 22:00 BST (UTC/GMT +1). > > We wish good luck to all those who will apply, and thank you in advance for > tweeting, blogging, and otherwise spreading the word. > > Regards, > The Travel Assistance Committee > > > - > To unsubscribe, e-mail: community-unsubscr...@apache.org > For additional commands, e-mail: community-h...@apache.org >
Re: [jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
unsubscribe
[jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-762: - Description: The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: geronimo-devtools-nightly-repo people.apache.org.username people.apache.org.password Thank Janet for helping me test to upload the devtools onto the apache site. was: The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: geronimo-devtools-nightly-repo people.apache.org.username people.apache.org.password > GEP needs a nightly builds repositary > - > > Key: GERONIMODEVTOOLS-762 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 > Project: Geronimo-Devtools > Issue Type: Wish > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Yi Xiao >Assignee: Yi Xiao > Labels: build, gep,, nightly > Attachments: gep_nightly_build.patch > > > The GEP had a nightly build repo before(refer to: > http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), > but it does not work now. So, I thought we should set up a environment to > redo it. > I've attached a patch to resolve the issue temporally. If you want to test it > in your local environment, should add below content to your maven's > settings.xml file: > > geronimo-devtools-nightly-repo > people.apache.org.username > people.apache.org.password > > Thank Janet for helping me test to upload the devtools onto the apache site. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6012) Fail to build restfulorder-javaee6 sample
[ https://issues.apache.org/jira/browse/GERONIMO-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-6012. -- Resolution: Invalid > Fail to build restfulorder-javaee6 sample > - > > Key: GERONIMO-6012 > URL: https://issues.apache.org/jira/browse/GERONIMO-6012 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: sample apps >Affects Versions: 3.0 > Environment: JDK: ibm jdk SR9-Fp1 >Reporter: viola.lu >Priority: Minor > Fix For: 3.0 > > > 1.Run mvn clean install under restfulorder-javaee6 > 2.Get "Can't package plugin" error -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Release Connector/Transaction components
On Thu, Jun 30, 2011 at 8:50 AM, jlmonteiro wrote: > Hi devs, > > We want to release Apache OpenEJB 3.2.0 but we are currently depending on > 2.2-SNAPSHOT. > Is it possible to get those 2 modules released? Hi, It's been a while since I was more active wrt Geronimo and there's a chance to change it - I may run the release process if no one objects. I've already discussed the matter with dblevins, so I'm pretty much aware what's needed, but if there's an official document I should be following for successful release I'd appreciate being pointed out. Jacek -- Jacek Laskowski Java EE, functional languages and IBM WebSphere - http://blog.japila.pl Warszawa JUG conference = Confitura (formerly Javarsovia) :: http://confitura.pl
[jira] [Commented] (GERONIMO-6030) Server can not shutdown using shutdown script
[ https://issues.apache.org/jira/browse/GERONIMO-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057721#comment-13057721 ] Rex Wang commented on GERONIMO-6030: commit to trunk at revision: 1141458 because the shutdown car bundle is not resolved > Server can not shutdown using shutdown script > - > > Key: GERONIMO-6030 > URL: https://issues.apache.org/jira/browse/GERONIMO-6030 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: commands >Affects Versions: 3.0 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 3.0 > > > says: "Main not found" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6030) Server can not shutdown using shutdown script
[ https://issues.apache.org/jira/browse/GERONIMO-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6030. Resolution: Fixed > Server can not shutdown using shutdown script > - > > Key: GERONIMO-6030 > URL: https://issues.apache.org/jira/browse/GERONIMO-6030 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: commands >Affects Versions: 3.0 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 3.0 > > > says: "Main not found" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057711#comment-13057711 ] Yi Xiao commented on GERONIMODEVTOOLS-762: -- The latest build has been upload to the site: http://apache.org/dist/geronimo/eclipse/nightly Can test it though eclipse's installation. > GEP needs a nightly builds repositary > - > > Key: GERONIMODEVTOOLS-762 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 > Project: Geronimo-Devtools > Issue Type: Wish > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Yi Xiao >Assignee: Yi Xiao > Labels: build, gep,, nightly > Attachments: gep_nightly_build.patch > > > The GEP had a nightly build repo before(refer to: > http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), > but it does not work now. So, I thought we should set up a environment to > redo it. > I've attached a patch to resolve the issue temporally. If you want to test it > in your local environment, should add below content to your maven's > settings.xml file: > > geronimo-devtools-nightly-repo > people.apache.org.username > people.apache.org.password > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao reassigned GERONIMODEVTOOLS-762: Assignee: Yi Xiao > GEP needs a nightly builds repositary > - > > Key: GERONIMODEVTOOLS-762 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 > Project: Geronimo-Devtools > Issue Type: Wish > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Yi Xiao >Assignee: Yi Xiao > Labels: build, gep,, nightly > Attachments: gep_nightly_build.patch > > > The GEP had a nightly build repo before(refer to: > http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), > but it does not work now. So, I thought we should set up a environment to > redo it. > I've attached a patch to resolve the issue temporally. If you want to test it > in your local environment, should add below content to your maven's > settings.xml file: > > geronimo-devtools-nightly-repo > people.apache.org.username > people.apache.org.password > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-762: - Attachment: gep_nightly_build.patch > GEP needs a nightly builds repositary > - > > Key: GERONIMODEVTOOLS-762 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 > Project: Geronimo-Devtools > Issue Type: Wish > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Yi Xiao > Labels: build, gep,, nightly > Attachments: gep_nightly_build.patch > > > The GEP had a nightly build repo before(refer to: > http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), > but it does not work now. So, I thought we should set up a environment to > redo it. > I've attached a patch to resolve the issue temporally. If you want to test it > in your local environment, should add below content to your maven's > settings.xml file: > > geronimo-devtools-nightly-repo > people.apache.org.username > people.apache.org.password > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-762: - Description: The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: geronimo-devtools-nightly-repo people.apache.org.username people.apache.org.password was:The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. > GEP needs a nightly builds repositary > - > > Key: GERONIMODEVTOOLS-762 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 > Project: Geronimo-Devtools > Issue Type: Wish > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Yi Xiao > Labels: build, gep,, nightly > Attachments: gep_nightly_build.patch > > > The GEP had a nightly build repo before(refer to: > http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), > but it does not work now. So, I thought we should set up a environment to > redo it. > I've attached a patch to resolve the issue temporally. If you want to test it > in your local environment, should add below content to your maven's > settings.xml file: > > geronimo-devtools-nightly-repo > people.apache.org.username > people.apache.org.password > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-762: - Summary: GEP needs a nightly builds repositary (was: GEP needs a nightly build repositary) > GEP needs a nightly builds repositary > - > > Key: GERONIMODEVTOOLS-762 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 > Project: Geronimo-Devtools > Issue Type: Wish > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Yi Xiao > Labels: build, gep,, nightly > > The GEP had a nightly build repo before(refer to: > http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), > but it does not work now. So, I thought we should set up a environment to > redo it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-762) GEP needs a nightly build repositary
GEP needs a nightly build repositary Key: GERONIMODEVTOOLS-762 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-728) The original geronimo deployment plan will be cleaned when importing an existing EAR project
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang resolved GERONIMODEVTOOLS-728. Resolution: Fixed Fix Version/s: 3.0 3.0-M2 fixed at revision: 1141445 > The original geronimo deployment plan will be cleaned when importing an > existing EAR project > > > Key: GERONIMODEVTOOLS-728 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-728 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: helios jee sr1 >Reporter: Forrest Xia > Fix For: 3.0-M2, 3.0 > > Attachments: corbahellobean_ejb_ear.ear > > > When importing an existing EAR into eclipse, if selecting geronimo server as > the target runtime, the original geronimo deployment descriptor will be > flushed. > For example, the plan in the ear file is like this: > > >xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"; > xmlns:bp="http://www.osgi.org/xmlns/blueprint/v1.0.0"; > > xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0"; > xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"; > xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"; > xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"; > xmlns:jaspi="http://geronimo.apache.org/xml/ns/geronimo-jaspi"; > xmlns:log="http://geronimo.apache.org/xml/ns/loginconfig-2.0"; > xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2"; > xmlns:ns5="http://geronimo.apache.org/xml/ns/j2ee/ejb/openejb-2.0"; > xmlns:pers="http://java.sun.com/xml/ns/persistence"; > xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"; > xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"; > xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1";> > > > default > corbahellobean_ejb > 1.0 > car > > > > > HelloEJBRemote > HelloEJBRemote > IOR3 > > > > After import, the deployment descriptor will be flushed like this: > >xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"; > xmlns:bp="http://www.osgi.org/xmlns/blueprint/v1.0.0"; > > xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0"; > xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"; > xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"; > xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"; > xmlns:jaspi="http://geronimo.apache.org/xml/ns/geronimo-jaspi"; > xmlns:log="http://geronimo.apache.org/xml/ns/loginconfig-2.0"; > xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2"; > xmlns:ns5="http://geronimo.apache.org/xml/ns/j2ee/ejb/openejb-2.0"; > xmlns:pers="http://java.sun.com/xml/ns/persistence"; > xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"; > xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"; > xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1";> > > > default > corbahellobean_ejb > 1.0 > car > > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6030) Server can not shutdown using shutdown script
Server can not shutdown using shutdown script - Key: GERONIMO-6030 URL: https://issues.apache.org/jira/browse/GERONIMO-6030 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: commands Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 says: "Main not found" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6027) fail to create BIO HTTPS connector for Tomcat using admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shenghao Fang reassigned GERONIMO-6027: --- Assignee: Shenghao Fang > fail to create BIO HTTPS connector for Tomcat using admin console > - > > Key: GERONIMO-6027 > URL: https://issues.apache.org/jira/browse/GERONIMO-6027 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console, Tomcat >Reporter: Chi Runhua >Assignee: Shenghao Fang >Priority: Minor > > Tried to create a BIO https connector using admin console, and input all > required fields, then click save. > The connector fails to start. > 2011-06-29 15:31:47,433 WARN [ConnectorGBean] test_BIOHTTPS connector failed > 2011-06-29 15:31:47,433 ERROR [GBeanInstanceState] Error while starting; > GBean is now in the FAILED state: > abstractName="org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car,j2eeType=GBean,name=test_BIOHTTPS" > org.apache.xbean.recipe.ConstructionException: Error creating gbean of class: > org.apache.geronimo.tomcat.connector.Https11ConnectorGBean, attempting to set > nonexistent properties: [clientAuth] > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:955) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:567) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.tomcat.connector.Https11Protocol$$EnhancerByCGLIB$$c056c043.startRecursive() > at > org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorPortlet.java:152) > at > org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:117) > at > org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:84) > at > org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:112) > at > org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:359) > at > org.apache.pluto.container.driver.PortletServlet.doPost(PortletServlet.java:267) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:581) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:518) > at > org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) > at > org.apache.pluto.driver.container.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:101) > at > org.apache.pluto.container.impl.PortletContainerImpl.doAction(PortletContainerImpl.java:251) > at > org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:135) > at > org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:205) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > org.apache.geronimo.console.filter.RedirectByHashFilter.doFilter(RedirectByHashFilter.java:116) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at > org.apache.geronimo.con
[jira] [Updated] (GERONIMO-5678) Derby NetworkServerControl with credentials improvement for Geronimo trunk
[ https://issues.apache.org/jira/browse/GERONIMO-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang updated GERONIMO-5678: Fix Version/s: 3.0.1 > Derby NetworkServerControl with credentials improvement for Geronimo trunk > -- > > Key: GERONIMO-5678 > URL: https://issues.apache.org/jira/browse/GERONIMO-5678 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 3.0 >Reporter: Forrest Xia >Assignee: Han Hong Fang >Priority: Minor > Fix For: 3.0.1 > > > We need the fix of GERONIMO-4296 into Geronimo trunk. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6024) support dd schema validation when deploy web app
[ https://issues.apache.org/jira/browse/GERONIMO-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057665#comment-13057665 ] Rex Wang commented on GERONIMO-6024: Currently, the patch only validate the web.xml defined by schema. If a old web.xml defined by dtd is in, the deployment will fail. So, we need simply check the web.xml to determine if it should be validated. Any comments? > support dd schema validation when deploy web app > > > Key: GERONIMO-6024 > URL: https://issues.apache.org/jira/browse/GERONIMO-6024 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 3.0 > > Attachments: GERONIMO-6024.patch > > > Now we don't validate deployment descriptor against its schema when deploy > the web app. we must support it.. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Release geronimo-el and geronimo-jaxws spec package
Another dependent package is also required to release first, geronimo-stax-api_1.2_spec 2011/6/28 Ivan > Hi, we just got some fixes for geronimo-el and geronimo-jaxws-2.2 spec > package in the past, I am thinking to do those two package release soon if > no objection. > > -- > Ivan > -- Ivan
