[jboss-as7-dev] Configuration conundrum with Express

[Brian Stansberry]

On 10/20/11 11:56 AM, Scott Stark wrote:
> Actually it does support alternative properties, and I have added tests
> for that. I'm working on the update as part of
> https://issues.jboss.org/browse/AS7-2169.
>

Awesome, thanks.

> The full syntax for the expression will now be:
> ${<[env.]name>[,<[env.]name2>[,<[env.]name3>...]][:<default>]}
>
> with the following resolution logic:
>
> 1. For each [env.]name value,
>       a. First look for System.getProperty([env.]name) and use it if defined
>       b. else, look for System.getenv(name) and use it if defined
> 2. If there is no matching system property or environment variable, use
> the default if provided.
>
> I have added tests for all of these combinations to the
> org.jboss.dmr.ExpressionValueTest test. This will be pushed out shortly.
>

If it doesn't already, can you make it fail with an ISE if the string 
actually is an expression (i.e. has ${} syntax) and it can't resolve?

> On 10/20/11 7:45 AM, Brian Stansberry wrote:
>> <trolling-for-patch>The resolve() logic in dmr doesn't support
>> alternative properties the way the old jboss-common-core stuff
>> did.</trolling-for-patch>
>>
>> Doesn't deal with System.getEnv() either. ;)
>>
>>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat