[ http://issues.apache.org/jira/browse/IBATIS-22?page=comments#action_58065 ] Juergen Hoeller commented on IBATIS-22: ---------------------------------------
FYI, as of Spring 1.1.4 (to be released this week), the iBATIS SQL Maps support will automatically apply Spring-managed transaction timeouts to all JDBC statements executed by iBATIS. Spring's SqlMapClientFactoryBean class simply passed a special transaction-aware DataSource proxy to the SqlMapClient, with the DataSource that the user passed in as target. So from Spring's point of view, there is no need for higher-level timeout support in iBATIS anymore. Of course, such support nevertheless wouldn't hurt in general :-) Juergen > Specify Query Timeout > --------------------- > > Key: IBATIS-22 > URL: http://issues.apache.org/jira/browse/IBATIS-22 > Project: iBatis for Java > Type: New Feature > Components: SQL Maps > Reporter: Rahul Kapoor > > There seems to be no current way to specify timeouts for select statements. I > did see a message in the sf forum that using driver properties is a possible > workaround. But it would be really nice to have a per statement timeout. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
