Chris Pratt wrote:
<!-- Equals(): <s:property
value='%{originalMember.name.equals(currentMember.name)}'/> -->
Just to be pedantic, can you also verify that:<!-- Equals(): <s:property value='%{currentMember.name.equals(originalMember.name)}'/> -->
yields: <!-- Equals(): true --> ?All correctly implemented equals methods are symmetric, so in the event OGNL decides that neither of these are null and that it should call the equals() method, it could theoretically do so in either order. If the reversed order (above) throws an exception then that would explain the observed output.
Assuming that's not it, I'd suggest instrumenting your model to log when the equals and getName methods are called so you can verify it's making the calls you expect.
I agree it does seem strange. Also: Which version of ognl are you using? -Dale --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
