[
https://issues.jboss.org/browse/AS7-5182?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5182:
---------------------------------------
If a user says ${exp:default} it's an indication that they expect full expression
resolution. Not doing that and just using the default is a violation of that contract.
I don't see how this can be done. At best we could have the master send a request to
the slave asking it to resolve the expression against the HC process' system props/env
props/vault. But, the system props and env props can vary between servers that slave HC
manages. And the master can only send a single value; making it be something that varies
by server means... sending an expression. Which isn't supported by those processes.
I believe this should be resolved as Won't Fix. If people want to use new features,
they need to upgrade to versions that support those features.
properly transform/resolve expression values
--------------------------------------------
Key: AS7-5182
URL:
https://issues.jboss.org/browse/AS7-5182
Project: Application Server 7
Issue Type: Sub-task
Components: Domain Management
Reporter: Emanuel Muckenhuber
Priority: Optional
Fix For: 7.3.0.Alpha1
We need to be able to properly handle values which are getting changed to allow
expressions.
The problem is that older HCs won't understand the expression value, therefore they
need be resolved before sending the initial model. At this point this can only be done
against domain/host specific system properties. Server-group and server level overrides
would be lost when starting a managed server.
--
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