Nonsense. Post Hibernate questions on the Hibernate forum and don't hijack
other peoples threads.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081177#4081177
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081177
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.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081165#4081165
Reply to the post :
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.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081149#4081149
Reply to the post :
http://www.jboss.com/index.html?module=b
FYI, the decision between JPA and Hibernate also affects Seam functionality
available to you. For example, strangely only works with
JPA and not Hibernate.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081121#4081121
Reply to the post :
http://www.jboss.c
Thanks for the info :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081100#4081100
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081100
___
jboss-user mailing list
jboss-us
It's the same persistence context. You are simply casting to a proprietary API
when you have to. That's perfectly OK.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081081#4081081
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode
