Hi Jan & Arno,
at the moment it looks like all jdbc Connection handling is done inside the SQLExecuter. Would it be possible to provide a ConnectionProvider containing a connection that will not be opened/closed within the framework? This would enable the reuse of an already established connection and also enable more sophisticated TX Management in the outer application using safejdbc if required.
e.g. Additional interface KeepAliveConnectionProvider extends ConnectionProvider
And the coresponding implementation: e.g.
SimpleKeepAliveConnectionProvider(Connection c) implements KeepAliveConenctionProvider
If this ConnectionProvider is provided, no action is taken on the Connection during the SQLExecuter processing.
Just an idea,
Wolfgang
P.S.
The framework is simple and great!
Questions: wolfgang.frank@itemis.de