L PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Juergen
> Donnerstag
> Sent: Friday, July 07, 2006 2:28 PM
> To: wicket-user@lists.sourceforge.net
> Subject: Re: [Wicket-user] Panel visibility
>
> Are you sure it not a caching issue? Your browser caching the page?
> Did you
#x27;s now gone. Oh, well.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Juergen
Donnerstag
Sent: Friday, July 07, 2006 2:28 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Panel visibility
Are you sure it not a caching issue? Your
Are you sure it not a caching issue? Your browser caching the page?
Did you modify the response header to disable client caching?
Juergen
On 7/7/06, Frank Silbermann <[EMAIL PROTECTED]> wrote:
>
>
> I'm using Wicket 1.2, and I've included on my page a subclass of Panel. In
> response to an event
I'm using Wicket 1.2, and I've included on my page a
subclass of Panel. In response to an event, I called
"myPanel.setVisible(false)" but the panel remains visible. Is this a known
bug, or do I need to do something to implement "void setVisible(boolean)" in my
subclass?
Using Tomcat but ne