The DataSource you are using is supplied by JBoss, so it gets to decide
what Connection implementation it will use. It is absolutely required to
wrap a connection obtained from DriverManager, and this has always happened
both in jboss 2.4 and 3. It is necessary to wrap a connection obtained
from
I use this code
public java.sql.Connection getStandardConnection() throws Exception {
return standardDS.getConnection( "name", "pwd" );
}
java.sql.Connection conn= getStandardConnection();
OracleCallableStatement stmt= (OracleCallableStatement)
conn.createCallableStatem
Oops, my instructions were wrong. Should be
(OracleConnection)c =
(OracleConnection)((LocalConnection)ds.getConnection()).getUnderlyingConnection();
in 3.0 and 3.2 (current)
or
(OracleConnection)c =
(OracleConnection)((WrappedConnection)ds.getConnection())
I cast to (DataSource), and then I get connection from a standard DataSource. Isn't it correct?
thanx
Stefano
Il mer, 2002-08-21 alle 15:20, David Jencks ha scritto:
Just a warning, the xa wrapper in 3.0 does not wrap connection but the new
one I just wrote for 4.0 does. I'm ho
Just a warning, the xa wrapper in 3.0 does not wrap connection but the new
one I just wrote for 4.0 does. I'm hoping it will get tested shortly and I
will back port it to 3.2. With the local wrapper or the new xa wrapper you
need to call
(OracleConnection)c = (OracleConnection)((LocalConnectio
i tried with XA connection and it works.
Il mer, 2002-08-21 alle 10:00, Stefano Maestri ha scritto:
Il mar, 2002-08-20 alle 18:49, David Jencks ha scritto:
I think either you have 2 copies of the oracle driver deployed or you have
a version of jboss that has a bug where it
Il mar, 2002-08-20 alle 18:49, David Jencks ha scritto:
I think either you have 2 copies of the oracle driver deployed or you have
a version of jboss that has a bug where it creates 2 classloaders for each
deployed package. If you have only one copy of Oracle, which exact jboss
are you us
We have a big system in production based on J2ee and using Jboss-tomcat 2.4.x.
We are going to switch to JBoss 3.0.1, but when I configured it I had some trouble with connection pooling. Here is the stack trace that I get when I try to access to the pool with:
dataSource.getConnection( log,
