These two exception were designed to use as follows: - OAuthSystemException - critical problem with the Amber library, user is not able to recover from this error - OAuthProblemException - error that regards to OAuth protocol error, which user can handle and recover from it, e.g. obtain new token if OAuthProblemException says: token_expired
I agree that OAuthSystemException should be probably runtime. Cheers, Lukasz On Fri, Dec 30, 2011 at 6:47 PM, Raymond Feng <[email protected]> wrote: > I agree. At least we should make OAuthSystemException as a runtime > exception. > > Raymond Feng > Sent from my iPhone > > On Dec 30, 2011, at 7:29 AM, Antonio Sanso <[email protected]> wrote: > > > Hi *, > > > > I have noticed that a lot of Amber method throws both > OAuthSystemException,OAuthProblemException. > > > > While I understand the use of OAuthProblemException that matches really > well with OAuthResponse I feel a little ackward on catch/use > OAuthSystemException. > > > > I was wondering is it really needed? If yes, which one is the idea > behind? > > > > Thanks in advance > > > > Antonio >
