[JBoss JIRA] (AS7-6431) Incorrectly evaluated expression when property is defined after the expression in xml
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6431?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-6431:
---------------------------------------
I'm surprised reload helps.
> 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
13 years, 3 months
[JBoss JIRA] (AS7-6432) Incorrect evaluation of system property for expression substitution
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6432?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-6432:
---------------------------------------
Ah, good. My first long comment above was before I really understood how the test worked. For the 2nd one I understood better what it was doing and was concerned there really was an issue but wasn't sure. I'm glad it's ok.
> Incorrect evaluation of system property for expression substitution
> -------------------------------------------------------------------
>
> Key: AS7-6432
> URL: https://issues.jboss.org/browse/AS7-6432
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Brian Stansberry
>
> Finally I think that I've got a way how to resolve expressions on VM where container resides.
> My test case:
> https://github.com/ochaloup/jboss-as/blob/expression-substitution-run-in-...
> From this I've found issues for system property evaluation. I mean the case when System.getProperty(someName) is called.
> The application should get the evaluated value from expression but instead of it it gets the default value from expression.
> The problematic test cases are
> testSystemPropertyEvaluation - there is defined system property by calling System.setProperty and it's expected that the expression which uses this defined property will evaluate itself to the value of the System.setProperty. For the way of :resolve-expression it works fine but for getting value with System.getProperty the old default value is returned.
> setInnerExpression - it defines two levels of evaluation of expression and it seems that then the System.getProperty on the second level of evaluation does not get the evaluated/substituted value
> I hope that the test code will be more comprehensible than my explanation.
--
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
13 years, 3 months
[JBoss JIRA] (SECURITY-724) Vault created through 7.2.0_Alpha not compatible with 7.1.1_Final
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/SECURITY-724?page=com.atlassian.jira.plug... ]
Darran Lofthouse commented on SECURITY-724:
-------------------------------------------
One comment regarding compatibility - we don't really have a compatibility requirement for moving from AS 7.2 to AS 7.1 but we do have a requirement for the move from 7.1 to 7.2.
> Vault created through 7.2.0_Alpha not compatible with 7.1.1_Final
> ------------------------------------------------------------------
>
> Key: SECURITY-724
> URL: https://issues.jboss.org/browse/SECURITY-724
> Project: PicketBox
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Interoperability
> Reporter: subh aym
> Assignee: Peter Skopek
>
> Created a security vault through security jars of JBoss AS 7.2.0-Alpha which is scriptable. But the same vault could not be used in JBoss 7.1.1-Final release.
> How can the vault be created through script, working for JBoss 7.1
--
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
13 years, 3 months