RE: [Proxool-developer] Release 0.5

[Martin C. <mus...@us...>]

Bill,

> I've taken a look at the code and I see the problem. Their Statement
> implementation doesn't implement Statement directly but extends an
> abstract class that does so. This exposes a limitation in Proxool's code
> that I have now fixed. The latest CVS copy should now work for jxDBCon
> driver using methods to create Statements, PreparedStatements and
> CallableStatements.

Right, this is the whole concept for the jxDBCon framework. I guess not many
drivers make use of abstraction? I find this driver to be a better/cleaner
implementation for PostgreSQL than the one that actually ships with the
database.

> For your convenience I have I built a JAR:
>
>  http://proxool.sourceforge.net/download/proxool-CVS.jar

Again thanks for providing binaries. I feel lazy;) I think it's time I get a
copy and compile myself from source.

> Don't bother with that now. Just let me know whether the new version
> fixes it for you. I suspect it will.

Sorry it didn't. Here is the stack trace:

Caused by: java.lang.RuntimeException: Unexpected invocation exception:
$Proxy2
	at
org.logicalcobwebs.proxool.ProxyConnection.invoke(ProxyConnection.java:114)
	at $Proxy1.createStatement(Unknown Source)

> Since nobody else has reported this problem I probably won't bother
> making a new release early. 0.6 is scheduled for round about December
> 12.

I'm in not hurry to upgrade 0.4 works perfectly fine for me. But, I am happy
to help test this one. I was easily able to build from source so we can
begin the debugging mayhem! My company is actively developing a servlet
application using proxool, so it's very easy for me to drop in a new version
during the development cycle. Again 0.4 works perfect for us so we're in no
panic.

Perhaps you could share the differences between the 0.4 code and 0.5 code
that would "break" abstraction of a Statement interface? Just for those
curious...

Thanks again for being so helpful.
Martin