(last try; if the apache.org mailserver rejects this too I'm giving up)
Yup, it's working now. I'd mistakenly pruned out all the valid VTL references and only left in the invalid one in the test case (blushes), i.e. the opposite of what I'd intended to do :).
So, it was just the null that was causing the whole problem!
Thanks.
Nathan Bubna wrote:
workings of your app. so, if you have a reference (whether $ref or $obj.ref) that you can reasonably expect to return or be null, then you should be using silent notation. this is essentially what the warning is trying to tell you, though i readily confess that it isn't clear from the message.
Yup.
That error message ought at least to make explicit mention of null as a possible cause, since null is OFTEN a valid return value for
but there can be something wrong with displaying unrendered references in a template language. thus the warning message.
Clarification: I'm arguing that because it often is valid, velocity needs to go a little further in informing the developers that it has happened.
I didn't mean to imply that velocity ought to always display "null" in a template, but only that it ought to explicitly SOMEHOW be telling the developer that a null was received.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
