Bug 535212 (RHQ-1932) - Provide friendlier error messages when a resource can not be found
Summary: Provide friendlier error messages when a resource can not be found
Keywords:
Status: CLOSED NOTABUG
Alias: RHQ-1932
Product: RHQ Project
Classification: Other
Component: Core UI
Version: unspecified
Hardware: All
OS: All
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-06 08:56 UTC by Heiko W. Rupp
Modified: 2009-04-28 07:02 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Heiko W. Rupp 2009-04-06 08:56:00 UTC
I did have the following in my browsers page history.

http://pickeldi:7080/rhq/resource/inventory/view.xhtml?id=506050

Calling this, resulted in a red box saying 
"/rhq/resource/layout/main.xhtml @81,60 test="#{ResourceUIBean.facets.callTime}" Cant instantiate class: org.rhq.enterprise.gui.inventory.resource.ResourceUIBean."

Looking at the stack trace shows way down that the resource just does not exist. 

In cases like those (user may have saved a resource in the browsers bookmark and the resource has meanwhile been deleted) or just any other, we should print a much friendlier message with a link back to resource hub or dashboard -- a little bit like we had it in the past.


Comment 1 Heiko W. Rupp 2009-04-07 12:13:41 UTC
This can also happen in situations like RHQ-1943

Comment 2 Joseph Marques 2009-04-28 07:02:39 UTC
ah, i was looking for this jira a while back but couldn't find it.  anyway, this is now done as the new error.xhtml page which you're redirect to upon errors loading other facelets, one of those instances being ResourceNotFoundException.

Comment 3 Red Hat Bugzilla 2009-11-10 20:49:45 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1932
This bug relates to RHQ-1943



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