Hi Andrea, Nice to hear from you :)
> and follow from there in a debug session. Let us know what you find out! Debugging in my target environment isn't that easy - so it will have to wait a bit. In the meantime, I added debug logging to my UnWrapper and the results puzzle me: Hikari Unwrapper instantiated Hikari Unwrapper instantiated canunwrap for com.zaxxer.hikari.pool.HikariProxyConnection: true canunwrap for com.zaxxer.hikari.pool.HikariProxyConnection: true unwrap result: oracle.jdbc.driver.T4CConnection@3cd2409 canunwrap for oracle.jdbc.driver.T4CConnection: false So geotools correctly detects my unwrapper, and unwrapping succeeds in the first place. However, after the connection has been unwrapped (to an oracle.jdbc.driver.T4CConnection) it seems geotools is still not happy and asks unwrappers to unwarp it again. Is the T4Connection not the expected datatype? One thing complicating things is that the application is using OSGI (and geotools is contained in a bundle), whereas the oracle driver (and the connection pool classes) are installed in tomcat and therefore most likely loaded via a different class loader. Hopefully debugging will reveal what is going on here. Br, Clemens _______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
