[jboss-jira] [JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

[Stuart Douglas (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12947147#comment-12947147 ] 

Stuart Douglas commented on WFLY-2859:
--------------------------------------

[~jharting] what do you think about modifying the Resteasy CDI integration to not make beans request scoped any more, and instead just create an instance directly and destroy it at the end of the request using a listener (or using some other hook in Resteasy)? 

As it is this also causes some performance problems, Resteasy with CDI is noticeably slower.
                
> Treating all JAX-RS components as CDI Beans has some negative consequences
> --------------------------------------------------------------------------
>
>                 Key: WFLY-2859
>                 URL: https://issues.jboss.org/browse/WFLY-2859
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: CDI / Weld, REST
>    Affects Versions: 8.0.0.CR1
>            Reporter: Matt Drees
>            Assignee: Stuart Douglas
>
> It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans.  This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class.
> See the forum link for a specific instance of this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira