>> Unfortunately, our code is written the same way as Lopez's code --
>> i.e. all statements are closed in a finally block and the resultset

is

>> returned from the procedure to be used afterwards, so a switch to

DBCP

>> would require a rather major rewrite. :-/ Maybe ValueObject might
>> provide an easier solution in our case.
>
>Sorry to say, but you would need to modify your code, since I'm going
>to fix the issue in 1.0.1.

Would CachedRowSet's provide a solution? Are these supported by the
JayBird driver?

Regards,
Natal Vande Casteele
Software Engineer
Pocket and Soul