Major Description
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).