anonymous wrote : At first it would seem to the neophyte like me a more natural
way to keep the object itself and perhaps merge it at the beginning of each
conversation.
Thats a valid alternative approach, but doesn't work so nicely with EntityHome.
anonymous wrote : (issue aside I wonder if th
Thanks for you answer, although I don't see a hit to database at the beginning
of every conversation much extra load I would like to know more about why
keeping just the Id is better.
At first it would seem to the neophyte like me a more natural way to keep the
object itself and perhaps merge i
I think I've found the precise answer in last reply of
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103356
the @Out scope doesn't rely on the scope of @In, it must declared individually:
@Out(scope=ScopeType.SESSION)
that's why I wasn't reaching same instance between calls
great fo
This is my preferred solution
http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamEntityHomeForLongRunningContexts
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109973#4109973
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=41
I could, of course, load the user and collection from database every time, but
I don't think this is the best way
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109965#4109965
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
