[DERBY-2582] EmbeddedConnectionPoolDataSource does not implement java.sql.Wrapper but reports JDBC 4 compliance when run with JDK 6

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.2.2.1
• Component/s: JDBC
• Labels: derby_triage10_11
• Environment: JDK 6
• Urgency: Normal
• Issue & fix info: High Value Fix
• Assignee: Unassigned
• Reporter: Sun Seng David Tan
• Created: 23/Apr/07 19:16
• Updated: 18/Jul/13 20:53
• Resolved: 18/Jul/13 20:53

Description

Software that checks the value returned by the dataseMetadata method getJDBCMajorVersion for JDBC compliance level and, based on the value, takes different paths in the code will fail unexpectedly accessing java.sql.Wrapper when loading EmbeddedConnectionPoolDataSource in a JDK 6 environment. EmbeddedConnectionPoolDataSource reports a compliance level of 4 when loaded in a JDK 6 environment. It returns JDBC 4 objects but the Datasource itself does NOT satify the JDBC 4.0 interface Wrapper and so, not being fully compliant, should not report JDBC 4 compliance.

JSR 221 does not detail the behavior of the dataseMetadata method getJDBCMajorVersion but the description in Section 6.3, JDBC 4.0 API Compliance, states: "A driver that is compliant with the JDBC 4.0 specification must .. Fully implement .. java.sql.Wrapper". As Dan stated in his comment on DERBY-2488, (http://issues.apache.org/jira/browse/DERBY-2488#action_12485033) EmbeddedConnectionPoolDataSource does not implement Wrapper.

Issue Links

• duplicates: DERBY-5880 Move java.sql.Wrapper implementations to base classes in embedded driver