There are four selector impls that do not provide any filter fields: - RoleSubjectSelector - SystemUsersNotificationSenderForm$SubjectSelector - SubjectRoleSelector - SystemRolesNotificationSenderForm$RoleSelector
[master 4d78975] (http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=4d78975) provides a stop-gap workaround for RHQ 4.2. We simply override getMaxAvailableRecords() in the four selectors with no filters and return 500, rather than the default of 100, i.e.: @Override protected int getMaxAvailableRecords() { return 500; } The permanent and more robust fix for JON 3.0 will be to add one or more filters to each of the four selectors.
info on verification .... RoleSubjectSelector and SubjectRoleSelector are on the pages where you add users to roles and roles to users so around the workflow of adding an RHQ user
SystemUsersNotificationSenderForm$SubjectSelector and SystemRolesNotificationSenderForm$RoleSelector would be for when you are setting up email notifications from an alert and you went to send emails to either a particular user or all the users in a particular role
verified RHQ master 10/28/2011: 1) create roles 2) create users 3) alert notification with email notification to system user 4) alert notification with email notification to system role
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
marking VERIFIED BZs to CLOSED/CURRENTRELEASE