David Rauschenbach said:
Nature abhors a vacuum, and so does my architecture diagram. That
leaves
O/R mappers filling a role that is not otherwise addressed in the
object
containers I've seen. And I don't know if I ever will see things
like a
TOPLink container for GemStone/J (for example...), because I know
that's
not where those vendor's heads are at. What would you call such a
product
anyway? A "non-relational object/relational mapper"? That'd be fun
to try
and market (not).
<vendor>
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. We plan to add additional
containers which support relational stores such as Oracle and Sybase(these
containers will likely leverage existing O/R mapping technologies).
</vendor>
Larry
===========================================================================
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".
