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 Sun, 24 Nov 2013 21:42:35 GMT

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

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

Hi Andriy,

In the original code example, the idea is not to duplicate but delegate to Spring to auto-discover
both root resource and providers and then add them to the CXF factory bean, i.e, initiate
some Spring related class path scanner, get it discover root/providers, and add them.    

Do you reckon it is possible simply do

<jaxrs:server id="bookservice" address="/"/>

and rely on Spring to auto-discover ? I'm not sure it is.
Note it is also possible to have multiple jaxrs:server endpoints within a single context,
so restricting at the endpoint level can be useful. 
I'm not sure about introducing multiple bus extensions with each of them responsible for discovering
different types of JAX-RS 'participants'. I'd rather have a single config property and get
everything discovered.

Also, I don't mind relying on Spring and also Blueprint specific mechanisms when either Spring
or Blueprint is available. But I'd also like to be able to declare CXFNonSpringJaxrsServlet
and only point to a package to be scanned, and that is it. We'd then have a single solution
working everywhere. But may be we should just make Spring auto-discovery support wired in
first

 


 

> 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
>
> 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