: Orchestra integration with legacy Hibernate 2 app
To: Reply-MyFaces Discussion users@myfaces.apache.orgTo: MyFaces
Discussion users@myfaces.apache.org
Mario,
Thanks for that response to my question about that Session is closed! error
when trying to use HibernatePersistenceContextFactory (HPCF
Hi!
I made my simple test app work by stripping out all the JPA stuff I
had, both in the code and the applicationContext.xml, and then using
Spring to inject the DAO with a LocalSessionFactoryBean. Is that the
right way to approach it? (Or is that a naive solution, with lurking
problems?)
At 06:52 AM 9/8/2007, Mario wrote:
whm wrote:
Right away I noticed that there's no SessionHolder in Spring's
Hibernate 3 support. I see some things further down that may be a
problem, too, but my understanding of the machinery is tenuous at best.
I've found a SessionHolder in my spring-2.0.6
Mario,
Thanks for that response to my question about that Session is
closed! error when trying to use HibernatePersistenceContextFactory (HPCF).
I made my simple test app work by stripping out all the JPA stuff I
had, both in the code and the applicationContext.xml, and then using
Spring to
I'm involved with a legacy web app project using Java 5, Struts 1.x,
JSF 1.1, Hibernate 2, Spring 1.x, some EJB2s and more. Orchestra has
caught our eye as way to do some refactoring to take full advantage
of Hibernate's lazy-loading across a series of requests. (A
conversation, of course.)
Hi!
The Orchestra installation page has a tantalizing sentence: The
installation guide will show you how to setup a JPA entity manager
..., later a chapter explaining how to access Hibernate directly will
be added.
Yep, we use it here with a completely custom way of how to get in touch
to the
6 matches
Mail list logo
