We are in the beginning stages of a Turbine project and are looking at
persistence solutions.
So far we are looking at Peers, Castor, and TOPLink.
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?
Castor looks to me like it will, some day, be what we need, but isn't there
yet. Would anyone care to offer some user experience with Castor?
TOPLink would seem to do everything we want, but is an expensive commercial
product. Any feedback on TOPLink would also be appreciated.
I welcome any and all feedback on any persistence mechanisms, including
flames. I'll slip the asbestos cover on my monitor before sending this.
Thanks,
Chris Crossen
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
