You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2014/11/20 19:16:34 UTC
[jira] [Commented] (CXF-6112)
org.apache.cxf.jaxrs.impl.ResourceContextImpl#getResource should support a
custom ResourceProvider
[ https://issues.apache.org/jira/browse/CXF-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219697#comment-14219697 ]
Sergey Beryozkin commented on CXF-6112:
---------------------------------------
Hi Romain - I added ResourceContextProvider; for now it can be registered as an endpoint or bus property, I'd like to avoid getting into service factories, etc for now :-). Please experiment. The documentation is probably intentionally kept open to the interpretation, so I guess using CDI/etc creators is a possibility.
The main use case is really about initiaizing subresource classes when the application can not do it, I haven't seen a case of using it to create root resources ever being covered, and as such the info re life-cycles is somewhat confusing, may be it will be clarified in 2.1, etc...
Thanks
> org.apache.cxf.jaxrs.impl.ResourceContextImpl#getResource should support a custom ResourceProvider
> --------------------------------------------------------------------------------------------------
>
> Key: CXF-6112
> URL: https://issues.apache.org/jira/browse/CXF-6112
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.0.2
> Reporter: Romain Manni-Bucau
>
> Idea is to be able to plug easily CDI, Spring bean resolution/injections. So PerRequestResourceProvider shouldn't be hardcoded.
> Solution can be a kind of SPI in the message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)