geronimo-dev mailing list archives

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

I agree with Matt that we should at least print the stack trace for the should not occur scenario.
I also agree with Aaron on the visual aspects of the view and would like to see a link to
show this on a second screen (and thereby keeping the commands on the right ... there are
a few exceptions to those but we need to fix those).   That would also provide more space
if we want to show multiple relationships (as Aaron pointed out with the WAR-in-EAR, etc..)

If those two things were done, I think it would be good enough to go ahead and integrate (with
appropriate rtc votes of course).  We could continue to work out more details like transitive
dependencies in subsequent changes or possibly even replace the linked to view with a network
view of dependencies highlighting the item in question.

> 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