[jboss-as7-dev] Configuration conundrum with Express
Jason T. Greene
jason.greene at redhat.com
Tue Oct 18 17:21:37 EDT 2011
It's the same as in in XML ${property:default}
On 10/18/11 2:48 PM, Scott Stark wrote:
> Are there some examples of what the syntax looks like for the expression?
>
> On 10/18/11 11:41 AM, Brian Stansberry wrote:
>> On 10/18/11 1:28 PM, Scott Stark wrote:
>>> On 10/18/11 7:07 AM, Jason T. Greene wrote:
>>>> I think Brian's question was "Why can't we just put the env
>>>> expressions in the management operation?" Perhaps the CLI doesn't
>>>> fully use the expression type when seen?
>>>>
>>> I am talking about having the env expressions in the batch script of the
>>> management operations. The issue was that these are not being replaced
>>> by the command line tools.
>> They are not meant to be replaced by the command line tools; they should
>> be passed through to the server and stored as expressions. I'll put
>> through a change today in how some less-recently changed parts of the
>> model (e.g. interfaces, sockets) deal with expressions; I believe they
>> are not handling expressions that come in via the management APIs
>> correctly; they just deal with them properly in the parser.
>>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
More information about the jboss-as7-dev
mailing list