Yes wicket creates those dirs and files
But it should clean them up when a session is terminated.
But are you seeing this in development? or in production?
In both occasions: how are you terminating jetty?
If you just kill it, so you don't tell jetty that it should shutdown
then dirs can be left behind yes. Because we don't get a session timeout of
those sessions.
johan
On 2/24/07, Wouter de Vaal <[EMAIL PROTECTED]> wrote:
Hi,
I'm running wicket within jetty in an OSGi application and wicket
seems to create cache or temporary files named like
"wicket.protocol.http.WicketFilter-page-0-version-0" and these appear
in directories with names like:
11dd84rdpqf1n
1br6tnohudlcb
etc.
The problem is that these directories aren't deleted and are writting
in the same directory as where the application was started. So I'm
trying to figure out which part is responsible. Running jetty with a
non-wicket app doesn't create these directories, so my first guess it
has something to do with Wicket.
I'm running a 2.0 snapshot.
Any suggestions?
Thanx,
Wouter
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
