logging out and logging back in should fix this. the tree component is placed in the session for performance reasons (it's expensive to gather the data needed for the tree). perhaps we need a way of detecting that the inventory has changed and so to force the tree to recreate itself. generally (read: hopefully) this won't be need all too often, and i would consider this a corner case, but it would be nice to eliminate session oddities like this. since we already know when the inventory changes (specific methods on ResourceManagerBean are called), we can thus determine when the hierarchy under some platform has changed. if we compare that time to the time when the tree nav was generated, that should be a fairly efficient mechanism that will allow us to cache the tree data/contents, but still know when that cache is stale and needs to be regenerated.
I don't consider new resources being added to the inventory and the user wanting to see them in the nav as a corner case. People got annoyed with Embedded when the nav and tab views got out of sync, as is happening here. There were various strategies we employed in embedded to resolve this, none completely satisfactory right now. Speak to Ian or myself if you want more details
charles, add whatever background info you can to this case
rev2966 - ghinkle moved tree to request scope, which should eliminate this issue.
Test this too - log in, view a platform inv tab, then view a 2nd platform. The problem is the left nav still shows the 1st platform. <joseph> jweiss: i'm thinking that the first time you log in it caches the tree in the session. then you go to another platform, but the first platform is still in session. you'll see this if you test against multi-platform inventories. this should be fixed in the new cut to QA since the tree is stored in reqeust scope <jweiss> joseph: ok thanks joseph: ghinkle: yeah that's it - the first tree i look at after logging in is the one it stays with until i log out - i'll comment on that same jira
The left nav now updates properly when 1) you add a resource in another session 2) when you navigate from one platform to another rev3509
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1362 This bug is duplicated by RHQ-1509