Keep SFSB stub in HttpSession!?

[tsar_bomba]

I posted earlier about having problems keeping values in-state using a stateful session bean.

Looking through the TrailBlazer app, I think I found the answer:

http://trailblazer.demo.jboss.com/EJB3Trail/serviceobjects/sfsb/index.html

...which leads me to a *new* question.

If I have to keep a stub of the SFSB's interface in an HttpSession, why on earth would I use a Stateful bean at all?? Why would I need the additional overhead of a Stateful bean on the server if I have to store it in the web layer in-session anyhow?

Why wouldn't I just use a Stateless bean stored in the HttpSession...which gives me essentially the same result, doesn't it?

Obviously, I'm very new to EJB...so bare with me.

Thanks!

[starksm64]

The difference is in the api used to work with the state. Try both and asses the difference.