[jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
[ http://issues.apache.org/jira/browse/GERONIMO-2248?page=comments#action_12435496 ] Jeff Genender commented on GERONIMO-2248: - +1 from mecool stuff. 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.1, 1.1.1, 1.2 Reporter: Vamsavardhana Reddy Fix For: 1.2 Attachments: GERONIMO-2248-revised.patch, 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
[jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
[ http://issues.apache.org/jira/browse/GERONIMO-2248?page=comments#action_12433714 ] David Jencks commented on GERONIMO-2248: This is really great! +1000! I'd really like it if we could also push a button and see _all_ the modules deployed on that page rather than just the non-j2ee modules. I would find this very helpful frequently. It would be great to indicate the dependency type -- classes only, services only, or all -- in addition. I agree with gianni that loading (not starting) the configuration is necessary and causes no problems. When you deploy a module all its parents get loaded recursively, but not started. 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.1, 1.1.1, 1.2 Reporter: Vamsavardhana Reddy Fix For: 1.2 Attachments: GERONIMO-2248-revised.patch, 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
[jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
[ http://issues.apache.org/jira/browse/GERONIMO-2248?page=comments#action_12433565 ] Gianny Damour commented on GERONIMO-2248: - Thanks for this patch. I think that this is a great add-on. I also think that if you can add a new screen to display parent and child configurations, this would be better. Also, I am not sure why Aaron is raising a problem with respect to loading a configuration to get the parents and children configurations of a configuration. My understanding is that this will only load and start (and not start recursive) the configuration. Also, you can easily get much more information from the Configuration class, e.g. ClassParents, ServiceParents. So just after having loaded a configuration, you can do ConfigurationManager.getConfiguration. 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.1, 1.1.1, 1.2 Reporter: Vamsavardhana Reddy Fix For: 1.2 Attachments: GERONIMO-2248-revised.patch, 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
[jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
[ http://issues.apache.org/jira/browse/GERONIMO-2248?page=comments#action_12433587 ] Vamsavardhana Reddy commented on GERONIMO-2248: --- Loading configuration loads the configuration gbean data. It does not start the configuration at all. 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.1, 1.1.1, 1.2 Reporter: Vamsavardhana Reddy Fix For: 1.2 Attachments: GERONIMO-2248-revised.patch, 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
[jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
[ 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
[jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
[ http://issues.apache.org/jira/browse/GERONIMO-2248?page=comments#action_12426984 ] Matt Hogstrom commented on GERONIMO-2248: - I think this is fine for inclusion in 1.1.2. Although it is an improvement it improves server usability. My +1 for 1.1.2 Vamsi, can you rework the patch to spit out a stack trace when the Should Not Occur issue arises :) 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
[jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
[ http://issues.apache.org/jira/browse/GERONIMO-2248?page=comments#action_12427038 ] 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: 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
[jira] Commented: (GERONIMO-2248) Applications portlets: List Parent and Child components against each component
[ http://issues.apache.org/jira/browse/GERONIMO-2248?page=comments#action_12427040 ] 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: 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
