What DataSource implementation is used internally by JNDI is up to
the admin (it can be Cayenne, DBCP or million others). Conversly, you
can deploy Cayenne with your own DataSource without JNDI. In this
respect two deployment strategies are equivalent.
All JNDI does is making your application a good J2EE citizen,
externalizing certain configuration pieces and providing a "contract"
between an application (that you control as a developer) and J2EE
container (that is supposedly controlled by sysadmins).
It is a requirement for "enterprise" deployment (whatever that
means). If you control the environment yourself end-to-end, you may
still find it useful, as a single String name in your Cayenne mapping
can be used to access different databases on different servers
(sometimes you can swap DB on a "hot" server) ... It is extra
configuration though...
Andrus
On Oct 5, 2005, at 10:40 PM, Kevin Menard wrote:
> If you're only having one webapp access a DB connection pool, does
> using a JNDI data source gain you anything over using the Cayenne one?
>
> Thanks,
> Kevin
This archive was generated by hypermail 2.0.0 : Wed Oct 05 2005 - 22:56:35 EDT