I just started an EJB 3 project - which is more or less my first EE project, so please bear with me.
In the beginning I did not realize that I have to store a current user in my http session on the client side and pass it into almost each and every method of my session beans. (Why are they called 'session' beans when nothing in the bean or container itself actually deals with sessions?)
I take it that Seam would exactly solve this issue, right?
One of my requirements is that the sever part of the app (session and entity beans) is deployed in a separate ear. (The JSF part is in another ear).
So if I use seam, how will it actually determine the session scope?
