----- Original Message -----
From: "Jonathan Mast" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Friday, August 29, 2008 11:00 PM
Subject: apparent problem with work/ directory
I refactored the POJO side of a webapp I have. I basically moved some
objects referenced by the JSPs into a new package. I updated the jsps
accordingly, by importing the new package with the PAGE directive at the
top. I deleted the old version of the webapp, rebuilt it, and restarted
tomcat.
It then started spewing errors, generated from the jsp's, about not being
able to find the old classes. I am convinced that the errors lies in the
work/ directly, specifically the derived java sources of the jsp were not
updated when I restarted Tomcat.
I know the problem is not in the webapp itself because i tested it out on
my
Windoze box before deploying to Linux where the problem occured. My
question is: how do I force Tomcat to delete the "work" directory upon
restarting or when I'm building from Ant?
Thanks,
Tomcat 5.5.17
Java 1.4.2
Jonathan it doesnt sound right... I dont believe TC is rememberting old
classes....
TC is running and you drop a webapp into it... it will do its thing and
redeploy...
If its looking for old classes... possibly in the dev enviroment the test
missed it because JSP's a "late compiled"
Or in the refactor... I know nebeans does it... if you drag the classes to
another "old stuff" folder... it actually points the app at it.
So they still used but no packed...
Or worse... your delete folder is in the classpath or something weird like
that...
It just doesnt happen on our systems... why are you stopping TC to
redeploy... soes the old app not release... thats a bug get rid of it.
Also... in your test enviroment, when you are sure the webapp is working...
Have a look at /conf/catalina/loahost/<context file>
Is that docbase still pointing at the dev environment... ie you think its
working with your test war, but its actually running the project in the IDE
still... so the test is bogus and then shows itself else where... delete the
context file... start yout test TC and drop the war in... I think you may
see the errors...
If NB... comile every JSP in your test env... ie the big build doesnt
compile them so whether they actually working is not proven by a good
compile...
... something else is catching you (I think).
Have fun...
---------------------------------------------------------------------------
HARBOR : http://www.kewlstuff.co.za/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm
---------------------------------------------------------------------------
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
