Thanks for the reply, Jon.
> Peers has the obvious advantage of being integrated into Turbine. What we
> don't see is the automatic mapping of an object hierarchy. With TOPLink
for
> example, we save our top-level object and all the objects in the hierarchy
> are automatically persisted. Is this capability in Peers and I have missed
> it? If not, how are other folks handling this?
>>Huh? Could you be a bit more clear please? If you can explain what you
want,
>>I'm sure that we can add it...or you can also scratch your own itch. :-)
If I have object A which has an ArrayList of B objects each of which may
have a collection of C objects, and I commit object A to the database, any
changes made to the B and C objects are automagically reflected to the
database. Modified B and C cause updates, new B and C cause inserts.
Have I made it clearer?
Chris
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
