History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RHQ-1118
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Ian Springer
Reporter: Ian Springer
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project

Add a new discoveryScanId field to ResourceDiscoveryContext to allow plugins to do something once per scan

Created: 13/Nov/08 12:30 PM   Updated: 13/Nov/08 12:30 PM
Component/s: Plugin Container
Fix Version/s: 1.2

Time Tracking:
Original Estimate: 1 hour
Original Estimate - 1 hour
Remaining Estimate: 1 hour
Remaining Estimate - 1 hour
Time Spent: Not Specified
Remaining Estimate - 1 hour

VCS Revision: 1,992


 Description  « Hide
The use case for this is the AS5 plugin. It uses the profile service to retrieve a ManagementView, which is a snapshot of the management info for a particular profile at a particular point in time. Since it is a point in time snapshot, the ManagementView needs to be refreshed periodically; this is done by calling loadProfile() on it.

For runtime discoveries, it is vital to refresh the view prior to the discovery, so that any managed components that were deployed since the last time the ManagementView was refreshed will get discovered. We currently refresh the view at the top of JndiResourceDiscoveryComponent.discoverResources() and DeploymentResourceDiscoveryComponent.discoverResources(), but we really only need to refresh the view at the very beginning of a runtime scan, not for each service type that is scanned for. And doing it once per scan is better, particularly for the Embedded Console, because refreshing the view is presumably a fairly expensive operation.

The problem is the ResourceDiscoveryComponent.discoverResources() currently has no API provided that allows it to ascertain the scan that called it. I propose adding a new discoveryScanId integer field to ResourceDiscoveryContext. This would be set to a unique value by the PluginContainer for each scan it executes.


 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.