If you store your user with the conversation, the login information will
disappear when you end the conversation. This would almost never be the
behavior you want.
To eagerly load a relationship, use a join fetch. Check out any EJB3 book
(like Bill's new one with O'Reilly) to see how to do that. Here are a couple
of examples from the Seam examples:
| em.createQuery("from Order o join fetch o.orderLines where o.orderId =
:orderId")
|
| entityManager.createQuery("from Blog b left join fetch b.blogEntries")
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954554#3954554
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954554
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
