Ah, finally I found why is it wrong. Its bad HFSJ doesn't cover this.
This is from JSP Spec JSP.5.3 1-108
The object named by the name must have been “introduced” to the JSP processor using either the jsp:useBean action or a custom action with an
associated VariableInfo entry for this name. If the object was not introduced in this manner, the container implementation is recommended (but not required) to raise a translation error, since the page implementation is in violation of the specification.
Note – A consequence of the previous paragraph is that objects that are stored in, say, the session by a front component are not automatically visible to jsp:set- Property and jsp:getProperty actions in that page unless a jsp:useBean action, or some other action, makes them visible.
If the JSP processor can ascertain that there is an alternate way guaranteed to access the same object, it can use that information. For example it may use a scripting variable, but it must guarantee that no intervening code has invalidated the copy held by the scripting variable. The truth is always the value held by the pageContext object.
Hey Lee thnx, even after posting my last post, I was wondering you wouldn't have posted what you wrote without knowing something concrete and then I consulted the spec.
Kamal Tripathi
SCJP 1.4 90%, SCWCD5 94%, Next SCDJWS--> In Naescent stage. Researching abt exam and material itself.