Branko Matijasevic wrote:
Can you tell me where/when the OJB 1.1 code+documentation might be
available?
The code is available from CVS right now.
OJB 1.1 is CVS HEAD/trunk and the current 1.0.x line of releases
is on the OJB_1_0_RELEASE branch.
Most documentation for 1.0.x on the OJB website is valid for 1.1,
since the largest changes are concerning inversion of control and
internal refactoring of non-public interfaces.
Regarding release plans I can't give you any exact dates,
just that there are talks on the dev list to do a technology
preview release.
Regarding the releasing of connections....
I tried using the following:
ConnectionManagerImpl.releaseConnection()
ConnectionFactory.releaseConnection(JdbcConnectionDescriptor jcd,
java.sql.Connection con)
... but neither one seemed to have an effect.
The effect of these are only to release the Connection object back
to the connection pool. Next time you use the same connection factory,
some pool elements will be statically kept in memory for the same
jcdAlias.
releaseAllResources() is effective for the most part, but certain
elements don't get cleared.
What I've come across is that when I toggle between drivers:
m_connDesc.setDriver(m_debug? "com.p6spy.engine.spy.P6SpyDriver" :
"com.sybase.jdbc2.jdbc.SybDriver");
... the broker's descriptor always has the correct setting, but the
actual connection keeps using the P6Spy driver.
P6Spy is a bit tricky, since it registers it's own driver for the same
JDBC subprotocol as the real underlying driver. What you can try is
to manually deregister the P6Spy driver:
import java.sql.Driver;
import java.sql.DriverManager;
import org.apache.ojb.broker.util.ClassHelper;
...
Driver p6Driver = ClassHelper.newInstance("com.p6spy.engine.spy.P6SpyDriver");
DriverManager.deregisterDriver(p6Driver);
This way the OJB-internal call to registerDriver has a chance to
change the DriverManager driver registration for the Sybase
JDBC subprotocol.
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
