Re: [Springframework-developer] Re: HibernateTemplate enhancement

[Colin S. <col...@ex...>]

Sourceforge anon access finally caught up with these changes, so I was 
able to pull them down.

Good stuff. However, is there any particular reason you didn't make a 
constructor of HibernateTemplate which includes the allowCreate flag in 
it (same as SessionFactoryUtils.getSession())?

There are a number of cases where HibernateTemplate can be used in a 
one-line fashion, as
  return new HibernateTemplate(_sessionFactory).load(theClass, id);
but if you need to set the allowCreate flag, that becomes
  HibernateTemplate ht = new HibernateTemplate(_sessionFactory);
  ht.setAllowCreate(false);
  return ht.load(theClass, id);

quite a bit more verbose. Now I know the HibernateTemplate instance 
itself can come out of the context, but that's not necessarily always 
the best choice...

Regards,
Colin


jürgen höller [werk3AT] wrote:

>Colin,
> 
>I've just added an "allowCreate" property to both HibernateTemplate and JdoTemplate, to support the use case you've outlined.
> 
>I've also finished entity interceptor support: LocalSessionFactoryBean, HibernateTemplate, HibernateInterceptor, and HibernateTransactionManager all feature a "entityInterceptor" property now, taken a net.sf.hibernate.Interceptor to apply at the respective level.
> 
>Furthermore, LocalSessionFactoryBean and LocalPersistenceManagerFactoryBean support "newConfiguration", "newSessionFactory", and "newPersistenceManagerFactory" factory and customization hooks now. This should allow to use any specifically preconfigured instance or custom subclass of these.
> 
>Regards,
>Juergen
> 
> 
>
>	-----Ursprüngliche Nachricht----- 
>	Von: Colin Sampaleanu [mailto:col...@ex...] 
>	Gesendet: Mo 28.07.2003 03:27 
>	An: spr...@li... 
>	Cc: jürgen höller [werk3AT] 
>	Betreff: HibernateTemplate enhancement
>	
>	
>
>	I think it would be useful to enhance HibernateTemplate to work in a
>	mode such that it doesn't create the session if it isn't already bound
>	on the thread. That is, there would be a new constructor which mirrors
>	the SessionFactoryUtils.getSession(factory, boolean) method signature.
>	
>	With the new convenience methods and the wrapping of Hibernate
>	exceptions, I think HibernateTemplate is useful in some cases even when
>	HibernateInterceptor is used to actually bind the session to the thread.
>	However, in the latter case, I am somewhat worrried about using
>	HibernateTemplate as it now exists since there is the danger of missing
>	the interceptor in one place and accidentally auto creating the session.
>	
>	
>	
>	
>	
>
>N?HS^?隊[)?{(??[?Z?z??n襴?4D?׬?w%?ا?6?i???l?&???x?+??ljwE??????j??zz0?'?????Zɩ?z{^??0?v?\???b??J۝??DNm??ڲ?޵?brK???&?
>??ƴ?]4?Mڽ?݊????Z??޷N??M???5J???jg???z??????x%??R?????ڙ?(?G^??h????l???q???z?m????X???(??~??zw??X?????b???????jg???z??
>