I think when pooled connection is used it should create logical statements and under JDBC4 it should create xxxx40 statements. So all calls should go through those classes. Is there a reason for coverage report showing no coverage for some methods, which are called in the test classes and whose physical statement methods are also covered?
Three possibilities come to mind: 1) The test isn't actually running under JDBC4? 2) The code coverage tool is providing an inaccurate report? 3) The decision about when to use LogicalPreparedStatement40 is more complicated, and there is some other factor involved? Perhaps it would help if you posted a patch to JIRA, with instructions about the test you're trying, and others could try to reproduce the behavior you're seeing. thanks, bryan
