If you use XMBeans you have the option of declaring attributes, that don't correspond to actual POJO attributes (i.e. no getter/setter) and for which a default value may be specified, e.g
| <attribute access="read-only"> | <name>SomeString</name> | <type>java.lang.String</type> | <descriptors> | <default value="Initial value"/> | </descriptors> | </attribute> | A problem with this is your POJO code will have to go through the MBeanServer to read the atttribute, if needed. But as Scott pointed out, this seems to be mostly an access control issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864430#3864430 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864430 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
