[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941006#comment-13941006
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Hi Andriy, the smiley is nice, yeah :-)
Sure, making CDI servlet generic can help; lets keep exploring this path. I
thought that may be we can have @Named beans right in that beans.xml, and it
can be either application beans or service/provider beans, that can cover most
of the customization cases. For JAX-RS we can have some sort of the
customization with Application - but this can be limited.
We have the extra customization for the endpoints, like transportId,
properties, etc. We can review it later on. If we can customize service and
provider beans then I guess we'd be nearly done...
Thanks, Sergey
> 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)
