Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-1168

Invalid JCR paths not caught

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 0.20
    • core, jcr
    • None

    Description

      NamePathMapper.getOakPath should return null when called with an invalid JCR path like foo:bar]baz, but it doesn't.

      Attachments

        Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. OAK-1174 Inconsistent handling of invalid names/paths

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. OAK-1179 Use dedicated Path class for handling paths in Oak

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            angela Angela Schreiber
            mduerig Michael Dürig
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment