If ResultSet.close is throwing an exception when being closed then to my
mind that's a bug, but we would never see it through a Junit test.

Unless the resultset is already closed, or you have closed the connection for the resultset.

Correction: I guess ResultSet.close() should not throw an exception if it is already closed.

My point was anyway that we should be careful about throwing exceptions to the junit-framework in the tearDown() since it will overwrite the "real" error.

Andreas

Reply via email to