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

I wonder if those were overwritten or it's some kind of harmless fluke bug that magically works on my system, although I see what you're saying... 

But going back on topic, I'd say it fits somewhere between best practices (instantiating an object on the back end - although I'd imagine leaving the object null is ever so slightly more speed/memory efficient, particularly with HashMaps), and perhaps dealing with the ww tags... I'd trust in your opinion on putting it in a sensible location.

It would be nice if something threw at least a warning when a method is not found. Do you know if there is already logging/exception handling that I'm just not using, or would this always occur transparently?

To me, if just feels like the caveat either unnecesarily complicates things "((x == null) || (x.isEmpty()))" or detracts from the MVC paradigm.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=55613&messageID=110652#110652