Cool. That can just be mapped to the ResponseError.INTERNAL_ERROR code. Thanks!
- Cassie On Mon, Mar 31, 2008 at 6:52 PM, Brian Eaton <[EMAIL PROTECTED]> wrote: > On Mon, Mar 31, 2008 at 3:22 AM, Cassie <[EMAIL PROTECTED]> wrote: > > Why do all of the social classes need throws GadgetException in their > > signatures? I can't see anywhere this is thrown in the current social > code, > > and furthermore, the design is set up so that the service > implementations > > always handle their own exceptions and return a proper error code. > Allowing > > them to both return an error code and return an exception is just > confusing. > > Ah, I'd missed the error handling in the original design. There just > needs to be some mechanism to return an error from those APIs, it > doesn't have to be GadgetException. If a RemoteContentFetcher were to > throw a GadgetException, how should that exception be mapped to a > ResponseError? >
