Lazy loading exception with Seam EM

[trouby]

Hey,

I have a very simple authenticate component as in all seam examples such:

@In
EntityManager entityManager;

@Out(required=false, scope = SESSION)
User loggedUser;


public boolean authenticate() {
//load the user from db and set it into 'loggedUser' var
}





Well it works fine, the loggedUser object is being outjected to the session, the problem is that when I touch the collections of the 'loggedUser' entity (that are fetched lazily) I get lazy collection exceptions,


shouldn't any entity loaded by Seam's EM has to being in managed state for the whole user session (as long as I'm always using Seam's EM of course) ?


Thanks,

Asaf.

[trouby]

Uh, my mistake, EM is bound per conversation,

So there is no solution for this need?
The logged user may have many lazy relationships which are sometime accessed directly by the view,

I find myself doing stuff like:
loggedUser.getSomeRelationShip().size();

before outjecting to the session so the information will be available for the view later on, but this is not elegant solution,


Thanks,

Asaf.

[pmuir]

One way is to use

http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamEntityHomeForLongRunningContexts