cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-4199) Support class-scanning for discovering JAX-RS providers
Date Wed, 27 Nov 2013 22:02:36 GMT

    [ https://issues.apache.org/jira/browse/CXF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834204#comment-13834204
] 

Sergey Beryozkin commented on CXF-4199:
---------------------------------------

Hi Andriy

OK, lets do the root resource auto-discovery as part of https://issues.apache.org/jira/browse/CXF-3725;
as a side note I see both issues pretty much part of a single 'project', no much point to
auto-discover simple providers but still list equally basic root resources.
I believe Glassfish and JBoss would have a support for auto-discovering both types of the
resources, in addition to Application: it would have both the root resources & providers
packaged inside it, so the auto-discovery mechanism would pick up Application, and Application
will complete the initialization. The spec def talks about auto-discovering applications in
certain cases. We can also target Applications (only those containing JAX-RS Application Path
as part of 3725).

Re other cases where the discovery may be of help: I've been thinking that we'd have the tests
ready for Spring first, and then ask the question, what about Blueprint, your case with the
direct JAXRSServerFactoryBean as well as CXFNonSpringJaxrsServlet and may be at a later stage,
for CXF CDI JaxRs namespace support ? We can consider utilizing a Reflections project.

Thanks, Sergey    
 

> Support class-scanning for discovering JAX-RS providers 
> --------------------------------------------------------
>
>                 Key: CXF-4199
>                 URL: https://issues.apache.org/jira/browse/CXF-4199
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS
>            Reporter: Sergey Beryozkin
>         Attachments: patch-base-packages-discovery.txt
>
>
> With the search extensions module containing a provider the time has come to support
the optional class-scanning. Will help in cases when the providers are simple and no extra
configuration is expected. Post 2.6 though



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message