RajaSekhar Reddy t

• Sep 11th, 2005

 

You can pass the HttpSession as parameter to an EJB method, only if all objects in session are serializable.

This has to be consider as "passed-by-value", that means that it's read-only in the EJB. If anything is altered from inside the EJB, it won't be reflected back to the HttpSession of the Servlet Container.

The "pass-by-reference" can be used between EJBs Remote Interfaces, as they are remote references

k_yogi85

• Apr 16th, 2007

 

You can pass the HttpSession as parameter to an EJB method, however you should have all objects in session be serializable.This has to be consider as passed-by-value, that means that it’s read-only in the EJB. If anything is altered from inside the EJB, it won’t be reflected back to the HttpSession of the Servlet Container.
The pass-by-reference can be used between EJBs Remote Interfaces, as they are remote references.
While it is possible to pass an HttpSession as a parameter to an EJB object, it is considered to be bad practice in terms of object-oriented design. This is because you are creating an unnecessary coupling between back-end objects (EJBs) and front-end objects (HttpSession).
Better way to do it is, create a higher-level of abstraction for your EJBs API. Rather than passing the whole, fat, HttpSession (which carries with it a bunch of http semantics), create a class that acts as a value object (or structure) that holds all the data you need to pass back and forth between front-end/back-end. Consider the case where your EJB needs to support a non HTTP-based client. This higher level of abstraction will be flexible enough to support it.

Bhaktavatsalam Gani

• May 21st, 2007

 

It is not possible to pass the HttpSession as part of the EJB method parameter. Because it is not serializable. If we want to pass the session information we need to create another class that can hold all the session values in a serializable form.