tag:blogger.com,1999:blog-14415229.post112871615951984431..comments2023-10-10T16:55:02.139+02:00Comments on Chase The Devil: Spring Books RoundupFabienhttp://www.blogger.com/profile/07288327695801480778noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-14415229.post-1129174166691030442005-10-13T05:29:00.000+02:002005-10-13T05:29:00.000+02:00Sorry but I have to disagree with your comments th...Sorry but I have to disagree with your comments that Spring is useless for database use, especially in the case of JDBC. For JDBC the only thing you really need to be concerned about is your SQL...Spring handles most of the other stuff for you which is good. Why should I write that stuff if its already being done by a well-tested framework? <BR/><BR/>Its very useful to use the Spring templates for Hibenate, IBATIS, etc. for the very same reasons. How can you argue about common exception handling regardless of the ORM tool you happen to be using? Or ease of transaction handling? I don't know why you'd want to write transaction handling code on your own if there is a well-written, well-tested, framework out there that already does it. Spend time on the stuff that matters...not the glue.<BR/><BR/>JasonAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-14415229.post-1128936895625362932005-10-10T11:34:00.000+02:002005-10-10T11:34:00.000+02:00I updated the post about JDK 1.5 support. I will a...I updated the post about JDK 1.5 support. I will add a comparison with the good Spring Reference Book later.<BR/><BR/>About Spring JDBC, both Hibernate and iBatis allows you to write 1 line SQL calls against a datasource. You do need other lines for transaction demarcation, which I consider a good thing. And even that I suppose could be taken care of using the right annotations.Fabienhttps://www.blogger.com/profile/07288327695801480778noreply@blogger.comtag:blogger.com,1999:blog-14415229.post-1128752305037890532005-10-08T08:18:00.000+02:002005-10-08T08:18:00.000+02:00>JDBC or database use: while Spring >has a well do...>JDBC or database use: while Spring >has a well done framework, Hibernate >or iBatis have a very good API that >makes Spring abstraction useless.<BR/><BR/>ORM is not appropriate for all types of database access. iBatis does not allow execution of adhoc SQL.<BR/><BR/>Spring JDBC exists to make it easy to execute adhoc, one-liner SQL calls against a datasource in the context of a transaction.<BR/><BR/>That's a very valid need.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-14415229.post-1128752129620221412005-10-08T08:15:00.000+02:002005-10-08T08:15:00.000+02:00>Spring does not seem to make use of >any JDK 1.5 ...>Spring does not seem to make use of >any JDK 1.5 new features.<BR/><BR/>See the @Transactional annotation for demaracting transactions in source metadata. See the @ManagedResource annotation for describing JMX management metadata.<BR/><BR/>Spring supports 1.5 nicely, it just does it in away where it still runs on 1.3 because that is important to its customer base.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-14415229.post-1128725156540908082005-10-08T00:45:00.000+02:002005-10-08T00:45:00.000+02:00Those books showed me Swing could be useful in som...<I> Those books showed me Swing could be useful in some projects: </I><BR/>You surely mean <B>Spring</B> not Swing. :)Anonymousnoreply@blogger.com