[
https://issues.jboss.org/browse/AS7-2169?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-2169:
-----------------------------------
{quote}
1. Call System.getenv("X") and if it exists, use it as expression value
2. else, call System.getProperty("env.X") and if it exists, use it as expression
value
{quote}
Isn't it usually the other way around? Developers usually use the system properties to
override the environment entries (for example by passing -Denv.X). Would it be more
consistent if we did:
1. Call System.getProperty("env.X") and if it exists, use it as expression
value
2. else, call System.getenv("X") and if it exists, use it as expression value
Add support for using System.getenv() for DMR ExpressionValues.
---------------------------------------------------------------
Key: AS7-2169
URL:
https://issues.jboss.org/browse/AS7-2169
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.0.Alpha1
Reporter: Scott Stark
Assignee: Scott Stark
Fix For: 7.1.0.Beta1
Currently the org.jboss.dmr.ExpressionValue only looks to System.getProperty(name) to
obtain a reference value. We should try to also query System.getenv(name) if the system
property is not found.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira