1) Removing ambiguity in overloaded methods with explicit casting.
2) Adding two methods to InputStreamBlob.java that throw UnsupportedOperationException to comply with newly added methods in Blob interface.

Regarding the DataSource problems, I did not encounter them at first. After you mentioned, however, I investigated and the reason why I wasn't seeing them was that the jdbc2_0-stdext.jar is above the JRE in the export order of the eclipse .classpath file. This means that the DataSource from there is used during the compilation. After I put that jar below the JRE and I can also see those errors. The issue seems to be that the DataSource interface now extends a Wrapper interface that adds two methods. I am also not sure about the implementation required for those two methods.

public Object unwrap(Class iface) throws SQLException {

Assert.notNull(iface, "Interface argument must not be null");

if (!DataSource.class.equals(iface)) { throw new SQLException("DataSource of type [" + getClass().getName() + "] can only be unwrapped as [javax.sql.DataSource], not as [" + iface.getName()); }

return this;

}

public boolean isWrapperFor(Class iface) throws SQLException { return DataSource.class.equals(iface); }

The DelegatingDataSource (which is similar to the TransactionAwareDataSourceProxy in Compass in some sense) looks like:

public Object unwrap(Class iface) throws SQLException { return getTargetDataSource().unwrap(iface); }

public boolean isWrapperFor(Class iface) throws SQLException { return getTargetDataSource().isWrapperFor(iface); }

Maybe this is helpful.