Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.1
    • 2.0.0-RC1
    • None

    Description

      There were a couple of places where the tenantid wasn't being passed down to the DAO.

      Mostly centered around this method below. Notice how the tenantid isn't being passed into the api call.

      And there is another problem in this new method creates a cycle with the reviewmgrimpl as it is dependent on vutil and with this new method vice versa.

      While I'm not crazy about the solution, I have broken the code from this vutil and moved into the validate methods of both the permp and userp classes.

      public final class VUtil implements ConstraintValidator
      ...
      public static void permAttrSetName( String value ) throws ValidationException
      {
      try

      { ReviewMgr reviewMgr = ReviewMgrFactory.createInstance(); PermissionAttributeSet paSet = reviewMgr.readPermAttributeSet(new PermissionAttributeSet(value)); }

      catch(Exception e)

      { String error = "permissionAttributeSet - not found with name [" + value + "]"; throw new ValidationException( GlobalErrIds.PERM_ATTRIBUTE_SET_NOT_FOUND, error ); }

      RegExUtil.getInstance().safeText( value );
      }

      Attachments

        Activity

          People

            smckinney Shawn McKinney
            smckinney Shawn McKinney
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: