connector-spec
  1. connector-spec
  2. CONNECTOR_SPEC-10

Incorrect non-null constraint for serviceSubject in SecurityContext.setupSecurityContext's javadoc

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Labels:
      None

      Description

      The Connector 1.6 (and the current 1.7) javadoc for SecurityContext ( http://docs.oracle.com/javaee/6/api/index.html?javax/resource/spi/work/SecurityContext.html ) has the following erroneous non-null constraint for serviceSubject.

      In the description of setupSecurityContext [1], we have the following erroneous line:
      "The serviceSubject argument must be non-null and it must not be read-only."

      In the spec, and in the same method's 'serviceSubject' parameter javadoc, we talk about serviceSubject being nullable. The correct statement must be
      "The serviceSubject argument may be null, and when not null it must not be read-only."

      [1] http://docs.oracle.com/javaee/6/api/javax/resource/spi/work/SecurityContext.html#setupSecurityContext(javax.security.auth.callback.CallbackHandler, javax.security.auth.Subject, javax.security.auth.Subject)

        Activity

        Sivakumar Thyagarajan created issue -
        Sivakumar Thyagarajan made changes -
        Field Original Value New Value
        Description The Connector 1.6 (and the current 1.7) javadoc for SecurityContext ( http://docs.oracle.com/javaee/6/api/index.html?javax/resource/spi/work/SecurityContext.html ) has the following erroneous non-null constraint for serviceSubject.

        In the description of setupSecurityContext [1], we have the following erroneous line:
        "The serviceSubject argument must be non-null and it must not be read-only."

        In the spec, and in the same method's 'serviceSubject' parameter javadoc, we talk about it being nullable. The correct statement must be
        "The serviceSubject argument may be null, and when not null it must not be read-only."

        [1] http://docs.oracle.com/javaee/6/api/javax/resource/spi/work/SecurityContext.html#setupSecurityContext(javax.security.auth.callback.CallbackHandler, javax.security.auth.Subject, javax.security.auth.Subject)


        The Connector 1.6 (and the current 1.7) javadoc for SecurityContext ( http://docs.oracle.com/javaee/6/api/index.html?javax/resource/spi/work/SecurityContext.html ) has the following erroneous non-null constraint for serviceSubject.

        In the description of setupSecurityContext [1], we have the following erroneous line:
        "The serviceSubject argument must be non-null and it must not be read-only."

        In the spec, and in the same method's 'serviceSubject' parameter javadoc, we talk about serviceSubject being nullable. The correct statement must be
        "The serviceSubject argument may be null, and when not null it must not be read-only."

        [1] http://docs.oracle.com/javaee/6/api/javax/resource/spi/work/SecurityContext.html#setupSecurityContext(javax.security.auth.callback.CallbackHandler, javax.security.auth.Subject, javax.security.auth.Subject)


        Sivakumar Thyagarajan made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Sivakumar Thyagarajan
            Reporter:
            Sivakumar Thyagarajan
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: