December 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-855) Error while catching NonexistentConversationException with Seam Faces/Catch

by Brian Leathem (JIRA)

Error while catching NonexistentConversationException with Seam Faces/Catch --------------------------------------------------------------------------- Key: WELD-855 URL: https://issues.jboss.org/browse/WELD-855 Project: Weld Issue Type: Bug Environment: Glassfish 3.1 M2 (b41), weld 1.1 patched with Stuart's WELD-846 patch. Reporter: Brian Leathem I have a Faces app, with the exception handler: void conversationExpired(@Handles CaughtException<NonexistentConversationException> t) {...} When I pull up a URL with an invalid cid, I get the stacktrace below. (copied from SEAMCATCH-46) Stacktrace: --------------- java.lang.RuntimeException: Exception invoking method [conversationExpired] on object [ca.triumf.mis.qms.workrequest.jsf.exception.ExceptionCatchHandler@264d6a2c], using arguments [org.jboss.seam.exception.control.CaughtException@24758259] at org.jboss.seam.solder.reflection.Reflections.invokeMethod(Reflections.java:547) at org.jboss.seam.solder.reflection.Reflections.invokeMethod(Reflections.java:458) at org.jboss.seam.solder.reflection.annotated.InjectableMethod.invoke(InjectableMethod.java:189) at org.jboss.seam.exception.control.HandlerMethodImpl.notify(HandlerMethodImpl.java:189) at org.jboss.seam.exception.control.ExceptionHandlerDispatch.executeHandlers(ExceptionHandlerDispatch.java:129) 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222) at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:632) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:619) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:613) at org.jboss.seam.faces.exception.CatchExceptionHandler.handle(CatchExceptionHandler.java:81) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:113) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:409) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1534) at org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatcher.java:787) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:649) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:483) at org.apache.catalina.core.ApplicationDispatcher.doDispatch(ApplicationDispatcher.java:454) at org.apache.catalina.core.ApplicationDispatcher.dispatch(ApplicationDispatcher.java:350) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:300) at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.java:465) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:253) at com.sun.web.security.RealmAdapter.invokeAuthenticateDelegate(RealmAdapter.java:1192) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:551) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:623) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98) at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.IllegalStateException: Unable to load current conversations from the associated request, something went badly wrong when associate() was called at org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413) at org.jboss.weld.jsf.ConversationAwareViewHandler.getActionURL(ConversationAwareViewHandler.java:91) at com.sun.faces.application.view.MultiViewHandler.getRedirectURL(MultiViewHandler.java:381) at javax.faces.application.ViewHandlerWrapper.getRedirectURL(ViewHandlerWrapper.java:204) at javax.faces.application.ViewHandlerWrapper.getRedirectURL(ViewHandlerWrapper.java:204) at org.jboss.weld.jsf.ConversationAwareViewHandler.getRedirectURL(ConversationAwareViewHandler.java:134) at com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:166) at org.jboss.seam.faces.event.SeamPreNavigationHandler.handleNavigation(SeamPreNavigationHandler.java:77) at ca.triumf.mis.qms.workrequest.jsf.exception.ExceptionCatchHandler.conversationExpired(ExceptionCatchHandler.java:27) 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.jboss.seam.solder.reflection.Reflections.invokeMethod(Reflections.java:535) ... 59 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

13
28
0 / 0

[JBoss JIRA] (CDITCK-258) @MessageDriven bean ProcessInjectionTarget event

by David Blevins (Created) (JIRA)

@MessageDriven bean ProcessInjectionTarget event ------------------------------------------------ Key: CDITCK-258 URL: https://issues.jboss.org/browse/CDITCK-258 Project: CDI TCK Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Tests Reporter: David Blevins v1.0 s11.5.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] (CDITCK-254) MessageDriven Bean @Inject tests

by David Blevins (Created) (JIRA)

MessageDriven Bean @Inject tests -------------------------------- Key: CDITCK-254 URL: https://issues.jboss.org/browse/CDITCK-254 Project: CDI TCK Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Tests Reporter: David Blevins v1.0 s1.2.2 The container performs dependency injection on all session and message-driven bean instances, even those which are not contextual instances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] (CDITCK-255) @MessageDriven bean Request Context tests

by David Blevins (Created) (JIRA)

@MessageDriven bean Request Context tests ----------------------------------------- Key: CDITCK-255 URL: https://issues.jboss.org/browse/CDITCK-255 Project: CDI TCK Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Tests Reporter: David Blevins v1.0 s6.7.1 during any remote method invocation of any EJB, during any asynchronous method invocation of any EJB, during any call to an EJB timeout method and during message delivery to any EJB message-driven bean -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] (CDITCK-256) @MessageDriven bean Application context tests

by David Blevins (Created) (JIRA)

