[jboss-as7-dev] Attributes, metrics, additional descriptive information for such

Dimitris Andreadis dandread at redhat.com
Mon Jan 31 08:58:06 EST 2011


Makes sense, thanks.

On 31/01/2011 15:54, Emanuel Muckenhuber wrote:
> On 01/31/2011 02:37 PM, Dimitris Andreadis wrote:
>> What if I have a transient writable field, e.g. enable-metrics, that is not part of the
>> configuration info and I am not interested in persisting?
>>
>
> You can have runtime attribute handlers - which interact with services
> directly but don't affect the state of the domain model itself.
>
>> Also, can a subsystem update it's configuration without external intervention, e.g., I
>> haven't specified a certain field, or it's set wrong and the subsystem falls back to some
>> default.
>>
>
> The operation handlers registered by each subsystem would be responsible
> for validation and proper handling in case you define a wrong value.
> "default values" wouldn't be present in the configuration model itself,
> since we don't want them to get persisted. However they should be part
> of the metadata description of the model.
>
>> On 31/01/2011 15:29, Kabir Khan wrote:
>>> On 31 Jan 2011, at 13:27, Dimitris Andreadis wrote:
>>>
>>>> What's the defining feature between configuration info&
>>> max-pool-count
>>>
>>>> (runtime) metrics?
>>> current-pool-count
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Software Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

http://dandreadis.blogspot.com/



More information about the jboss-as7-dev mailing list