[
https://issues.apache.org/jira/browse/CXF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830698#comment-13830698
]
Andriy Redko commented on CXF-4199:
-----------------------------------
Hi Sergey,
I have spent some time to understand the scope of the issue (it's somehow
related to CXF-3725 in a way to make auto-discovery work in a generice way).
The option to have something like that (taken from CXF-3725)
{noformat}
<jaxrs:server id="bookservice" address="/"
scan-packages="org.apache.foo,org.apache.bar"/>
{noformat}
is quite interesting though in my opinion it duplicates a bit the Spring's way
to discover things using @ComponentScan. What I came up might look wrong but it
looks like this:
{noformat}
<jaxrs:server id="bookservice" address="/" auto-discovery="true"/>
{noformat}
The actual implementation is not a just a flag but context-dependent strategy:
SpringProvidersDiscovery() and ClasspathProvidersDiscovery().
SpringProvidersDiscovery will handle all discovered beans with @Provider
annotations while ClasspathProvidersDiscovery will handle all discovered
classes from classpath with @Provider annotations (+ we should provide
basePackages / baseClasses to limit the auto-discovery scope). What do you
think, is it feasible and make sense to you?
Thank you.
Andriy.
> 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)
