This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
What you want to do is check to what object these implicit objects are associated, for instance request maps to HttpServletRequest. Then simply check the API. Whatever is conform to the JavaBean standard will be accessible via EL.
JDBCSupport - An easy to use, light-weight JDBC framework -
1- pageScop ---------- Map of scope attribute
2- requestScope ---------- Map of scope attribute
3- sessionScope ---------- Map of scope attribute
4- applicationScope ---------- Map of scope attribute
5- param ---------- Map of request parameter
6- paramValues ---------- Map of request parameter
7- header ---------- Map of request headers
8- headerValues ---------- Map of request headers
9- cookie ---------- Map of cookie
10- initParam ---------- Map of context init param
11- pageContext ---------- PageContext object
Except pageContext, all are the map object which will be holding key- value pairs. pageContext is real reference to PageContext object so that we can get any other implicit object as well as any attribute in any scope:-
getAtribute(String name, int scope)
Guys excuse my message it was regarding the implicit objects you use in Scriptlets ;)
Joined: Oct 26, 2008
Thanks guys for all your answers.
i am kind of clear with 10 map implicit objects.atleast i think so..
but with pageContext object its not quite clear -
if i want to print the request URI -
<%= request.getRequestURI() %>
so here the method getRequestURI() becomes property requestURI .
i know its intuitive to figure out the property name from method name.
but still i am used to check the api's .so do we have something for checking EL stuff.
(whereas, jsp implicit objects - methods remain as it is.
Well the "get" prefix is a javabean standard. EL adds the get prefix to properties that you access from bean objects. So if you write bean.name, it will be like calling bean.getName(). The pageContext object's type is the actual PageContext. But you can only access the properties that follows the javabean naming convention, so you can only call the methods that have the "get" or "is" prefix. That is why you write pageContext.request, which is like pageContext.getRequest...