@MessageDriven bean Application context tests --------------------------------------------- Key: CDITCK-256 URL: https://issues.jboss.org/browse/CDITCK-256 Project: CDI TCK Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Tests Reporter: David Blevins v1.0 s6.7.3 "Application context lifecycle" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] (WELD-1014) Weld does not work with Oracle WebLogic Server 11g (10.3.5)

by George Gastaldi (Created) (JIRA)

Weld does not work with Oracle WebLogic Server 11g (10.3.5) ----------------------------------------------------------- Key: WELD-1014 URL: https://issues.jboss.org/browse/WELD-1014 Project: Weld Issue Type: Bug Reporter: George Gastaldi Weblogic doesn´t seem to run Weld. When configuring the WeldListener, I get the following exception: {code:java} java.lang.IllegalStateException: Singleton is not set at org.jboss.weld.bootstrap.api.helpers.IsolatedStaticSingletonProvider$IsolatedStaticSingleton.get(IsolatedStaticSingletonProvider.java:52) at org.jboss.weld.Container.instance(Container.java:54) at org.jboss.weld.jsf.WeldPhaseListener.instance(WeldPhaseListener.java:161) at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:98) at org.jboss.weld.jsf.WeldPhaseListener.beforePhase(WeldPhaseListener.java:85) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:508) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

6
14
0 / 0

[JBoss JIRA] (WELD-1030) Change the ProxyServices SPI to allow the container to determine the correct ProtectionDomain to use for the proxy

by Stuart Douglas (Created) (JIRA)

Change the ProxyServices SPI to allow the container to determine the correct ProtectionDomain to use for the proxy ------------------------------------------------------------------------------------------------------------------- Key: WELD-1030 URL: https://issues.jboss.org/browse/WELD-1030 Project: Weld Issue Type: Feature Request Reporter: Stuart Douglas This involves an SPI change, so cannot be done as part of a point release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] (CDITCK-252) Implement tests for CDI-97

by Martin Kouba (Created) (JIRA)

Implement tests for CDI-97 -------------------------- Key: CDITCK-252 URL: https://issues.jboss.org/browse/CDITCK-252 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 1.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] (WELD-1027) @Inject'ed protected base class member access problem

by Brendan Healey (Created) (JIRA)

@Inject'ed protected base class member access problem ----------------------------------------------------- Key: WELD-1027 URL: https://issues.jboss.org/browse/WELD-1027 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Environment: Glassfish 3.1.1 Chrome browser. Reporter: Brendan Healey In the following code I'm trying to inject a SessionScoped bean into a stateless EJB, but I want to do the @Inject in an abstract base class of the EJB. According to the CDI spec it seems to suggest that this should work: "4.2. Inheritance of member-level metadata Suppose a class X is extended directly or indirectly by the bean class of a managed bean or session bean Y. If X declares an injected field x then Y inherits x." What happens is that I can access the inherited protected member sessionView from TestEjb, but not from code within the base class. When I say "can access", I mean that the injected member is accessible at runtime and is not null. @Named @ViewAccessScoped public class JsfBean extends implements Serializable { @Inject private TestEjb ejb; SessionView s1 = ejb.getSessionViewChild(); // sessionView injected ok SessionView s2 = ejb.getSessionViewBase(); // s2 is null } @Named @SessionScoped public class SessionView implements Serializable {} @Stateless public class TestEjb extends BaseClass implements Serializable { public SessionView getSessionViewChild() { return sessionView; } } public abstract class BaseClass implements Serializable { @Inject protected SessionView sessionView; public SessionView getSessionViewBase() { return sessionView; } } What happens is that s1 is a valid SessionView reference, but s2 is null. It now turns out that if I change the access of sessionView in BaseClass to private, it works, but only if I clean & build before re-deployment. It will then consistently work - unless I change it back to protected, in which case it will consistently not work. I am using MyFaces CODI 1.0.1 in conjunction with Weld from Glassfish 3.1.1 (v20110404-1554). I am also using JDK 7u1. I reported this on the MyFaces mailing list but Gerhard said this looked like a weld issue. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] (CDITCK-250) Tests for @New session beans do not have @New injection points

by Jozef Hartinger (Created) (JIRA)

Tests for @New session beans do not have @New injection points -------------------------------------------------------------- Key: CDITCK-250 URL: https://issues.jboss.org/browse/CDITCK-250 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Jozef Hartinger Assignee: Martin Kouba Priority: Critical org.jboss.jsr299.tck.tests.implementation.enterprise.newBean.NewEnterpriseBeanTest and org.jboss.jsr299.tck.tests.implementation.enterprise.newBean.NewEnterpriseBeanICTest assume @New session beans to be created eagerly for each session bean. However, the specification says: {quote}The container discovers @New qualified beans by inspecting injection points other enabled beans.{quote} Proper injection points should be added for the tests to be valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2011