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

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

I verified my app finally boots just fine on wildfly 18.0.0.Beta1 without my previous workaround.

Thanks Ronald, James, R, Marek and everyone else who has worked on this!

> 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, 16.0.0.Beta1
>            Reporter: Matt Drees
>            Assignee: Ronald Sigal
>            Priority: Major
>             Fix For: 18.0.0.Beta1
>
>
> 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
(v7.13.5#713005)