Lazy loading works inside a persistence context. So it depends what is the scope of your persistence context. If you are using:
@PersistenceContext EntityManager em; Then you have a container-managed PC that is open only for the scope of the transaction. @PersistenceContext(type=EXTENDED) EntityManager em; Then you have a container-managed PC that is open whenever a transaction is running, for the lifetime of the SFSB. If you are using: @In(create=true) EntityManager em; then what you have is a (Seam-managed) conversation-scoped PC and it will be open only for the scope of the conversation. You can only lazy-fetch within the scope of a PC (for all kinds of excellent reasons). It would not usually make sense to have a conversation-scoped PC on a session-scoped SFSB. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916509#3916509 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916509 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
