(copied from the forums)
Hi all,
Is XMBean persistence supposed to persist the metadata, data (model object
state), or both?
I've been able to get this working to a point, based on the suggestions made
by David. I now have a service whose Persistence Manager class is
instantiated when the model MBean is created and is invoked according to the
persistence policy.
Now it's time to fully implement the persistence manager class. It seems
that, to do what I want it to do, the PersistenceManager interface should be
modified. Since this is the first major diversion I'm making from the
existing architecture, I thought I'd ask all of you to verify that I am on
the right track.
What is the Persistence Manager supposed to do, exactly? It occurs to me
that what I want it to do is to persist the state of the object that is
being managed by the MBean. For example, say I have an XMBean that has a
User object as its model. If I use the JMX Agent to change the Name
attribute of the User object to "Fred", then the persistence manager is
called, and I would expect the persistence manager to store the string
"Fred" in the persistence store.
When I look at the persistence code on p. 222 of "JMX: Managing J2EE...",
however, I see that only the metadata is persisted/loaded. The fact that the
Name attribute is read/write, for example, is stored, but the actual content
("Fred") is not, as far as I can tell.
What should I be persisting here -- data, metadata, or both?
Thanks again for all the help so far.
- Matt
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
