[
https://issues.apache.org/jira/browse/CXF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833993#comment-13833993
]
Andriy Redko commented on CXF-4199:
-----------------------------------
Hi Sergey,
Thanks a lot for the feedback. You are very right, there is quite a potential
out there. If you don't mind, I would prefer not to do @Path resources
discovery as part of this issue and limit the scope to providers only (just to
stay with the JSR and this issue title). But I would happily tackle this
feature as well (just under another JIRA issue so we can keep it under control
as @Path is used much broadly). I will address empty base-packages to see what
we discover and what the impact is (aside from being taken long time).
The question I want to ask though is: many people (including myself) don't used
XML-based configuration for years now, mostly RuntimeDelegate /
JAXRSServerFactoryBean directly. With the work we have done so far, the
auto-discovery won't be possible in this cases. Do you see any benefit
addressing it as well?
What do you think?
Thanks.
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
> 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)
