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 Magnus. Their algorithms for
caching, transaction management,
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
