[ http://issues.apache.org/jira/browse/GERONIMO-1631?page=comments#action_12453578 ] Rakesh Midha commented on GERONIMO-1631: ----------------------------------------
Question before I move further when you said "config A that imports config B" you mean "Config A is dependent on config B" right? I could not download the TestApplication you gave, so used mine TestEJB and TestWeb, my TestWeb define dependency on TestEJB application. I followed your steps and got these results: Step (3)Uninstall TestEJB resulted in unInstallation of TestEJB application and it also unloaded TestWar application. Hence when server restarted because for TestWar application load=false, the server started without TestWar Which means unistalling of application unloads all the application dependent on tis application, which means no "NoSuchConfig" exception. This sounded wrong because if i tried to install TestWeb without installing TestEJB , it was never installed. Which means TestWeb should also uninstall when TestEJB is uninstalled (and not just unloaded) I am attaching a patch which uninstalls all the child applications (just like stop command, stops all the child applications also) I hope this functaionallity is right? If it is, than please review and commit this patch. Otherwise ignore it. > NoSuchConfigException when restarting app after undeploying > ----------------------------------------------------------- > > Key: GERONIMO-1631 > URL: http://issues.apache.org/jira/browse/GERONIMO-1631 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment > Affects Versions: 1.0 > Reporter: Sachin Patel > Assigned To: Rakesh Midha > Fix For: Verification Required > > > If I have config A that imports config B. If undeploy is invoked on B... > then... > Module B/B unloaded. > Module B/B uninstalled. > Undeployed B/B > So module B is not being stopped, thus resulting in a NoSuchConfigException > on B when the server is restarted. > If A is undeployed before B, then all is ok. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
