This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 30212 - application doesn't get updated on re-deployment
Summary: application doesn't get updated on re-deployment
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@serverplugins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-18 06:10 UTC by arimus
Modified: 2006-06-05 00:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description arimus 2003-01-18 06:10:34 UTC 
Not sure if this is the proper category for this
issue...

Some of the changes to application code aren't
deployed.  It appears that either tomcat doesn't
update its cache properly or the changes just
aren't getting deployed as they should.  This
happens in both 3.4 and 3.4.1rc2.  Used to work
fine in 3.4, then started giving me problems as my
project grew, so I installed 3.4.1rc2 to see if
problems had been solved.  No luck =P

I can fix the problem only by:

1. closing netbeans
2. removing all files from ~/.netbeans/3.4/cache/
3. removing all files from
~/.netbeans/3.4/tomcat404_base/work/Tomcat-Internal/localhost/_2Fhome_2Farimus_2Fprojects_2Fladybug/
4. starting netbeans
5. redeploy the application
6. viola

* not sure if the ~/.netbeans/3.4/cache/ is
related, but I removed those files each time too...
Comment 1 _ rkubacki 2003-01-20 08:01:03 UTC 
Why do you think it is not redeployed? Does your browser caches pages?
Try to turn off this feature to be sure. Also check tomcat logs to see
what was really deployed (and when).
Comment 2 _ rkubacki 2003-02-17 15:38:36 UTC 
The caching works for me. I don't understand your point. Any
reproducible use case?