|
Actually, I was only taking the information given in the constructor
and copying it to the introduction of the class. public LDAPReferralException(String
message,
LDAPException rootException) Constructs a default exception with a specified string as
additional
information and an exception that indicates a failure to follow a referral. This exception applies only to synchronous operations and is thrown only on receipt of a referral when the referral was not followed. As I was looking at this, I wondered if LDAPException is
too restrictive. For example what is reported for a malformed URL? We cannot report MalformedURLException as it is of type Exception. Should the rootException be simply of type Exception? Should the ReferralException class use matchedDN to indicate
which referral caused the problem, or is that overloading that field too much. -Steve
Rob Weltman wrote: > Steve Sonntag wrote:
> > > LDAPReferralException 4.27 public class LDAPReferralException > > extends LDAPException > > > > This exception, derived from LDAPException, is thrown when a server > > returns a referral and automatic referral following has not been > > enabled.Add to the above or automatic referral following could not follow any referrals. -Steve > > That sounds hard to handle for a client. Are you thinking of the case where the referral points to a server which is inaccessible or which doesn't accept the credentials of the requestor? How would the client know which of those problems was being flagged if there is only a referral exception? And consequently, how would the client know what to do about it? > > Rob |