"Brian N. Miller" wrote:
>
> Larry wrote:
> >
> >Gemstone/J provides the ability to persist objects directly in the
> >application server via what we call the Persistent Cache Architecture(PCA).
> >Think of it as an OODB capability built into the app server. Java objects
> >are quickly and transparently commited with their referential integrity
> >maintained. Therefore, Container Managed Persistence with Gemstone/J does
> >NOT require any mapping code at all. Abstract data types in member fields of
> >a bean will not break the underlying persistence as can be the case in other
> >products which rely on mapping to accomplish CMP.
>
> But I get this service for less money via WebLogic. It supports
> transparent, transactional, serialized persistence of entities
> and the object graphs they root.
>
They sound similar. But I'd be surprised if the proferred functionality
was the same. For example, if your persistence model is serialization, then
(1) ... persisting an object may involve writing out lots of other
objects, many of which haven't changed since the last persist.
(2) ... persisting an object may be a lengthy operation and may lock
many other objects at the same time.
(3) ...you wind up writing out the same object many times (once per object
graph it's part of)
(4) ... you wind up with massive versioning problems (since serialization
is, essentially, a deep copy mechanism).
Now these objections are to a naive use of serialization as a persistence
mechanism. I have no idea what Weblogic really does. But the way to
solve these problems seems (to me) to be to make persistence more granular
(e.g. leave serialization behind and move to a more databasey approach).
William Grosso
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
