Question 60 - Final mock exam HFSJ

[Paul Statham]

The question is

When comparing servlet intialisation parameters to context initialisation parameters, which are true for both? (Choose all that apply.)

A. In their respective DD tags, they both have a <param-name> and a <param-value> tag.
B. Their repective DD tags are both placed directly under the <web-app> tag.
C. Their respective methods used to retrieve intialisation parameter values are both called getInitParameter.
D. Both can be directly accessed from a JSP.
E. Only changes to context initialisation parameters in the DD can be accessed without redeploying the web application.

The answers given are A+C, I think the answers should be A,C+D. The reason given for D being incorrect is

Option D: only context params can be directly accessed from JSPs

To me this is wrong, JSP has access to both application (ServletContext) and config (ServletConfig) implicit objects.

[Piyush Joshi]

I think the word that is tricky here is "directly accessed", which I guess here means directly by using parameter name. For example any Attribute can be directly accessed by its name ${attrName}. but you cant do ${initParamName}.

[Varun Chopra]

Option D is not correct and they have given a valid reason "only context params can be directly accessed from JSPs".
If you want to access servlet initialization parameters inside a JSP it is a tricky task. For this you need to treat your JSP as a servlet and also access it as a servlet in browser.
See this thread http://www.coderanch.com/t/177239/java-Web-Component-SCWCD/certification/init-param-jsp

[Paul Statham]

Ok you're right I suppose the method I was talking about would be something like

<%= application.getInitParameter("foo") %>
<%= config.getInitParameter("baz") %>

Which I suppose isn't direct. But if we were to use the EL example you've given it would still be

${applicationScope.foo}
${initParam.baz}

Edit: Ignore just noticed that initParam is actually a <context-param> not a <init-param>