[jboss-as7-dev] Configuration conundrum with Express

[Brian Stansberry]

See example below of reading a resource and then setting an attribute to 
an expression value. This will work properly on master when I'm done today.

Note that not all attributes support expressions (most don't). For those 
that do, the :read-resource-description content for the attribute will 
include:

"expressions-allowed" => true

[standalone at localhost:9999 /] cd subsystem=ejb3
[standalone at localhost:9999 subsystem=ejb3] :read-resource 

{
     "outcome" => "success",
     "result" => {
         "default-mdb-instance-pool" => "mdb-strict-max-pool",
         "default-resource-adapter-name" => "hornetq-ra",
         "default-singleton-access-timeout" => 5000L,
         "default-slsb-instance-pool" => "slsb-strict-max-pool",
         "default-stateful-access-timeout" => 5000,
         "service" => {
             "timer-service" => undefined,
             "remote" => undefined,
             "async" => undefined
         },
         "strict-max-bean-instance-pool" => {
             "slsb-strict-max-pool" => undefined,
             "mdb-strict-max-pool" => undefined
         },
         "thread-pool" => {"default" => undefined}
     }
}
[standalone at localhost:9999 subsystem=ejb3] 
:write-attribute(name=default-stateful-access-timeout,value=${sfsb.timeout:5000})
{"outcome" => "success"}
[standalone at localhost:9999 subsystem=ejb3] :read-resource 

{
     "outcome" => "success",
     "result" => {
         "default-mdb-instance-pool" => "mdb-strict-max-pool",
         "default-resource-adapter-name" => "hornetq-ra",
         "default-singleton-access-timeout" => 5000L,
         "default-slsb-instance-pool" => "slsb-strict-max-pool",
         "default-stateful-access-timeout" => expression 
"${sfsb.timeout:5000}",
         "service" => {
             "timer-service" => undefined,
             "remote" => undefined,
             "async" => undefined
         },
         "strict-max-bean-instance-pool" => {
             "slsb-strict-max-pool" => undefined,
             "mdb-strict-max-pool" => undefined
         },
         "thread-pool" => {"default" => undefined}
     }
}

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


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat