The interceptor can be safely removed. It was necessary for the
project I was working on, but you probably don't need it.
JDBC connection settings are best done through a DataSource and
specified at the container level instead of programmatically.
Martijn
On Mon, Nov 16, 2009 at 6:38 PM,
The interceptor can be safely removed. It was necessary for the
project I was working on, but you probably don't need it.
JDBC connection settings are best done through a DataSource and
specified at the container level instead of programmatically.
Martijn
On Mon, Nov 16, 2009 at 6:38 PM,
On Mon, Nov 16, 2009 at 12:38 PM, Jeffrey Schneller
jeffrey.schnel...@envisa.com wrote:
Also how would one move the configuration of the jdbc connection to
code? It is desirable to db connection information reside at the server
level so when deploying code from dev to stage to production, you
I'm not sure the purpose of the interceptor, but until you have a need
to extend and use it, you can use the org.hibernate.EmptyInterceptor
class instead of creating your own. I have had no problems with using
that class.
-Original Message-
From: Jeffrey Schneller
