Bug 684864 - cannot view events
Summary: cannot view events
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0.B02
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4
TreeView+ depends on / blocked
 
Reported: 2011-03-14 16:45 UTC by John Mazzitelli
Modified: 2011-05-24 01:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-24 01:12:02 UTC
Embargoed:

Attachments (Terms of Use)

Description John Mazzitelli 2011-03-14 16:45:00 UTC 
Can't view event history. getting gwt error:

Failure in datasource while processing FETCH request.

java.lang.IllegalArgumentException:No enum const class org.rhq.core.domain.event.EventSeverity

problem is the way we are parsing the events enums from the list of selected severities in org.rhq.enterprise.gui.coregui.client.inventory.common.event.EventCompositeDatasource.getFetchCriteria(DSRequest)
Comment 1 John Mazzitelli 2011-03-14 16:45:29 UTC 
without fixing this, I don't think you'll ever be able to view events
Comment 2 John Mazzitelli 2011-03-14 16:58:12 UTC 
master commit 32dcfe0

to test, go to  Event>History subtab for any resource. Make sure you have at least one event severity selected in the filter drop down. Hit refresh button in table. should not see any errors
Comment 3 Sunil Kondkar 2011-04-12 10:04:32 UTC 
Verified on build#1143 (Version: 4.0.0-SNAPSHOT Build Number: 90254fb)

Navigated to Event>History sub tab for a resource. Selected a event severity in the filter drop down. No errors are observed after hitting 'Refresh' button
in table. The UI displays the events filtered by the selected severity.

Marking as verified.
Comment 4 Corey Welton 2011-05-24 01:12:02 UTC 
Bookkeeping - closing bug - fixed in recent release.
Comment 5 Corey Welton 2011-05-24 01:12:02 UTC 
Bookkeeping - closing bug - fixed in recent release.
Note You need to log in before you can comment on or make changes to this bug.