Yeah, with hibernate 3 the HibernateTemplate doesn't really makes much sense. With hibernate 2 it was good for translating exceptions, since HibernateException was checked.
However, we've been working on a JDBC project lately and Spring's JdbcTemplate was a huge win to have. -Matej Igor Vaynberg wrote: > but you dont need to use spring template to reap the benefits, and you > damn well know that since we dont :) > > -Igor > > > On 6/14/06, *Eelco Hillenius* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > I'm familiar w/ Hibernate but unfortunately, know very little about > > Spring and know nothing about Jetty. I looked into Spring when I > > first started using Hibernate because I hated manually juggling the > > Hibernate Session/Transaction...apparently Spring has an elegant > > solution through templates? > > imvho hibernate templates are not elegant at all. The transaction > management with Spring is a plus though. > > Unfortunately, the JBoss/ Seam guys seems to have made Seam (and that > JSR they are submitting) tightly coupled to JSF. That might have made > a nice alternative. Maybe. > > Eelco > > > _______________________________________________ > Wicket-user mailing list > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/wicket-user > <https://lists.sourceforge.net/lists/listinfo/wicket-user> > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
