I have been trying to get tomcat's JNDI JDBC connection pooling
code working lately, and I have run into two bugs in the tyrex code.
Since these are bugs in tyrex, this is more of an FYI than a bug report.
First, tyrex calls AccessController.checkPermsission() whether
or not there is a security m
> Also, to use the transaction manager, you need to get the OTS classes.
I don't use the transaction manager, just the pooling code, and I still
get NoClassDefFoundError's looking for org.omg.CosTransactions.Inactive,
which lives in ots.jar. Since this seems to be a requirement for using
any tyr
I wanted to use tyrex to pool JNDI-acquired JDBC connections. I have
attached a file called "diary" that explains how I ultimately got this
working. Unfortunately, this required several undesirable things. First,
I had to specify a tomcat-specific class (tyrex.jdbc.ServerDataSource)
in my web.x
