tag:blogger.com,1999:blog-4262232281084864898.post3785511418386868659..comments2008-06-25T13:44:49.950-07:00Julian Sinaihttp://www.blogger.com/profile/06209296951442764412noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-4262232281084864898.post-80059698298986464572008-06-25T13:44:00.000-07:002008-06-25T13:44:00.000-07:00Eyal, glad I could help!Julian Sinaihttp://www.blogger.com/profile/06209296951442764412noreply@blogger.comtag:blogger.com,1999:blog-4262232281084864898.post-41298897621425707132008-06-25T08:54:00.000-07:002008-06-25T08:54:00.000-07:00Rod, thanks for the feedback.<BR/><BR/>You are right about swallowing the stack trace--in our production code we don't do that. I oversimplified it for the sake of the example. I've corrected it.<BR/><BR/>Regarding using Spring's DAO exceptions instead of ours--we specifically didn't because we wanted to change as little of the client code as possible, but as time goes by we can eliminate our own exceptions in favour of Spring's.<BR/><BR/>Regarding your other comment about Spring 2.5--one thing I neglected to mention is that we are currently restricted to using Spring version 2.0.1.jsinaihttps://me.yahoo.com/jsinai#aa1a8noreply@blogger.comtag:blogger.com,1999:blog-4262232281084864898.post-43250272912081689462008-06-25T01:52:00.000-07:002008-06-25T01:52:00.000-07:00"For example, we are fine with using XML configuration for dependency injection instead of EJB3-style annotations."<BR/>Spring 2.5 supports EJB style DI annotations. It also offers its own @Autowired annotation which is much more powerful.Rod Johnsonhttp://www.blogger.com/profile/16926906023111477203noreply@blogger.comtag:blogger.com,1999:blog-4262232281084864898.post-82473145121298654262008-06-25T01:51:00.000-07:002008-06-25T01:51:00.000-07:00You can have a lot less code in your Spring DAO--only one line per method, in fact.<BR/><BR/>- Consider whether you want to have your own DAO exceptions, or use Spring's automatic exception translation to Spring's DAO exception hierarchy. Application-specific exceptions are usually unnecessary<BR/>- That will also eliminate the need for the try/catch block.<BR/>- You also don't need to use HibernateTemplate any more--check out recent Spring examples<BR/><BR/>Btw you should not catch (Exception) in general, and you should be careful to preserve the stack trace, not just the message, when wrapping an exception.<BR/><BR/>Rgds<BR/>Rod JohnsonRod Johnsonhttp://www.blogger.com/profile/16926906023111477203noreply@blogger.comtag:blogger.com,1999:blog-4262232281084864898.post-86425715175185576532008-06-25T00:02:00.000-07:002008-06-25T00:02:00.000-07:00Hi,<BR/>Thanks for an interesting article.<BR/>I am not a Spring / Hibernate developer.<BR/>I'm a more user of these frameworks in our application.<BR/>This was very helpful as I am going to get interviewed for a position to build from scratch the back end of an NMS app.<BR/>This article really helped me prepare myself :)Eyalhttp://www.blogger.com/profile/02894268033436172462noreply@blogger.com