Re: It's a trap! OGNL / ww:if pitfall

No, because it would look for getIsEmpty() or isIsEmpty() - I've made similar mistakes in the past when I wasn't paying attention, that's why I pointed that out.

As for the not found/null evaluating to false - I'd say that's indeed the expected behaviour. With the caveat, as you pointed out, that one should indeed make sure that the return value from the getter is not null, or that you have to keep that rule in mind.

Is there a certain page you would like to see updated or clarified ?
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=55613&messageID=110618#110618