Hi all, I checked in a refactored version of OJB's statement handling:
- StatementManager class is now the main interface, StatementManagerIF is deprecated.
- Implementation class named to StatementManagerImpl (split in abstract base class and impl class to keep classes straightforward)
- StatementManager implementation does more strict control all statement handling (creation, closing, binding) and support a simple stmt caching if jdbc driver, ConnectionFactory or DataSource doesn't support this feature (configurable via custom-attributes in connection-factory element or via setter at runtime).
- StatementManager provide new convenience methods to get prepared statements with binded values (in one method call)
- Remove StatementForClassIF and impl class. This class did deal with connections, statements and sql-query strings, but in the end all these things are "natural tasks" for StatementManager and SqlGenerator. Now the basic sql statements for a class are internally cached by SqlGeneratorDefaultImpl (this was the main function of StatementForClass).
regards, Armin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
