Bug 697559

Summary:	all GWT service interface methods must explicitly declares throws runtime exception
Product:	[Other] RHQ Project	Reporter:	John Mazzitelli <mazz>
Component:	Core UI	Assignee:	John Mazzitelli <mazz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Corey Welton <cwelton>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.0.0.Beta1	CC:	hrupp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-24 01:09:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	585306

Description John Mazzitelli 2011-04-18 15:30:44 UTC

In order for GWT to properly propogate exceptions from server to client via our GWT Service design, we must ensure all GWT Service interface methods explicitly declare "throws RuntimeException". If they do not, GWT will not expect exceptions and you'll get the nebulous exception message from GWT :

com.google.gwt.user.client.rpc.StatusCodeException:The call failed on the server; see server log for details

If we declare that the interface throws exceptions, we'll get the actual exception messages at least, which should be more helpful to users to determine what happened and possibly how to fix.

I see this in SystemGWTService - I will fix those. We need to go through all other interfaces and fix. Note this is the INTERFACES that have to have this declaration.

Comment 1 Charles Crouch 2011-04-18 23:42:15 UTC

I think this is a must have in order to get useful feedback post release

Comment 2 John Mazzitelli 2011-04-19 15:07:53 UTC

commit: 36f7955cde61d7c306317e5b7fc8b7c93ee252a7

nothing for QA to do , this is a code level change only.

Comment 3 Corey Welton 2011-05-24 01:09:50 UTC

Bookkeeping - closing bug - fixed in recent release.