[openjms-developer] Connection pooling - dropping support for tyrex, proxool

[Tim Anderson]

OpenJMS uses old versions of tyrex (http://tyrex.sourceforge.net) and
proxool (http://proxool.sourceforge.net) for connection pooling. The
versions of
each are no longer readily available, which makes it hard to migrate the
build
environment over to maven.
Tyrex 1.0 is available, but is buggy and not actively maintained, and
the latest version of proxool requires JDK 1.3.

To cut a fat story thin, I want to drop support for both
tyrex and proxool, and replace them with commons-dbcp
(http://jakarta.apache.org/commons/dbcp)
Standardising on a single connection pool implementation will
cut down the number of configurations we have to test for
each release.
Anyone who wants to plug in their own connection pool will
still be able to.

Comments?

Thanks,

Tim

[Tim Anderson]

I want commons-dbcp to be the default pool,
but I also want to remove any dependency on both tyrex and proxool.
This means removing the jars from $OPENJMS_HOME/lib and
removing the ProxoolConnectionManager and TyrexConnectionManager
wrappers.

I guess the wrapper classes could be moved to a contrib
directory so they're not totally gone from CVS, but I don't
see a lot of point in keeping them.

Were you planning to use tyrex for XA support?

-----Original Message-----
Sent: Tuesday, 1 July 2003 5:46 PM
Subject: RE: [openjms-developer] Connection pooling - dropping support
for tyrex, proxool
Tim,
As long as we maintain support for the old connectors that is fine. If you
are just saying you want to distribute commons-dbcp as the default
connection pooling library then this is also fine, but I still
want to have
the option of using tyrex.
cheers
</jima>

-----Original Message-----
Anderson
Sent: Tuesday, July 01, 2003 5:36 PM
To: openjms-developer
Subject: [openjms-developer] Connection pooling - dropping support for
tyrex, proxool
OpenJMS uses old versions of tyrex (http://tyrex.sourceforge.net) and
proxool (http://proxool.sourceforge.net) for connection pooling. The
versions of
each are no longer readily available, which makes it hard to migrate the
build
environment over to maven.
Tyrex 1.0 is available, but is buggy and not actively maintained, and
the latest version of proxool requires JDK 1.3.
To cut a fat story thin, I want to drop support for both
tyrex and proxool, and replace them with commons-dbcp
(http://jakarta.apache.org/commons/dbcp)
Standardising on a single connection pool implementation will
cut down the number of configurations we have to test for
each release.
Anyone who wants to plug in their own connection pool will
still be able to.
Comments?
Thanks,
Tim
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
openjms-developer mailing list
https://lists.sourceforge.net/lists/listinfo/openjms-developer