Correct: Use of the jboss-service.xml attribute elements conflicts with the use of XMBean persistence. I have pointed this out in the next edition.
Correct: The default element does not actually affect the value of an attribute as seen by the underlying XMBean if it has a setter. Its only used when there is no accessor and no value element. This has been claried in the next edition.
Incorect: You cannot set an initial attribute value from the XMBean descriptor. You need to use the value element:
The location in JNDI where the Map we manage will be bound
On startup this value is set on the XMBean before any peristent value is loaded. The version 2 XMBean example now uses this mechanism to bootstrap the JndiName attribute.
I have been trying to provide a default value for an XMBean (using the xml config files) if a persisted value is not available, but cannot achieve this. If I set the attribute in jboss-service.xml, it overwrites the persisted value on startup. The default value in xmbean.xml is not suitable as it is only for attibutes with no accessor.
This topic seems related, but can you confirm that this is the case please and if so, what do you mean by 'the next edition'?
I am using jboss 4.0.0.