Bug 614599 - add ability to filter by plugin name to AlertCriteria and MeasurementDefinitionCriteria
add ability to filter by plugin name to AlertCriteria and MeasurementDefiniti...
Status: CLOSED NEXTRELEASE
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
1.3.1
All All
low Severity low (vote)
: GA
: RHQ 4.12
Assigned To: Jay Shaughnessy
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-14 16:34 EDT by Ian Springer
Modified: 2014-06-02 15:25 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-02 15:25:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Ian Springer 2010-07-14 16:34:14 EDT
Thee criteria classes both provide ability to filter by resource type name. They need to complement that with the ability to filter by plugin name, otherwise it will not be possible to lookup a resource type that is defined in other plugins with the same name (e.g. the "JBossAS Server" restype from the JBossAS plugin). 

Note, the workaround is to first lookup the desired resource type using ResourceTypeManager.getResourceTypeByNameAndPlugin() and then filter by that resource type's id (rather than name) in the AlertCriteria or MeasurementDefinitionCriteria.
Comment 5 Jay Shaughnessy 2014-06-02 15:25:52 EDT
Still totally true, Adding this for the next release (4.12).

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