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 40098 - Undeployed modules don't remain undeployed
Summary: Undeployed modules don't remain undeployed
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-13 17:59 UTC by Ana.von Klopp
Modified: 2004-02-20 10:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ana.von Klopp 2004-02-13 17:59:41 UTC
To reproduce: mount a few web modules in the IDE 
and execute them all. 

Unmount all the directories except one, and then 
delete them from disk. Exit the IDE. Restart the 
IDE and try to execute the web module. You see a 
lot of execptions in the output log because of 
the deleted modules. 

Go to the runtime tab and undeploy all the 
modules that are marked as stopped. Excute the 
remaining module again (everything is fine). 

Exit the IDE and start it again. Try to execute 
the module. All the modules that were undeployed 
are back!
Comment 1 Marek Fukala 2004-02-16 08:59:38 UTC
When the undeply action is called, then the undeployed webmodule
disappear from the list of deployed webmodules in both IDE webmodules
node and tomcat manager web application. 

The problem is with the
${CATALINA_BASE}/conf/Catalina/host/<wmname>.xml file which is not
deleted when the undeployment is done from the IDE.

If I do the undeployment via tomcat's manager app, the file
<wmname>.xml is deleted and there are no errors during next tomcat
startup.
Comment 2 Martin Grebac 2004-02-19 15:40:21 UTC
I'm not able to reproduce. Do I need to have some special webmodules?
Comment 3 Pavel Buzek 2004-02-19 23:07:36 UTC
I asked Martin for help but now I think I have the fix so I am taking
the issue back.

I can reproduce what Marek Fukala describes. The problem was that
tomcat5 plugin was using "remove" instead of "undeploy". "remove" is
not even mentioned at manager page of t5 docs, it is likely 4.1-ism
and is not fully funtional in t5.
Comment 4 Pavel Buzek 2004-02-19 23:09:21 UTC
forgot to assign to myself, should you ever dare to reopen this issue
please assign it to pbuzek@netbeans.org
tx
Comment 5 Marek Fukala 2004-02-20 10:53:57 UTC
verified