Clarification required -HFSJ page 447
Sayak Banerjee
Ranch Hand
Posts: 292
posted 10 years ago
Twon thing I'd like to point out in this page which I don't think is correct:
1.> In the "Key points and gotchas" column the last point says:
This is NOT TRUE...if you use ${fooBean.notAProperty} and the property "notAProperty" is not a property of this bean, the container throws an ELException.
2.>Just beside this column, in the Q & A section, the second one reads:
What exactly is implied here? Did they mean that if the Container finds an attribute of that name in any of the 4 scopes( say application scope) then it's replaced by this one in that scope.....or is it meant that if an attribute is found in any of the four scopes then the new value is not set?
Well, both don't hold good....If you don't specify a "scope", the Container sets the new attribute in the page scope...I've tried it out and that's what I've got.
Could anybody please confirm this.....it would be very helpful....
Many thanks in advance.
1.> In the "Key points and gotchas" column the last point says:
If the target expression is a bean, but the bean does not have a property that matches "property", the Container throws an exception. But be careful, because the EL expression by itself will NOT cause an exception to be thrown if the property doesn't exist. So even though : ${fooBean.notAProperty} won't cause an exception by itself(it just returns null), if that same "notAProperty" is the value of a "target" attribute, the Container throws an exception.
This is NOT TRUE...if you use ${fooBean.notAProperty} and the property "notAProperty" is not a property of this bean, the container throws an ELException.
2.>Just beside this column, in the Q & A section, the second one reads:
Q: If I don't specify a scope, does that mean it will find attributes that are ONLY within page scope, or does it do a search beginning with page scope?
A: If you don't use the optional "scope" attribute in the tag, and you're using "var", the container will search scopes in the order in which you've come to expect--page, then request, then session, then application(context).
If you use the var version without a scope, and the Container can't find an attribute of that name in any of the 4 scopes, the Container makes a new one in page scope.
What exactly is implied here? Did they mean that if the Container finds an attribute of that name in any of the 4 scopes( say application scope) then it's replaced by this one in that scope.....or is it meant that if an attribute is found in any of the four scopes then the new value is not set?
Well, both don't hold good....If you don't specify a "scope", the Container sets the new attribute in the page scope...I've tried it out and that's what I've got.
Could anybody please confirm this.....it would be very helpful....
Many thanks in advance.
Turn on, tune in, drop out.
Sreeraj G Harilal
Ranch Hand
Posts: 310
Sreeraj G Harilal
Ranch Hand
Posts: 310
posted 10 years ago
Your second point.
You are right, Sayak. Its really a good piece of information.
<c:set var="avar" value="Preparing for SCWCD" scope="session"/>
<c:set var="avar" value="My Name is sreeraj"/>
${pageScope.avar}<br>
${sessionScope.avar}<br>
it displays
My Name is sreeraj
Preparing for SCWCD
You are right, Sayak. Its really a good piece of information.
<c:set var="avar" value="Preparing for SCWCD" scope="session"/>
<c:set var="avar" value="My Name is sreeraj"/>
${pageScope.avar}<br>
${sessionScope.avar}<br>
it displays
My Name is sreeraj
Preparing for SCWCD
SCJP 5.0<br />SCWCD 1.4<br />Preparing for <b>SCEA</b>.<br /><b>"I prefer an interesting vice to a virtue that bores."</b>
Sayak Banerjee
Ranch Hand
Posts: 292
posted 10 years ago
The first point says if you use a non-existent bean property in an EL expression, it does not throw an Exception(please check the part of the sentence in bold)....but that is NOT TRUE....that too throws an ELException
Try this code...you'll get an ELException
[ December 22, 2006: Message edited by: Sayak Banerjee ]
Try this code...you'll get an ELException
[ December 22, 2006: Message edited by: Sayak Banerjee ]
Turn on, tune in, drop out.
Ali Gohar
Ranch Hand
Posts: 572
posted 10 years ago
Yes i can also see javax.servlet.jsp.el.ELException exception while trying to access a property of bean which doesn't exist.
So i think that which is written in the book is invalid. BTW i don't have HFS&J book
So i think that which is written in the book is invalid. BTW i don't have HFS&J book
