geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
Date Wed, 09 Aug 2006 21:42:14 GMT
    [ ] 
Aaron Mulder commented on GERONIMO-2248:

I'm not real happy with this:
 * It puts data to the right of commands, where usually commands are on the far right
 * It shows Module IDs without any more useful data for the children
 * It increases the height of the display
 * we should think about whether to show child modules such as WAR-within-EAR or child modules
such as WAR-dependent-on-DB-pool or both
 * if we're trying to show everything that will be stopped if the module is stopped, the list
should show transitive children, and the entry for e.g. rmi-naming will be unimaginably huge
 * I'm not sure it's a good idea to load the Confiiguration if it's not already loaded

I think it would be better to hyperlink the module ID in the current display and introduce
a new screen with more module details and move this kind of stuff to that screen.

> Applications portlets: List Parent and Child components against each component
> ------------------------------------------------------------------------------
>                 Key: GERONIMO-2248
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 1.2, 1.1, 1.1.1
>            Reporter: Vamsavardhana Reddy
>             Fix For: 1.2
>         Attachments: GERONIMO-2248.patch
> Applications portlets currently provide component status and links to start/stop/restart/uninstall.
 They do not provide a listing of parent components and child components.
> If child components are listed, a user will immediatley know what all configurations
will be stopped if a particular component is stopped.
> How is it useful?
> I have stopped " geronimo/system-database/1.1.1-SNAPSHOT/car" to test something.  Only
after an error HTTP 404 was displayed next,  I realized that the admin console had a dependency
on "geronimo/system-database/1.1.1-SNAPSHOT/car".  Had there been a Child Components listing
next to "geronimo/system-database/1.1.1-SNAPSHOT/car", it would have avoided the surprise.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message