CODEWITHSUNDEEP
javajspservletsel
Alex
Alex

Reputation: 3413

How to access a request attribute set by a servlet in JSP?

I'm trying to retrieve attribute values set by a servlet in a JSP page, but I've only luck with parameters by ${param}. I'm not sure about what can I do different. Maybe its simple, but I couldn't manage it yet.

public void execute(HttpServletRequest request, HttpServletResponse response) {

    //there's no "setParameter" method for the "request" object
    request.setAttribute("attrib", "attribValue");

    RequestDispatcher rd = request.getRequestDispatcher("/Test.jsp");
    rd.forward(request,response);
}

In the JSP I have been trying to retrieve the "attribValue", but without success:

<body>
    <!-- Is there another tag instead of "param"??? -->
    <p>Test attribute value: ${param.attrib}
</body>

If I pass a parameter through all the process (invoking page, servlets and destination page), it works quite good.

Upvotes: 30

Views: 99728

Answers (4)

Kumar Abhi
Kumar Abhi

Reputation: 31

If the scope is of request type, we set the attribute using request.setAttribute(key,value) in request and retrieve using ${requestScope.key} in jsp .

Upvotes: 3

mooonli
mooonli

Reputation: 2393

have you tried using an expression tag?

<%= request.getAttribute("attrib") %>

Upvotes: 4

smwikipedia
smwikipedia

Reputation: 64175

Maybe a comparison between EL syntax and scriptlet syntax will help you understand the concept.

  • param is like request.getParameter()
  • requestScope is like request.getAttribute()

You need to tell request attribute from request parameter.

Upvotes: 11

BalusC
BalusC

Reputation: 1108632

It's available in the default EL scope already, so just

${attrib}

should do.

If you like to explicitly specify the scope (EL will namely search the page, request, session and application scopes in sequence for the first non-null attribute value matching the attribute name), then you need to refer it by the scope map instead, which is ${requestScope} for the request scope

${requestScope.attrib}

This is only useful if you have possibly an attribute with exactly the same name in the page scope which would otherwise get precedence (but such case usually indicate poor design after all).

See also:

Upvotes: 38

Related Questions