From: Simon Stewart [mailto:[EMAIL PROTECTED]]
Forgive me, but what about the case where you just set the
prim-key-class to be java.lang.Object and don't specify a managed
primary key field in your ejb-jar.xml file? While that's not the
world's most advanced method for automatically
-interest]CMP/BMP and standard JDBC, speed is of essence
From: Simon Stewart [mailto:[EMAIL PROTECTED]]
Forgive me, but what about the case where you just set the
prim-key-class to be java.lang.Object and don't specify a managed
primary key field in your ejb-jar.xml file? While that's
Jeff -
Yes, it really works. You can get access to the key value later by using getPrimaryKey on the instance.
Cheers
Ray
Jeff Schnitzer [EMAIL PROTECTED] wrote:
From: Simon Stewart [mailto:[EMAIL PROTECTED]] Forgive me, but what about the case where you just set the prim-key-class to be
: Orion-InterestSubject: RE: [orion-interest]CMP/BMP
and standard JDBC, speed is of essence
Jeff -
Yes, it really works. You can get access to the key value later by
using getPrimaryKey on the instance.
Cheers
Ray
Jeff Schnitzer [EMAIL PROTECTED] wrote:
From: Simon Stewart
]CMP/BMP and standard JDBC, speed is of
essence
Jeff -
Yes, it really works. You can get access to the key value later by
using getPrimaryKey on the instance.
Cheers
Ray
Jeff Schnitzer [EMAIL PROTECTED] wrote:
From: Simon Stewart [mailto:[EMAIL PROTECTED]]
Forgive me, but what about
On Sun, Apr 07, 2002 at 01:11:37PM -0700, Jeff Schnitzer wrote:
Irrespective of who may be a smarter developer, I can guarantee you that
I know a *lot* more about *my* specific business logic than Karl or
Magnus. Furthermore, Karl and Magnus are for the most part just
implementing a
]]On Behalf Of Jeff Schnitzer
Sent: Saturday, April 06, 2002 10:41 PM
To: Orion-Interest
Subject: RE: [orion-interest]CMP/BMP and standard JDBC, speed is of
essence
From: Hani Suleiman [mailto:[EMAIL PROTECTED]]
Sent: Saturday, April 06, 2002 6:20 PM
To: Orion-Interest
Subject: Re: [orion-interest
From: The elephantwalker [mailto:[EMAIL PROTECTED]]
You will find that if you want the _enterprise_ features offered by
cmp
with
straight jdbc calls, your classes for jdbc calls will be slower than
cmp,
and _much more_ difficult to develop.
I am not a smarter developer than Karl or
Entity bean caching I have found to be remarkably useless. First of
all, it depends on a pessimistic locking strategy, which is both hard to
use (gotta love those deadlock exceptions!) and not applicable to a
clustered environment or any environment in which the database table can
be modified
CMP will load in all the entities in one go (in orion at least).
There will be a performance difference between straight JDBC and EJB, since
there's more involved with an EJB query. Transactions, constructing entities
and so on are extra overhead that just getting a resultset back will not
have.
From: Hani Suleiman [mailto:[EMAIL PROTECTED]]
Sent: Saturday, April 06, 2002 6:20 PM
To: Orion-Interest
Subject: Re: [orion-interest]CMP/BMP and standard JDBC, speed is of
essence
CMP will load in all the entities in one go (in orion at least).
There will be a performance difference
11 matches
Mail list logo
