Ok...it worked after upgrading to Wicket 1.3.4
So, the problem was what Richard mentioned below "that in wicket 1.3.3
enclosure wouldn't call isVisible() after first time"
Thanks again.
Rachit
nanotech wrote:
>
> Hi Richard,
>
> Thanks for the reply. I am using 1.3.3
> I will update to 1.3.4
Hi Richard,
Thanks for the reply. I am using 1.3.3
I will update to 1.3.4 and try again.
Thanks,
Rachit
richardwilko wrote:
>
> There was a bug in enclosure in 1.3.3, where it wouldn't call isVisible
> after the first time (fixed in 1.3.4) which version are you using?
>
>
>
>
> nanotech w
There was a bug in enclosure in 1.3.3, where it wouldn't call isVisible after
the first time (fixed in 1.3.4) which version are you using?
nanotech wrote:
>
> The line below
> pojo.setSampleText(pojo.getSampleText());
> should be ignored.
>
> Thanks,
>
>
>
> nanotech wrote:
>>
>> Hi All,
The line below
pojo.setSampleText(pojo.getSampleText());
should be ignored.
Thanks,
nanotech wrote:
>
> Hi All,
>
> I have a simple requirement in which I want to display two different
> messages on Form Submit depending on whether or not the text field is
> filled in . The way I thought it
Hi All,
I have a simple requirement in which I want to display two different
messages on Form Submit depending on whether or not the text field is filled
in . The way I thought it should work is if I use combination of AjaxButton,
WebMarkupContainer, and by overriding isVisible().
The flow of sam
