[
https://issues.apache.org/jira/browse/CXF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842568#comment-13842568
]
Sergey Beryozkin commented on CXF-4199:
---------------------------------------
Hi Andrei,
we can have as many utility methods in this wrapper as we like, one method
returning classes, another one - instances;
IMHO, in case of the server spring support, we'd rather have the wrapper (as
all the Spring code which can handle it will be there) creating instances for
us, JAXRSServerFactoryBean.setResourceClasses uses CXF utility class for
creating instances, so it can accidentally bypass some of Spring specific
subtleties.
But for the client, we'd need your option, because jaxrs:client needs a class
argument to create a proxy, but can accept provider instances, so in this case
we'll do exactly what you suggest.
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
>
>
> 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)
