On Thu, 7 Nov 2002, Joel Carklin wrote:
> Thanks Shawn, that works great. Just wondering, in the line
> <c:out value="${myMap.key}"/>
> no scope is identified. In my case it is a requestScope Map, but I only
> just noticed I never said requestScope.myMap.key
> Does this mean that the request scope is 'default' or assumed?
Not xactly. By default, all of the scopes are searched (in increasing
order of generality -- that is, page, then request, then session, then
application) until a variable is found. (Technically, the order isn't
important because the JSP specification suggests that all the scopes
constitute a single namespace. But since the specification doesn't
mandate that containers implement this suggestion, many don't, which leads
to the view by most developers that each scope has a separate namespace.)
> or doesn't it matter because the page is in request scope, session
> scope, application scope etc and will find myMap wherever it may be?
Right, exactly.
--
Shawn Bayern
"JSTL in Action" http://www.manning.com/bayern
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://archives.java.sun.com/jsp-interest.html
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.jsp
http://www.jguru.com/faq/index.jsp
http://www.jspinsider.com
