I do not get it what is the difference between these sessions, if it's only based on performance?
The satateful bean is used to 'maintain users conversation state'. Considering that users state in web tier is managed through HttpSession (through an ID correctly),
does it measn when I pass some object from web tier to ejb, sesion id is passed too?
Or, when it said that stateful beans are used to maintain conversational state it mean only a rhetorically right? there is no some kind of id-trasmission between web tier and ejb tier, or it does? Dows Statefull beans have principle of storing some kind of HttpSession passed by web tier (if it does I donot see purpose of it)
If communication occurs mediating through web tier, user conversational state is maintained through HttpSession, only?!?!
We can use Statless bean with session facade in web tier, where we have an instance of stateless bean, and that instance invoke some method, inside what are encapsulated some business methods.
And here I come to conclusion (if my exposed opinion is correct) that only lyfecycles and performance issues, are peculiarities what make distinctions between these two beans.
These are not the droids you are looking for. Perhaps I can interest you in a tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton