0

Earlier days when I used to do coding, I used mostly Stateless Session Beans and all the info needed to traverse across pages was put in HTTP Session object. Back then(and even now) I never understood the "USP" of EJB being "transparent" and "safe" for "business layer" implementation with its round about ways of dealing with Skeleton and Stub and other jargons which were an overkill masquerading in the name of ease of use/secure. I was just wondering why exactly one would have used Stateful Session EJB, if the same can be accomplished via a SLSB + HTTPSession? Please dont give me the high level example of Shopping cart or bank app, as I already know that. I am looking for some answer that would be detailed on why coders chose SFSB over SLSB+HttpSession. Plus how are these session related stuff handled in your experience recently?

Spear A1
  • 525
  • 1
  • 7
  • 20

1 Answers1

0

You are supposing that the view layer always is a http client. But the view layer can be architected in other ways. For example a Java Swing client application (Where the client server communication is done only with ejbs.

A question that helps diff SFSB vs HttpSession. Stateful Session Bean and HTTP Session

Henrique Fernandes Cipriano
  • 555
  • 6
  • 17
  • Thanks for attempting to answer my question Henrique. I am curious to know how Swing , which is an UI Framework not work with Http protocol. Also not to get hijacked from the main topic, I am looking to understand why "coders chose SFSB over SLSB+HttpSession? " – Spear A1 Aug 19 '18 at 22:15