The Jalo layer in hybris is depreacted, not the jalosession.

Whenever a REQUEST is made to hybris server, it may need current user details, currency, language, timezone etc to serve that request efficiently. SINCE HttpSession does not hold all these details, hybris came up with the CONCEPT of JaloSession.

Whenever a request comes to Hybris, the FILTER HybrisInitFilter creates an object of JaloSession. Every JaloSession object is associated with a SessionContext object, which has current user, language, currency etc and the current httpSession object.

• Cron jobs ALSO run in a JaloSession.
• Each JaloSession is bound to a tenant. This cannot be changed, after the instance of JaloSession is created.
• JaloSession is never made persistent in database.

The Jalo layer in hybris is depreacted, not the jalosession.

Whenever a request is made to hybris server, it may need current user details, currency, language, timezone etc to serve that request efficiently. Since HttpSession does not hold all these details, hybris came up with the concept of JaloSession.

Whenever a request comes to Hybris, the filter HybrisInitFilter creates an object of JaloSession. Every JaloSession object is associated with a SessionContext object, which has current user, language, currency etc and the current httpSession object.