Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Thu, 4 Dec 2014 14:15:12 +0000 (UTC)
From: "Mikhail S (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12750573.1414288875000.75757.1417702512568@Atlassian.JIRA>
In-Reply-To: <JIRA.12750573.1414288875000@Atlassian.JIRA>
References: <JIRA.12750573.1414288875000@Atlassian.JIRA>
 <JIRA.12750573.1414288875778@arcas>
Subject: [jira] [Commented] (CXF-6064) Improve WADL Generator Extensibility
 for ID generation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mikhail S commented on CXF-6064:
--------------------------------

Yes, it is the case when the resource locator is a JAXB bean. We currently annotate subresources with the @XmlRootElement while 3.0.3 is not released yet. 

Mikhail

> Improve WADL Generator Extensibility for ID generation
> ------------------------------------------------------
>
>                 Key: CXF-6064
>                 URL: https://issues.apache.org/jira/browse/CXF-6064
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS
>    Affects Versions: 3.0.1
>            Reporter: Mikhail S
>            Assignee: Sergey Beryozkin
>             Fix For: 3.1.0, 3.0.3
>
>
> WADLGenerator class is not extensible and prevents extensions for simple customizations.
> Example: We would like to use custom IDs on the resource and methods. The mechanism provided in CXF requires to either use {{@XmlRootElement}} or rely on the default mechanism which will use fully qualified class name as the resource ID. 
> Our beans are annotated with {{@WebService}} annotation (and other metadata) so it would only require a slight extension of the WADL generator to utilize a different strategy. 
> However, this task becomes quite unattainable given the current design of the WADLGenerator. It basically requires to create (and maintain) a copy of the class that extends WADL generator. 
> In general, WADL generator extensibility could be reviewed (at least private vs protected methods, allowing additional strategy injection for ID generation that defaults to some built-in strategy). 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)