You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2017/04/07 14:51:41 UTC
[jira] [Updated] (CXF-7324) [cdi] allow to define applications
getClasses by declaration on resources
[ https://issues.apache.org/jira/browse/CXF-7324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Romain Manni-Bucau updated CXF-7324:
------------------------------------
Priority: Minor (was: Major)
> [cdi] allow to define applications getClasses by declaration on resources
> -------------------------------------------------------------------------
>
> Key: CXF-7324
> URL: https://issues.apache.org/jira/browse/CXF-7324
> Project: CXF
> Issue Type: New Feature
> Reporter: Romain Manni-Bucau
> Priority: Minor
>
> Idea is to reverse the Application pattern by having an "empty" application (ie scanning by spec) and mark a resource as belonging to the application:
> {code}
> @org.apache.cxf.rs.cdi.ApplicationType(MyApp.class)
> @Path("test")
> public class MyTestEndpointBelongsToMyAppApp {...}
> {code}
> Why is that useful? cause if you develop N applications (N > 1) using autoscanning but Application class to define the path (@ApplicationPath) and then merge them (packaging detail) then you will get 3 times the same deployment instead of 3 distincts applications.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)