cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andriy Redko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-4199) Support class-scanning for discovering JAX-RS providers
Date Sat, 07 Dec 2013 17:04:35 GMT

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

Andriy Redko commented on CXF-4199:
-----------------------------------

Hi Sergey,

Sounds like a good plan to me. I will start with 1 to extract all necessary implementation
into ClassPathScanner.
The suggestion  I have would be to return Map<Annotation, List< Class < ? > >
instead of  Map<Annotation, List<Object>>: in case of Spring, classes will be
used to create respective beans, but often class is just enough, and could be created later
on (setResourceClasses( ... ) is a good example). Do you think it has sense?

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-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)

Mime
View raw message