[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944877#comment-13944877
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Hi Andriy,
Right, I've learnt something new re Application :-). To be honest, I can only
think of the empty Application being used where no web.xml is available, to get
@ApplicationPath affecting the mappings... But I guess, in scope of working
with CDI/Weld, which provides the scanning capabilities, we can continue
supporting this option. Thanks for spotting this option.
Ok, then, where do we stand right now re the customizations ? I'd like to
propose that we actually explore the CDI way of injecting the properties.
For example, step1, can we get basic properties (no Named beans, but something
basic, String/etc) injected into BookStore resource ? I think once we do it we
then can figure out how to inject properties like transportId, etc, into server
factory beans
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)
