InfoCenter Home >
3: Migration overview >
3.3: Migrating APIs and specifications >
3.3.6: Migrating session management >
3.3.6.1: Migrating from Version 2.0 session support

3.3.6.1: Migrating from Version 2.0 session support

Note these changes to the implementation of sessions in IBM WebSphere Application Server Version 2.x.

  • The public classes in the com.ibm.servlet.personalization.sessiontracking package have been deprecated.

    Application developers can still compile servlets using the old classes. (Specifically, the IBMSessionData class typecast still works). However, the functions will return null or constant values, and no processing or setting of values will occur.

  • Extensions for sessions to the Java Servlet API are now encapsulated in the com.ibm.websphere.servlet.session.IBMSession interface.
  • If URL encoding is configured and response.encodeURL() or encodeRedirectURL() is called, the URL is encoded, even if the browser making the HTTP request processes cookies. This differs from the behavior in previous releases, which checked for the condition and halted URL encoding in such a case.
Go to previous article: Migrating session management Go to next article: Migrating to supported security APIs

 

 
Go to previous article: Migrating session management Go to next article: Migrating to supported security APIs