|
From: Thomas R. <tho...@tr...> - 2004-12-03 04:35:13
|
The only drawback that I can think of is that now you are responsible for closing any statements/resultsets that you open - you need to provide a try/finally block within the callback to properly close them in case of an exception being thrown. As long as we document this, we should be OK. Thomas Colin Sampaleanu wrote: > Does anybody think it doesn't make sense to add a > JdbcOperationsCallback interface, similar to some of the other > callbacks, which can be used via a new > jdbcTemplate.execute(JdbcOperationsCallback) > method? This could be used to wrap arbitrary code which throws SQL > exceptions, so that they are properly mapped. I've had a need for > something like this a few times... > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > |