[ 
https://issues.jboss.org/browse/SEAM-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Porter updated SEAM-120:
------------------------------

      Fix Version/s: 3.1.0.CR1
    Forum Reference: 
http://seamframework.org/Community/WELD000052ErrorFollowingSeamSecurityIdentitylogout
  (was: 
http://seamframework.org/Community/WELD000052ErrorFollowingSeamSecurityIdentitylogout)

    
> WELD-000052 error following Seam Security identity.logout()
> -----------------------------------------------------------
>
>                 Key: SEAM-120
>                 URL: https://issues.jboss.org/browse/SEAM-120
>             Project: Seam 3 Distribution
>          Issue Type: Bug
>    Affects Versions: 3.1.0.Beta5
>         Environment: JBoss AS 7.0.2, JSF 2, CDI, Seam 3.1.0.Beta5.  
>            Reporter: Daniel Miklancic
>            Priority: Blocker
>             Fix For: 3.1.0.CR1
>
>
> After upgrading to Seam 3.1.0.Beta5, a simple, identity.logout() call 
> generates the following:
> Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 
> Cannot return null from a non-dependent producer method:  [method] @Produces 
> @RequestScoped protected 
> org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpSession()
>       at 
> org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:256)
>  [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
>       at 
> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:362)
>  [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
>       at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:122) 
> [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
>       at 
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99)
>  [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
>       at 
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:124)
>  [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
>       at 
> org.jboss.weld.proxies.HttpSession$1681475766$Proxy$_$$_WeldClientProxy.invalidate(HttpSession$1681475766$Proxy$_$$_WeldClientProxy.java)
>       at org.jboss.seam.security.IdentityImpl.logout(IdentityImpl.java:424) 
> [seam-security-3.1.0.Beta5.jar:]
>       at 
> org.jboss.seam.security.IdentityImpl$Proxy$_$$_WeldClientProxy.logout(IdentityImpl$Proxy$_$$_WeldClientProxy.java)
>  [seam-security-3.1.0.Beta5.jar:]
>       at 
> com.bp.cpr.pn.application.onepcoe.security.PortalSecurityManager.logout(PortalSecurityManager.java:153)
>  [classes:]
>       at 
> com.bp.cpr.pn.application.onepcoe.security.PortalSecurityManager$Proxy$_$$_WeldClientProxy.logout(PortalSecurityManager$Proxy$_$$_WeldClientProxy.java)
>  [classes:]
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [:1.6.0_29]
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
> [:1.6.0_29]
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  [:1.6.0_29]
>       at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_29]
>       at org.apache.el.parser.AstValue.invoke(AstValue.java:196) 
> [jbossweb-7.0.1.Final.jar:7.0.2.Final]
>       at 
> org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) 
> [jbossweb-7.0.1.Final.jar:7.0.2.Final]
>       at 
> org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43)
>  [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
>       at 
> org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) 
> [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
>       at 
> com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
>  [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT]
>       at 
> javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
>  [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
>       ... 29 more
> I have reviewed various WELD-000052 errors, but none seem to be related to 
> the HttpSession. Can such an error be caused by a new configuration that is 
> required with the new version of Seam that I may have overlooked? 

--
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

        
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues

Reply via email to