[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919261#comment-13919261
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
In fact we can probably do
{code:java}
final BeanManager beanManager = CDI.current().getBeanManager();
CdiResourceExtension extension =
beanManager.getExtension(CdiResourceExtension.class);
if( extension != null ) {
extension.getBean().create();
}
{code}
where CDIResourceExtension an interface extending CDI Extension and implemented
by JAX-RS & JAX-WS extensions; assuming Weld can actually discover the
extension this way then we can have a completely reusable CDI Servlet helper
> 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)
