Thanks Kent
I got the new cvs since the stack trace did show something about data
squeeze.
This does solve that issue but after setting the value to null I have an
"@If" statement which checks for the values existence, i.e. something like:
<tr jwcid="@If" condition="ognl:value1" element="tr">
since value1 is now not set (null), instead of the normal data squeeze "X",
this "@If" statement is true when previously in Beta-3 it was false, as
expected.
How can I make this "@If" false, or make the data squeeze return an "X"
instead of nothing (i.e. "" - a null String)?
Thanks again
Paul
seloha . <seloha <at> hotmail.com> writes:
I have a List which is displayed using jwcid=" <at> For" I am using
volatile="true".
I also have the List 'displayed' as a jwcid=" <at> Hidden".
When the form is submitted I reset the list to null. This causes the
jwcid=" <at> Hidden" to throw a NullPointerException. This did not happen
with Tapestry 4.0 beta-3.
Kent Tong wrote:
If the stack trace shows something about data squeezer, then it is a bug
in tapestry 4. A workaround is in the latest CVS, or you can check
chapter 1 (free download) of my book which shows you how to
apply the workaround yourself.
Author of an e-Book for learning Tapestry
(http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
