Session/jstl and load balancing - need expert advice

Question

After user loggs in, I am getting locale from db and storing it inside userSession along with userLogin. Inside jsp using <fmt> tag to display locale based resource property.
HttpSession userSession = request.getSession(true);
userSession.setAttribute("UserLogin", oRS.getString("user_login"));
Config.set(userSession, Config.FMT_LOCALE, currentLocale);Also using filter after login page to check for User Session. Currently all working fine .
But if i want to make use of load balancing, whether still it will work?
1)I understand that if i depend on network config i.e. session request sticks to one server then i believe shld not be a problem
2)But if that is not the choice then what else ? Client want to make use of serialization technique. I do not know much about it, how to implement it, any sample is greatly appreciated.
3)what about jstl Config.set(..) whether any changes needed here?
4)Do i need to change filter code.
Pls pls help me, i really need expert advice on this.
regards
Manisha

Answer 1

1)If i want cluster server to replicate the session
then all attributes saved in the session have to be
serializable.yes.
2)In docs it is mentioned
Use setAttribute to Change Session State
In an HTTP servlet that implements
javax.servlet.http.HttpSession, use
HttpSession.setAttribute (which replaces the
deprecated putValue) to change attributes in a
session object. If you set attributes in a session
object with setAttribute, the object and its
attributes are replicated in a cluster using
in-memory replication. If you use other set methods
to change objects within a session, WebLogic Server
does not replicate those changes. Every time a change
is made to an object that is in the session,
setAttribute() should be called to update that object
across the cluster.
Whether it means that if I want to store a object
(which is serializable) e.g. 'String' inside session
and use setAttribute() method then I do not need to
make that object implicitly serializable?No, you still need the objects to be serializable.