[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949307#comment-13949307
]
Andriy Redko commented on CXF-5576:
-----------------------------------
Hi Sergey,
Sounds very good. I just need couple of days to finish up with extension. The
examples I provided to you will work once I make the Application classes
discovery compliant with the specification (it is already in progress but not
completed yet). Also, I would like to share with you very important difference
between CDI and f.e. Spring: in CDI all beans are lazy and, generally, will be
discovered but will not be created. For example, if you have any CDI bean, it
won't be created till someone really needs it. That's where our CDI extension
comes into play: we tell the CDI container to create the beans we care about
(Application, services, providers). And it's by cascade initiates the injection
process. Without the extension, we have just a bunch of beans metadata sitting
around :-)
Thanks.
Andriy.
> Initital support for CDI integration
> ------------------------------------
>
> Key: CXF-5576
> URL: https://issues.apache.org/jira/browse/CXF-5576
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.0.0
> Reporter: Andriy Redko
> Assignee: Andriy Redko
> Labels: cdi
> Attachments: weld-one-jar.zip, weld-one-war.zip
>
>
> A per section 10.2.3 Context and Dependency Injection (CDI) of JAX-RS 2.0
> specification, in a product that supports CDI, the implementations MUST
> support the use of CDI-style Beans as root resource classes, providers and
> Application subclasses. Providers and Application subclasses MUST be
> singletons or use application scope.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
