[jboss-as7-dev] Configuration conundrum with Express

Brian Stansberry brian.stansberry at redhat.com
Tue Oct 18 19:22:31 EDT 2011


On 10/18/11 5:34 PM, Scott Stark wrote:
> Thanks. I'll check against the attributes I'll need and raise issues to
> address those I find missing.
>

Thanks; that will be very helpful.

> One issue I see is that we are only looking to System.getProperty(name)
> for the value of an expression in the org.jboss.dmr.ExpressionValue
> class. The expressions I'm typically using need to be queried using
> System.getenv(name). Would it be ok to fallback to a System.getenv(name)
> if there is no System.getProperty(name) value found? This would require
> an update to the dmr project.
>

I'm fine with that.

> On 10/18/11 1:35 PM, Brian Stansberry wrote:
>> 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}
>>        }
>> }
>>
>>
>
> _______________________________________________
> 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


More information about the jboss-as7-dev mailing list