You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2014/11/14 18:16:34 UTC
[jira] [Resolved] (CXF-6064) Improve WADL Generator Extensibility
for ID generation
[ https://issues.apache.org/jira/browse/CXF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin resolved CXF-6064.
-----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.3
3.1.0
Assignee: Sergey Beryozkin
See
http://git-wip-us.apache.org/repos/asf/cxf/commit/2cd4f136
> 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)