Re: [JBoss-user] XMBean's default attributes values

[Scott M S. <sco...@jb...>]

The only reason I can see for both is to support attributes
without setters, in which case there can be no push of the
data to the xmbean resource. I guess its not different than
specifying an attribute value for the xmbean in the jboss-service
descriptor, which is another point of conflict with
peristence and this initialization in preRegister. For example:

    <mbean code="org.jboss.chap2.xmbean.JNDIMap" name="chap2.xmbean:service=JNDIMap"
       xmbean-dd="META-INF/jndimap-xmbean.xml">
       <attribute name="JndiName">inmemory/maps/MapTest</attribute>
    </mbean>

The setting of values from the jboss-service descriptor should
also occur before the load of persistent data. Maybe the load
should be moved to postRegister.

There is no load of the model mbean descriptor data in the 3.2
version of the ModelMBeanInvoker currently.

-- 
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

David Jencks wrote:
> 
> jboss 4 ModelMBeanInvoker, preregister:
> 
> ...
>       super.preRegister(server, name);
>       configureInterceptorStack((ModelMBeanInfo)info, server);
>       //Set initial values provided in descriptors
>       setValuesFromMBeanInfo();
>       initPersistence(server);
>       //Set (and override) values from mbean persistence store.
>       load();
>       return invokePreRegister(server, name);
> 
> 
> setValuesFromMBeanInfo goes through the attribute descriptors and sets the
> values, if present, if there is a setter.
> 
> As you can see this cant happen after persistence is loaded.
> 
> If this is not the spec-intended behavior I can't see any reason to have
> both default and value descriptors.
> 
> david