[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=13251188#comment-13251188 ] 

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

Hey [~swd847] I'm bumping into this again. (After initially trying to port my app from jboss 7.1 to wildfly 8 a few years ago and failing, I'm now trying again to port it, but to wildfly 10 now).

I'm sad that your change was backed out. So I'm wondering about other ways to fix this.

Would it be reasonable to change Resteasy such that, instead of always adding the Application scope annotation to the provider's AnnotatedType, it chose either Dependent or Application, depending on whether the class was proxyable?

If so I'd be happy to contribute that.

> 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
>          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 was sent by Atlassian JIRA
(v6.4.11#64026)