Hello Sebastian,
i think, the common-dbcp + commons-pooling is the better way. I tried
both ways, but no one works!
My problem is the context.
Whe i make a
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
DataSource ds = (DataSource)envCtx.lookup("jdbc/TestB");
this Datasource Statement raise an error.
It seems, the context "jdbc/TestDB" will never initialized. I test the
(envCtx != null), but it is not null.
I don't know, what I can do, because I tried it two weeks and every time
the same error. It seems, it would not work on XP and 1.4.1?!
Regards Chris
-----Urspr�ngliche Nachricht-----
Von: Sebasti�o Carlos Santos [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 23. Februar 2003 19:37
An: [EMAIL PROTECTED]
Betreff: RE: Connection Pooling
Indeed which is the difference of using
1. Tomcat JNDI: or
2. commons-dbcp + commons-pooling: ?
Thank you
****************************************************************
There are two options.
1. Tomcat JNDI: refer to Tomcat's JNDI datasource how-to
2. commons-dbcp + commons-pooling: refer to commons-dbcp and pooling API
documentation
Which one do you want to know?
Regards,
PQ
"This Guy Thinks He Knows Everything"
"This Guy Thinks He Knows What He Is Doing"
Sebasti�o Carlos Santos
Oracle Database Administrator - OCP DBA 8i
Universidade Federal de Uberl�ndia - UFU
Gratifica��o de Est�mulo � Doc�ncia - GED
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
