It Seams to me there are two obvious ways to do a very common task.
For a Seam + EJB 3.0 based application.
Scenario: Need to maintain state between requests.
Solution 1: use statefull session beans and store into instance variables
Solution 2: use stateless session beans and use @In and @Out to store into Seam managed context variables
Which way is best?
What is more expensive? bijection or stateful bean management
It is well understood that SFSBs require more resources than SLSBs but now were are comparing SFSBs to bijection
I should have added: For my application there is a single server. Local session bean access not remote. The answer may differ for remote.
Comments on remote access and clustering are solicited as well but my primary interest is within a single JVM.