Description of problem: ======================= The following exception causes Facelets to show their ugly Exception screen. It should be caught and handled gracefully. -------------------- Caused by: org.rhq.enterprise.server.resource.ResourceNotFoundException: A resource with id 10251 does not exist in inventory. at org.rhq.enterprise.server.resource.ResourceManagerBean.getResourceById(ResourceManagerBean.java:518) -------------------- Btw the same problem is in EmbJopr. Steps to Reproduce: =================== Basically, any request to non-existent ID causes this. E.g. browser's back button or history or bookmarks may contain URLs causing this when the resource is deleted. Expected behavior: ================== Normal JON page should appear saying that user is trying to reach a resource which was removed.
Created attachment 390379 [details] JON invalid resource ID Facelets exception.
Facelets header is: (or similar) Cant instantiate class: org.rhq.enterprise.gui.inventory.resource.ResourceUIBean. /rhq/resource/layout/main.xhtml @81,60 test="#{ResourceUIBean.facets.callTime}
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
closing per gwt efforts