|
From: <tri...@tr...> - 2004-02-28 22:14:53
|
How about a new JdbcResourceException extending DataAccessResourceFailureException. Btw could we rename the latter to DataAccessResourceException - FailureException sounds like a double negative :-) Thomas Quoting Rod Johnson <rod...@in...>: > > > > >Good point - changed to IllegalArgumentException. > > >I just didn't want to throw CannotGetJdbcConnectionException like before; > it arguably wasn't appropriate. In general. the DataSource implementations > shouldn't use DataAccessExceptions in the first place. > > I disagree. I think that the user should be able to catch > DataAccessException confidently in all cases (which was why I changed from > ClassNotFoundException to a DataAccessException). > > I don't have terribly strong views on this as it's not a production usage > class anyway--but that also implies it wasn't really worth changing the > behaviour either... > > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |