cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-4199) Support class-scanning for discovering JAX-RS providers
Date Tue, 10 Dec 2013 11:34:08 GMT


Sergey Beryozkin commented on CXF-4199:

Hi Andriy, yes, it is very close, thanks. we need to encapsulate it a bit to make sure it
works without Spring, similar to this approach,

example, so that a call to ClassScanner works from Blueprint or any CXF code which needs the
resources scanning support, the no-op handler will be used for now in non-Spring cases; we
can of course start from putting it directly into core/spring, but the minor encapsulation
should do it. I can work with the patch and do few minor updates on it.

Hmm... Just spotted it, with this patch (or more precisely, this my idea) we lose the ability
to load classes with ApplicationContext. You were right, we have to keep the actual instantiation
out of the scanner, if we want to make it reusable across. Let me play a bit wit it 

Thanks, Sergey

> Support class-scanning for discovering JAX-RS providers 
> --------------------------------------------------------
>                 Key: CXF-4199
>                 URL:
>             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

View raw message