[
https://issues.apache.org/jira/browse/GERONIMO-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel updated GERONIMO-4076:
-----------------------------
Description:
1.) The console/web GUI does not explicitly warn the user when he is about to
delete a module which other modules depend upon. [Improvement?]
(Note: the server does then remove the module properly, and all dependent
modules are stopped.)
2.) When the screen is reloaded, the depending modules are displayed as
stopped, but not as "missing dependencies". [Improvement?]
3.) When the user now attempts to restart this module, this leads to an
unhandled exception. The GUI doesn't show up at all. Instead, an error code 500
is displayed (=>
org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction).
[BUG]
was:
1.) The console/web GUI does not explicitly warn the user when he is about to
delete a module which other modules depend upon. [Improvement?]
(Note: the server does then remove the module properly, and all dependent
modules are stopped.)
2.) When the screen is reloaded, the depending modules are displayed as
stopped, but not as missing dependencies. [Improvement?]
3.) When the user now attempts to restart a depending module, this leads to an
unhandled exception. The GUI doesn't show up. Instead, an error code 500 is
displayed (=>
org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction).
[BUG]
> Console runs in unhandled exception when user starts module with unresolved
> dependencies
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMO-4076
> URL: https://issues.apache.org/jira/browse/GERONIMO-4076
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.1.1
> Reporter: Daniel
> Priority: Minor
>
> 1.) The console/web GUI does not explicitly warn the user when he is about to
> delete a module which other modules depend upon. [Improvement?]
> (Note: the server does then remove the module properly, and all dependent
> modules are stopped.)
> 2.) When the screen is reloaded, the depending modules are displayed as
> stopped, but not as "missing dependencies". [Improvement?]
> 3.) When the user now attempts to restart this module, this leads to an
> unhandled exception. The GUI doesn't show up at all. Instead, an error code
> 500 is displayed (=>
> org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction).
> [BUG]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
