I'm working on updating the xmbean tests in 3.2 to make sure what we will
have in the 3.2.0 release is usable and there is an issue with transient attributes
and the default value for currencyTimeLimit. An attribute element like:

   <attribute access="read-write" default="jboss.security:service=JaasSecurityManager">
      <description>SecMgr is a read-write attribute added at the metadata level
         for which there is no state in the User2 instance.
      </description>
      <name>SecMgr</name>
      <type>javax.management.ObjectName</type>
   </attribute>

where there is no currencyTimeLimit defined fails to have a value for this attribute,
and a value cannot be set. Given that it has a default value this does not seem like
valid behavior. If the currencyTimeLimit set to -1 then the default value is seen
as the initial value for the attribute and it may be updated.

   <attribute access="read-write" default="jboss.security:service=JaasSecurityManager">
      <description>SecMgr is a read-write attribute added at the metadata level
         for which there is no state in the User2 instance.
      </description>
      <name>SecMgr</name>
      <type>javax.management.ObjectName</type>
      <descriptors>
         <currencyTimeLimit value="-1"/> 
      </descriptors>
   </attribute>

The question is why should a failure to specify the attribute descriptors result in
an unusable attribute? Either the caching logic is faulty or the implicit settings for
the attribute descriptors a not correct.




-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to