Comprehensive Guide to Setting Session Attributes in Java: From JSP Scriptlets to Servlet Implementation

Fundamental Principles of Session Attribute Setting

In Java Web development, session management serves as the core mechanism for maintaining user state. Many developers encounter the "session cannot be resolved" error when transitioning from JSP scriptlets to Java classes, which stems from insufficient understanding of session acquisition mechanisms.

Session Setting in JSP Scriptlets

Within JSP pages, the session object is implicitly available, allowing direct attribute setting through scriptlets:

<%
String username = (String)request.getAttribute("un");
session.setAttribute("UserName", username);
%>

While this approach is straightforward, it violates MVC design principles by mixing business logic with the presentation layer.

Proper Implementation in Servlets

In Servlet classes, the session must be explicitly obtained through the HttpServletRequest object:

public void doGet(HttpServletRequest request, HttpServletResponse response) {
    HttpSession session = request.getSession();
    String username = (String)request.getAttribute("un");
    session.setAttribute("UserName", username);
}

The request.getSession() method returns the HttpSession object associated with the current request, creating a new session if none exists. This represents the standard approach defined by the Servlet specification.

Session vs Request Scope Comparison

Understanding the distinction between session and request scopes is crucial:

• Session Scope: Data remains valid throughout the user session, suitable for user login information, shopping cart contents, and other data requiring persistence across multiple requests
• Request Scope: Data is only valid during a single request-response cycle, appropriate for temporary data transfer between pages

Attribute Lifecycle Analysis

Considering a page flow scenario: page1→page2→page3→page4

• Attributes set using session.setAttribute() remain available across all pages
• Attributes set using request.setAttribute() in page2 are only accessible in page3
• Request parameters obtained via request.getParameter() exist only in the original request

Best Practice Recommendations

1. Avoid direct session manipulation in ordinary Java classes; manage sessions through Servlets or controller layers

2. Choose scope appropriately: use session for long-term data, request for temporary transfer

3. Promptly clean up unnecessary session attributes to prevent memory leaks

4. Consider using filters or interceptors for unified session logic handling

Common Issue Resolution

When encountering "session cannot be resolved" errors, verify:

• Whether HttpSession is correctly obtained within Servlet's doGet/doPost methods
• Whether the class properly extends HttpServlet and overrides service methods
• Whether web.xml configuration or annotations are correctly set