Bug 617380 - Sorting on column headers in history sub-view of group alerts is broken
Summary: Sorting on column headers in history sub-view of group alerts is broken
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RHQ Project
Classification: Other
Component: Alerts
Version: 3.0.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: jon-sprint12-bugs
TreeView+ depends on / blocked
 
Reported: 2010-07-22 21:21 UTC by John Sanda
Modified: 2010-09-28 12:17 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-28 12:17:50 UTC
Embargoed:


Attachments (Terms of Use)

Description John Sanda 2010-07-22 21:21:50 UTC
Description of problem:
Generate some alerts for a group. Then go to,

group --> alerts --> history

Clicking on the 'Date Created' header should toggle sorting back and forth between ascending and descending order. Nothing happens though due to the following hibernate query exception,

ERROR [org.rhq.enterprise.gui.common.paging.PagedListDataModel] PageControlView[ListGroupAlertHistoryUIBean]: Received error[java.lang.IllegalArgumentException: org.hibernate.QueryException: could not resolve property: a of: org.rhq.core.domain.alert.Alert [SELECT alert
FROM org.rhq.core.domain.alert.Alert alert
LEFT JOIN FETCH alert.alertDefinition
WHERE ( alert.alertDefinition.resource.id IN ( :resourceIds ) )
ORDER BY alert.a.ctime ASC
]], resetting to PageControl[page=0, size=15]

This also happens when you click on the 'Priority' and 'Alert Definition' columns. This should be a quick fix on listGroupAlertHistory.xhtml.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Charles Crouch 2010-07-22 21:29:30 UTC
I dont see this as a release blocker at this stage, alert sorting still works at the individial resource level, but this should get fixed in master.

Comment 2 Corey Welton 2010-09-28 12:17:50 UTC
Closing per gwt effort


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