This content has been marked as final.
Show 6 replies
-
1. Re: Switching to Hibernate or not
christian.bauer Sep 4, 2007 4:34 PM (in response to rlhr)It's the same persistence context. You are simply casting to a proprietary API when you have to. That's perfectly OK.
-
2. Re: Switching to Hibernate or not
rlhr Sep 4, 2007 5:21 PM (in response to rlhr)Thanks for the info :)
-
3. Re: Switching to Hibernate or not
igx89 Sep 4, 2007 6:36 PM (in response to rlhr)FYI, the decision between JPA and Hibernate also affects Seam functionality available to you. For example, <s:convertEntity /> strangely only works with JPA and not Hibernate.
-
4. Re: Switching to Hibernate or not
christian.bauer Sep 4, 2007 10:01 PM (in response to rlhr)Of course not. I use the Hibernate JPA provider, cast to org.hibernate.Session when I have to, and s:convertEntity works fine as well.
-
5. Re: Switching to Hibernate or not
samdoyle Sep 4, 2007 11:27 PM (in response to rlhr)Unfortunately you cant have more then OneToMany mappings with EAGER FetchType or your application blows ups. If you set one to be LAZY it blows up. Please see my recent post.
-
6. Re: Switching to Hibernate or not
christian.bauer Sep 5, 2007 2:57 AM (in response to rlhr)Nonsense. Post Hibernate questions on the Hibernate forum and don't hijack other peoples threads.