[
https://issues.apache.org/jira/browse/CXF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847463#comment-13847463
]
Sergey Beryozkin commented on CXF-4199:
---------------------------------------
Hi Andriy, brilliant thanks;
FYI, it has not been urgent, we appreciate that the contributors are busy with
their own work :-).
As far as the patch is concerned, I applied it with only one modification, the
client will itself set up a qname if it has not been set, for proxies it is
"{packagename}Classname".
The other, unrelated change, was to the Spring scanner, to make it thread-safe.
I guess we are mostly done with this work, please play with
http://sourceforge.net/projects/extcos/files/releases/0.4b/
(or something similarly simple/light-weight)
in the next couple of months, whenever you can get a chance really, as it is
not urgent, and see if we can optionally use that to offer a non-Spring scanner
support. If it proves in the end it is too complex/difficult to do then we can
limit it all to Spring endpoints configured in XML with CXF namespace handlers
only, but perhaps we can push it a bit further :-)
Please don't hesitate to handle other JIRA(s) next if you prefer
Many 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,
> patch-jaxrs-client-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.4#6159)
