An exception like an IOException is specific to the implementation of the resolver (not all of them would need to do this). In addition, any handling of that exception would only be able to occur within that resolver (as none of the items that call it assume that resolvers require IO operations). Anything that couldn't be handled by the resolver is something that most likely could not be handled at all and thus would be a RuntimeException (which are generally not declared in the signature as you do not want to force people to catch something they probably won't be able to handle.
-Scott On Jan 28, 2008 6:16 PM, ssozonoff <[EMAIL PROTECTED]> wrote: > > Hi All, > > I was just curious why the method resolvePrincipal > (CredentialsToPrincipleResolver interface) does not throw an exception. > > Surely the task of looking up an principle other than the username could > involve a network IO operation (for example). In this case it is very > possible for it to fail for a number of reasons. > > How are people currently handling this? > > Thanks, > Serge > > > -- > View this message in context: > http://www.nabble.com/method-resolvePrincipal-of-Interface-CredentialsToPrincipleResolver-not-throwing-an-Exception--tp15148341p15148341.html > Sent from the CAS Dev mailing list archive at Nabble.com. > > _______________________________________________ > cas-dev mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas-dev > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
