[
https://issues.jboss.org/browse/AS7-6431?page=com.atlassian.jira.plugin.s...
]
Ondřej Chaloupka commented on AS7-6431:
---------------------------------------
Ok, new observation. The DMR operation
(/system-property=qa.test.exp:add(value=expression.value)) depends on order of definition
in the same way as the xml. So the substitution does not work well then.
Incorrectly evaluated expression when property is defined after the
expression in xml
-------------------------------------------------------------------------------------
Key: AS7-6431
URL:
https://issues.jboss.org/browse/AS7-6431
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.2.0.Alpha1
Reporter: Ondřej Chaloupka
Assignee: Brian Stansberry
There is problem in evaluation of expression in case that property for evaluation is
defined after the expression.
In case of using DMR the order of property and expression definition is not taken in
consideration and substitution works fine.
When you define system properties in xml like:
{code}
<system-properties>
<property name="qa.test.property"
value="${qa.test.exp:defaultValue}"/>
<property name="qa.test.exp"
value="expression.value"/>
</system-properties>
{code}
you start the container and then you can check the expression evaluation in jboss-cli.sh
with command:
{code}
:resolve-expression(expression="${qa.test.property}")
{code}
The expression will be evaluated as "defaultValue" what is not correct because
the "qa.test.exp" is defined.
When you switch definitions of properties (switch <property> tags) then the
expression will be evaluated correctly (as "expression.value).
--
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