1. Accueil
  2. Development
  3. RE: How to get session attribute from different RESt builder different APIs

RE: How to get session attribute from different RESt builder different APIs

RAVI RAJAMANI, modifié il y a 5 années.
How to get session attribute from different RESt builder different APIs?
Regular Member Publications: 123 Date d'inscription: 07/12/14 Publications récentes
How to get session attributes from different modules , RESTbuilder API modules.

say Module1 and Module2

In Module1 i had saved session value like below

HttpSession httpSession = contextHttpServletRequest.getSession(true);
httpSession.setAttribute("fooKey", "fooValue");

In Module2 i had getting session value like below
HttpSession httpSession = contextHttpServletRequest.getSession(true);
String value = (String) httpSession.getAttribute("fooKey")
System.out.println(value); // null is coming
Getting null , cannot able to getAttribute from different module
thumbnail
David H Nebinger, modifié il y a 5 années.
RE: How to get session attribute from different RESt builder different APIs
Liferay Legend Publications: 14933 Date d'inscription: 02/09/06 Publications récentes
You should not do this. The APIs are intended to be stateless. They are not built to support maintaining state across calls.
RAVI RAJAMANI, modifié il y a 5 années.
RE: How to get session attribute from different RESt builder different APIs
Regular Member Publications: 123 Date d'inscription: 07/12/14 Publications récentes
David H Nebinger:

You should not do this. The APIs are intended to be stateless. They are not built to support maintaining state across calls.
Is there any other way to achieve like this ? 
thumbnail
Christoph Rabel, modifié il y a 5 années.
RE: How to get session attribute from different RESt builder different APIs
Liferay Legend Publications: 1555 Date d'inscription: 24/09/09 Publications récentes
When you use rest calls, the application is usually the client and the application state is then held in the browser. The other option is to store only a key in the application and the rest of the information in the database.
Even if you find a momentary way around this, e.g. by using a cache or singleton + hash, believe me, it probably will bite you later on.