[
https://issues.apache.org/jira/browse/CXF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844724#comment-13844724
]
Sergey Beryozkin commented on CXF-4199:
---------------------------------------
Hi Andrei,
yes, I've been thinking about your earlier comment about initializing
JAXRSServerFactoryBean directly and missing on the auto-discovery, or Blueprint
Aries handlers. And few other other optimizations, to do with the discovery of
schema resources. May be we should push this code to the base factory in the
end, let me work on your patch in the next day or so, this week.
I checked Reflections, I thought it had may be too many deps, Extcos only
depends on ASM, and we can eventually may be also switch to
org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider
in Spring code which also depends on ASM. If you prefer to look more into it
now, please check Extcos & Reflections as two possible candidates.
The other possible thing to consider - update jaxrs:client to support the
auto-discovery.
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-all-packages.txt,
> patch-base-packages-discovery.txt, patch-classpath-scaner.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.4#6159)
