ok! @Repository, @Service, @Transactional etc are all exemples of great annotations schemas that eliminate the need of a significant amount of xml bean definition! I totally support that! By the way, I have read on the net that there are some people supporting the ideia of eliminating the HibernateTemplate from the DAO layer. Instead of using the hibernateTemplate it would be nice to eliminate this wrap class and inject the sessionFactory straight into your DAO code. Matt, what's your point of view about that!? Do you think it would be worth change the DAO layer of appfuse project and get the session in this straight-foward way? the only thing that I am concerned about is the checked excepetions, but that as I have been reading can be easilly treated using this
<bean class= "org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor" /> here it is what have been reading about. http://blog.springsource.com/2007/06/26/so-should-you-still-use-springs-hibernatetemplate-andor-jpatemplate/ and this http://blog.springsource.com/2006/08/07/using-jpa-in-spring-without-referencing-spring/ HTHs Flavio Oliva On Tue, Apr 6, 2010 at 5:32 PM, Matt Raible <m...@raibledesigns.com> wrote: > It's been done in SVN. I've also done some work to convert Controllers to > annotations. It's checked in in AppFuse Light, not AppFuse. The work is > sitting in my local workspace. All tests aren't passing yet. > > > On Mon, Apr 5, 2010 at 5:21 PM, Flávio Oliva <deno...@gmail.com> wrote: > >> is there any prespective of upgrading appfuse to spring 3.0? I think that >> upgrate to that would be a minor impact? maybe on Milestone 3? eheheh >> >> regards to all, >> >> Flávio Oliva >> > >
