You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2017/08/07 05:29:00 UTC

[jira] [Commented] (OWB-1208) Unable to use Unmanaged with mixed CDI 2.0/1.1 bean archives

    [ https://issues.apache.org/jira/browse/OWB-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116067#comment-16116067 ] 

Romain Manni-Bucau commented on OWB-1208:
-----------------------------------------

Hi John, is it the case with not web components? Don't think unmanaged should work for servlets since cdi doesnt handle them at all in the spec and let the servlet container doing it.

> Unable to use Unmanaged with mixed CDI 2.0/1.1 bean archives
> ------------------------------------------------------------
>
>                 Key: OWB-1208
>                 URL: https://issues.apache.org/jira/browse/OWB-1208
>             Project: OpenWebBeans
>          Issue Type: Bug
>            Reporter: John D. Ament
>
> Take for instance the Apache CXF CDI Extension.  There's a `CXFCdiServlet` class which has no bean defining annotations, but has a valid CDI 1.1 [beans.xml|https://github.com/apache/cxf/blob/master/integration/cdi/src/main/resources/META-INF/beans.xml].  If I start OWB from a main that has CDI 2.0's trimmed bean archive, this servlet is not available as a CDI bean, and hence cannot be used within Unmanaged.
> I'm not sure if the solution is that it should be a CDI bean, or if Unmanaged should be able to look at non-beans.  This issue does not replicate on Weld 3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)