cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-4199) Support class-scanning for discovering JAX-RS providers
Date Wed, 27 Nov 2013 17:28:36 GMT

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

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

Hi Andriy

I think it is exactly what I'm looking for, thanks for getting this project moving. Looks
promising indeed, in fact, now that I think about it, we can actually (later on) introduce
CXF annotation markers for in/out/inFault/outFault/feature elements and basically have everything
auto-discovered (for simple cases), possibly we can get that done for all of CXF endpoints,
so we will just have 
{code:xml}
<jaxrs:server address="/rs" base-packages=""/>
{code}

Some comments on the patch: 
- lets also discover root resources, if a Class has @Path then it is a root resource/serviceBean
- can we support empty base-packages - this will simply enable the auto-discovery of everything,
I guess we will need to exclude 'org.apache.cxf.jaxrs/**/*.class' in this case for now - if
the exclusions are tricky to manage then lets not do it
- this can be done later, in another patch, but lets do the same for jaxrs;client, the only
difference there is that we will pick up the very first Class with @Path and set it as jaxrs:client
serviceClass attribute, the providers will be found exactly the same way as on the server


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