Bug 1009089 - Metrics list from previous resource cached when navigating Monitor Sub Tabs
Summary: Metrics list from previous resource cached when navigating Monitor Sub Tabs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.10
Assignee: Mike Thompson
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 1009124
TreeView+ depends on / blocked
 
Reported: 2013-09-17 16:28 UTC by Mike Thompson
Modified: 2014-10-13 11:52 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
: 1009124 (view as bug list)
Environment:
Last Closed: 2014-04-23 12:31:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike Thompson 2013-09-17 16:28:46 UTC
Description of problem:
This one is a little but tricky to reproduce. But is one of those bugs you would run into with ad-hoc use.


How reproducible:
Always if the proper sequence of steps is performed.


Steps to Reproduce:
1. In the resource tree click on EAP RHQ Server
2. Select the monitoring tab and the Schedules sub tab
3. Now change resources, say to CPU 0
4. Now change to the Monitoring tab and change to Metrics sub tab

Actual results:
Metrics are shown from the previous resource and not the current resource.



The new metrics view is caching the changes between sub tab navigation (Schedules to Metrics) as it now is stateful to remember the opened graphs in the expandable table.

[jsanda actually found this bug]

Comment 1 Mike Thompson 2013-09-17 23:19:53 UTC
committed to master: 1e23623

Move the stateful momento containing open chart rows out to the ResourceDetailView instead of at the MetricsTableView which can then be created and destroyed like the other stateless views and state momento passed into the View to restore previous (opened rows) state.

Comment 2 Heiko W. Rupp 2014-04-23 12:31:38 UTC
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.


Note You need to log in before you can comment on or make changes to this bug.