Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 36366 invoked from network); 10 Aug 2006 19:03:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Aug 2006 19:03:15 -0000 Received: (qmail 64581 invoked by uid 500); 10 Aug 2006 19:03:09 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 64547 invoked by uid 500); 10 Aug 2006 19:03:09 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 64536 invoked by uid 99); 10 Aug 2006 19:03:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Aug 2006 12:03:09 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Aug 2006 12:03:06 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4FF8571421B for ; Thu, 10 Aug 2006 19:00:14 +0000 (GMT) Message-ID: <12138008.1155236414304.JavaMail.jira@brutus> Date: Thu, 10 Aug 2006 12:00:14 -0700 (PDT) From: "Paul McMahan (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component In-Reply-To: <23760774.1154272573829.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/GERONIMO-2248?page=comments#action_12427316 ] Paul McMahan commented on GERONIMO-2248: ---------------------------------------- This is a good idea, I have made the exact same mistake that you described above :-) Suggestion -- instead of listing all the child components how about instead providing very explicit feedback in the form of a prompt when the user attempts to shut down a component. e.g. user clicks the "stop" link for geronimo/system-database/1.1.1/car. console responds "stopping this component will also cause the following components to stop : [list] Proceed? yes/no". this could be done with a javascript prompt or (if it looks better) in a new portlet screen. This would accomplish the same goal while avoiding the UI issues listed above. I'm also doubtful that just seeing a component's children listed will provide sufficient indication that those components will be stopped when the parent is stopped, especially to the novice or unattentive user. > Applications portlets: List Parent and Child components against each component > ------------------------------------------------------------------------------ > > Key: GERONIMO-2248 > URL: http://issues.apache.org/jira/browse/GERONIMO-2248 > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira