I recently tried updating from a Tapestry 4.1.2 snapshot a couple months
old to one from 3-21. Along the way I had to incorporate the new 2.7
OGNL snapshot from 3-18. I'm seeing multiple expressions on each page
that no longer work. So far they have all involved AND expressions. Here
are some examples:
info.rootCause.getMessage() != null &&
info.rootCause.getMessage().length() > 0
currentElement.message != null && currentElement.message.length() > 0
sysMessages != null && sysMessages.size() != 0
title != null && title.length() > 0
Here is an example error message:
Error compiling expression on object
[EMAIL PROTECTED]/$SystemMessageDisplay
] with expression node (sysMessages != null) && (sysMessages.size() !=
0) getter body: { return ($w)
((ognl.OgnlOps.booleanValue((($SystemMessageDisplay_245)$2).getSysMessag
es() != null) ? ognl.OgnlOps.convertValue(!ognl.OgnlOps.equal( ($w)
ognl.OgnlOps.convertValue((($SystemMessageDisplay_245)$2).getSysMessages
().size(), java.lang.Integer.class) , ognl.OgnlOps.convertValue(0,
java.lang.Integer.class)), java.lang.Integer.class) :
(($SystemMessageDisplay_245)$2).getSysMessages() != null));} setter
body: { _node.setValue($1, $2, $3); }
Our app is now specless so any objects being accessed are defined on the
Java class. I can open a case in the OGNL issue tracking system but I
wanted to check if anyone knows what is going on first since I don't
want to have to go through and convert hundreds of expressions to Java
code if I can avoid it (still haven't even gotten our Home page to come
up yet..)
Thanks,
Ben
