All,

Can someone point me to the technical details of where and what Wicket caches? I'm not talking about the programming object model as such. I mean more practical matters such as:

 * In what directory does Wicket store cached stuff (e.g. page
   versions)? Is this just the Java temporary directory (e.g. %Temp% on
   Windows)? Is this some standard directory in the the servlet
   container? If I'm using embedded Jetty, any idea where I could find
   the cached Wicket stuff?
 * What naming convention does Wicket used for caches? If I find the
   temporary directory, how could I figure out which things are from
   Wicket? Which things are cached paged versions?
 * How can I tell Wicket to throw away all old caches? I found out
   (sadly) today on the users list that there's no easy way to turn off
   Wicket page versioning, which means that no matter what I do, I'm
   going to have a bunch of outdated cache junk for versioned pages
   lying around somewhere. How do I get rid of them? How do I tell
   Wicket to throw them away?


Pardon me if I missed this information in the documentation somewhere.

Thanks,

Garret

Reply via email to