Currently Castor closes JDBC connections at the end of each transaction, and
creates another session for each following transaction. This is very time
consuming (if not using connection pooling) and might be avoidable when
optimizing the Castor behaviour regarding transactions and JDBC sessions.
Don't closing JDBC sessions at every transaction end can enhance the overall
For a illustration of my idea please see this link: