if you have a dir structure like / /somedir and you delete the /somedir from the jspcache then next time you try and get a page in that directory you get a FileNotFoundException. see attached war after going to index.jsp delete the dir directory in the jspcache and reload index.jsp you will see errors in the two iframes instead of the jsp page.
Created attachment 3694 [details] this is a war file showing the error
I may be dumb, but I don't think this is supposed to be supported. I think Jasper could be made more robust in that particular scenario, but the user is not supposed to go on a rampage in the work directory without at least stop/start of the webapp.
has anyone looked at this... if nothing else this makes dev a real pain.
Why would you want to delete the work directories when developing?
to get rid of all the jsp cache (i guess I could touch each file too..) also our application allows for the deletion of the cache for our customer for reasons to long to explain here. none the less is it still not a bug??
I'm not sure if thinking of it as a "cache" helps much since I agree if it was a "cache" then you would expect to be able to easily clear it. The work directory is in reality more of a practical internal detail of Tomcat, rather than being part of any public functionality. The whole thing could in theory, even though being crap idea, have been built in memory and you wouldn't be able to touch it. I guess it is unfortunate that you gone as far as exposing these internals to your clients, I suspect if you need to have this sorted, you need to look at it yourself.
To be honest I agree with most of your points.. the only time I realy want to delete it is when getting files from vss because sometimes the timestamps are older than what I had localy (i know i can check them out with a current timestamp)