Hello, again.
I think I might have found the problem. I might have
misread the code completely, but here's what I think
is the case.
In JDBCHelper.handle(), the connection is closed in a
finally-block, before we get a chance to get a hold of
the ResultSet, and hence we get the exception I
Thanks - all fixed and working ok.
Thanks again for your help.
Ed.
On 21/11/06, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Ed,
Please check the /lib/README.txt file in the distribution, it lists all
the dependencies. In your case, I forgot to mention that you also need the
Simple JAR in the
Hello Kyrre,
you're right : the current behaviour is bugged. If you want to use the
resultSet, the connection need to stay open.
This connector has been released a long time ago and has probably been
updated without tests.
As Jerome said, we are working on some refactorings to the JDBC Client in
Hi John,
I have some concerns about the proposed approach...
(A) What about results that are quite large? I.e. that take up a lot
of memory or won't fit into memory?
One major use case I see for this JDBC connector is to fetch a reasonable
amount of data in order to assemble a
Jerome,
Thank you for the response...I thought I had an Aha! moment there. :)
I've changed my Representation to set the size to Representation.UNKNOWN_SIZE,
however, I still think I am having a problem. I think the problem lies in the
Message.isEntityAvailable() method, shown here:
public
Hi Mitch,
My turn to have a Aha! moment ;-) It's a rather major bug that you found
here. I will fix it today and release a new snapshot.
Best regards,
Jerome
-Message d'origine-
De : Mitch Stewart [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 24 novembre 2006 03:44
À :
6 matches
Mail list logo
