RE: [Proxool-developer] Driver specific interfaces

[Bertrand R. <ber...@mo...>]

> > The pluggable ConnectionBuilder I was talking about last time may=20
> > provide a solution. If required, people could build their own=20
> > connection builder. This builder would return an adapter around the=20
> > vendor supplied connection.
>=20
> I see that might be possible. But writing an adapter is not a=20
> trivial task. And they would have to maintain it across JDK versions.
>=20
As you say *they* would have to maintain it... Not the proxool team!
Anyway, this workaround would be for drivers not implementing interfaces =
and
people wanting to access their special features...


> I suppose they could provide just the interface and we could=20
> include that in out proxy class... No adapter needed. Just=20
> their own interface that matches the API of the driver's=20
> Connection object. I wonder whether that would work.
>=20
You point to another (easier) solution: the ability for people to =
*inject*
interfaces in our proxy class.

They could define an interface containing the signature of the methods =
they
want from the vendor jdbc connection (rs and st as well); then register =
this
extra interface with proxool.

When building the proxy, you would add these extra interfaces to the
proxy...