Well, it must not return null on attempting to create a DartmouthPrincial, because it is not failing through to the second C2PResolver.
I haven't worked it all out yet, but I believe it's not failing and returning null because the "new" command never returns a null object if it makes it into the constructor, ie by the time your constructor is called and you could check if the passed in params are valid, the object already exists. You can't force the constructor to return null at that point, and the exception I'm raising must not be handled in the correct spot. Steve On Feb 1, 2007, at 3:33 PM, Scott Battaglia wrote: > Would your DartmouthUserPassCred2PrincipalResolver be able to > return a principal for the types of users that the new > CredentialsToPrincipalResolver would be able to handle? If it > doesn't recognize those users and would return null, then the chain > would continue until it found one that did not return null. _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
