[jboss-jira] [JBoss JIRA] (WFLY-2461) refactoring of character escaping in operation parameter values

RH Bugzilla Integration (JIRA) issues at jboss.org
Fri Sep 19 08:32:02 EDT 2014


    [ https://issues.jboss.org/browse/WFLY-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004270#comment-13004270 ] 

RH Bugzilla Integration commented on WFLY-2461:
-----------------------------------------------

Radim Hatlapatka <rhatlapa at redhat.com> changed the Status of [bug 1056933|https://bugzilla.redhat.com/show_bug.cgi?id=1056933] from ON_QA to VERIFIED

> refactoring of character escaping in operation parameter values
> ---------------------------------------------------------------
>
>                 Key: WFLY-2461
>                 URL: https://issues.jboss.org/browse/WFLY-2461
>             Project: WildFly
>          Issue Type: Task
>          Components: CLI
>            Reporter: Alexey Loubyansky
>            Assignee: Alexey Loubyansky
>             Fix For: 8.0.0.CR1
>
>
> There are potential issues with unescaping operation parameter values and command argument values that will be used as operation request parameter values.
> The culprit is that these values are parsed twice: first, with the general command line parser and the second time with the value type parser (which depends on the type of the value: could be list, property list, DMR, etc). Both parsers support and may perform unescaping. Which may lead to confusions and issues like WFLY-161 or WFLY-1791 and then confusing conditions in the code.
> The goal of this task is to not unescape parameter/argument values on the first parsing and leave it to the value type parsers. This concerns *only* parameter and argument value parsing, parsing of the other parts of operation requests and commands will remain as it is.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jboss-jira mailing list