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

[Matt Drees (JIRA)]

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

Matt Drees commented on WFLY-2859:
----------------------------------

I wanted to mention another solution, but it'd require resteasy spi changes:

The ConstructorInjector/InjectorFactory interfaces are only given the implementation class to "instantiate". They are not given the type of interface the instantiated object will be referenced as (in my case, {{MessageBodyWriter}}).  If they were, CdiConstructor could pass the interface into the beanManager.getReference() call, and avoid the UnproxyableResolutionException. (I believe this could also help with EJB lookups).
                
> 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