It's something we probably will try to get rid of for Wicket 2.0;
instead of the pessimistic, register first approach we have now, we
can choose an optimistic approach which will allow disallow in a
similar fashion as file filters work.
Eelco
On 5/10/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
also no cluster or what ever. Simple one tomcat installationThe only thing is you need to do some maintenance. So you shutdown tomcat or the webapp contextupdate it and restart it again. The shutdown did save the session to disk..
Then after restart all sessions comes in memory again. And the reque
imagine this situation w/out the use of initializeryou have a cluster where you do not use sticky sessionsuser comes to node A and requests a page. this page binds a bunch of resources that image components on this page need. browser starts to render one of these image components and makes a resour
HiCan somebody explain the purpose of PackageResource.bind() in IInitializer ?I tried to remove PackageResource.bind(application , Foo.class , "bar.gif") in IInitializerand ... keeps the following code intact in Page/Panel
add(new Image("myImage" , new PackageResourceReference(Foo.class, "bar.gif"
