[ 
https://issues.apache.org/jira/browse/CXF-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846349#comment-13846349
 ] 

Sergey Beryozkin commented on CXF-4199:
---------------------------------------

Hi Andriy, I've applied your patch with minor modifications, thanks.

I've moved the scanner utility to org.apache.cxf.common.utils (for now), in 
addition to that package we also have org.apache.cxf.helpers, so I thought we'd 
not need a new package. 

Note that JAXRSServerFactoryBean is accumulating all the providers/resources so 
did minor optimizations based on that fact. 

The code will probably be nearly identical for jaxrs:client, the only 
difference that if we find many roots then we should probably throw an 
exception.

I'd like to suggest that we resolve the issue after jaxrs:client is taken care 
of, we can have another issue dedicated to finding a light-weight non-Spring 
class scanner support, and we can validate that new support by pushing the 
scanning support directly to JAXRSServerFactoryBean.

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)

Reply via email to