[
https://issues.apache.org/jira/browse/GERONIMO-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-1631:
-----------------------------------
Fix Version/s: (was: 2.0)
2.1
I'm not sure that I understand what the proposed behavior is. Here's what I
think should happen:
situation: app B depends on app A.
both A and B are running
undeploy A should result in:
B stops
A stops
A undeployed
B stopped but still in the g. repo.
Here's why:
If you are working on several apps with dependencies, such as A and B above,
you may need to make minor changes to A. This may well involve undeploying and
redeploying A. There is no need to undeploy B since everything will still work
as long as you haven't changed the interface B uses from A.
Note that undeploying A should definitely leave B stopped. If you shut down
and restart geronimo, B should remain stopped.
> NoSuchConfigException when restarting app after undeploying
> -----------------------------------------------------------
>
> Key: GERONIMO-1631
> URL: https://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
> Assignee: Rakesh Midha
> Fix For: 2.1
>
> Attachments: undeploydependecies.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
