[jira] [Resolved] (CXF-4979) WadlGenerator generates invalid xml for QueryParameters with a default value containing " characters

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin resolved CXF-4979.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.5
                   2.6.8
                   2.8.0
         Assignee: Sergey Beryozkin

Path, method parameter default values, doc title and values are now XML-encoded if needed 
                
> WadlGenerator generates invalid xml for QueryParameters with a default value containing " characters
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CXF-4979
>                 URL: https://issues.apache.org/jira/browse/CXF-4979
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.6.7
>         Environment: tomee-1.6.0-SNAPSHOT
>            Reporter: Antoine Reilles
>            Assignee: Sergey Beryozkin
>             Fix For: 2.8.0, 2.6.8, 2.7.5
>
>
> When defining a service with an {{@DefaultValue}} those value contains some double quotes, for instance:
> {code}
> @GET
>   public List<Task> tasks(
>    @DefaultValue("-\"Created\" -\"Done\"") @QueryParam("states") String states) {
>   ...
> }
> {code}
> The wadl description generated by the {{WadlGenerator}} class is not valid xml: the value should be xml encoded. It seems there are a lot of cases where the inputs are not correctly xml encoded in the generator, {{@DefaultValue}} being the one that will most probably contain offending values.
> As a side note, {{WadlGenerator}} is really painful to extend. For instance, in order to support custom "doc" annotations, one cannot override the handledocs method, but has to redefine all its callers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira