users@jaspic-spec.java.net

[Bug 4673] New: AuthConfigFactory javadoc indicates methods throw AuthException but method signatures do not

From: <bugzilla-daemon_at_java.net>
Date: Wed, 13 Feb 2013 02:11:47 +0000

http://java.net/bugzilla/show_bug.cgi?id=4673

             Bug #: 4673
           Summary: AuthConfigFactory javadoc indicates methods throw
                    AuthException but method signatures do not
    Classification: Unclassified
           Product: jaspic-spec
           Version: 1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: source
        AssignedTo: monzillo_at_java.net
        ReportedBy: monzillo_at_java.net
                CC: issues_at_jaspic-spec.java.net


Javadoc of four AuthConfigFactory methods indicate that they throw
AuthException (which is a checked exception) but method signatures do not
declare that they throw AuthException, and thus the exception cannot be thrown.
Moreover, the inability to throw this exception, makes it unclear how errors
are to be signaled by these methods.


public static AuthConfigFactory getFactory();

public abstract java.lang.StringregisterConfigProvider(
    java.lang.String className,
    java.util.Map properties,
    java.lang.String layer,
    java.lang.String appContext,
    java.lang.String description);

public abstract java.lang.String registerConfigProvider(
    AuthConfigProvider provider,
    java.lang.String layer,
    java.lang.String appContext,
    java.lang.String description)

public abstract void refresh()

javadoc if refresh method of AuthConfig interface also indicates that it throws
AuthException although method signature does not declare that it does.

javadoc if refresh method of AuthConfigProvider interface also indicates that
it throws AuthException although method signature does not declare that it
does.

-- 
Configure bugmail: http://java.net/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.