At 01:45 PM 8/22/00 +0200, you wrote:
>vikas gupta wrote:
>
> > Hi,
> > I feel Weblogic should be the choice if you are thinking of doing some
> > complex Entity Bean-EntityBean or EntityBean-Object mapping .
> > Weblogic provides exclusive support for these Bean-Object-DataBase
> > Mapping Tools (TOPLink).
> >
>
>In what way is this support "exclusive"? The "basic" CMP support of IAS is way
>more powerful than the one of Weblogic, and it also supports Toplink and
>Cocobase, as I'm sure other EJB servers do (doesn't Gemstone have an embedded
>object database?).
(FWIW, I currently contract to GemStone, am technically not an employee of
theirs, and have my own independent opinions. However, since I do receive
compensation from GemStone it seems appropriate that I caveat my comments
with vendor tags. I really don't intend this reply as flame bait to other
vendors or to deride other vendors' products in any way).
<vendor>
Yes, GemStone/J (http://www.gemstone.com/) still includes the object
database that has been part of GemStone's application servers (of the
Smalltalk and Java variety) for the past 15+ years. These days, GemStone
refers to it as "PCA" or the Persistent Cache Architecture, but in fact it
is an object database. As you can imagine, after more than 15 years of
building this stuff, GemStone's application server and object database
technology is very sophisticated.
The object database has the features that you expect to find in a
full-blown database. But, using it means you don't have to O/R map your
objects since it stores objects as objects. Your classes don't even have
to extend any special "persistence" class or implement any special
"persistence" interface (not even Serializable). Making "object X"
persistent in the object database is as simple as establishing an object
reference from an object that is already persistent to "object X" within
the context of a transaction of course. Really, it's that simple! And,
since you are avoiding the penalty of O/R mapping, it's really performant.
Having said that, I do realize (as does GemStone) that there are a host of
legitimate reasons that you might choose to use a relational database as
your database of record over the object database. And, GemStone/J most
definitely does NOT require you to use it's object database.
That's fine, O/R mapping tools like Cocobase and TopLink most definitely do
work with GemStone and do support that usage model quite well.
</vendor>
Have fun,
Dave Muirhead
>JB.
>
> >
> > Cheers,
> > Vikas.
>
><deleted>
>--
>Jean-Baptiste Nizet
>[EMAIL PROTECTED]
>
>R&D Engineer, S1 Belgium
>Kleine Kloosterstraat, 23
>B-1932 Sint-Stevens Woluwe
>+32 2 200 45 42
>
>===========================================================================
>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".
===========================================================================
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".
