Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-1433

web.xml should contain explicit jndi-enabled param instead of checking for a provided java.naming.provider.url

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

Details

    • Improvement
    • Status: Patch Available
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • jackrabbit-webapp
    • None
    • This should work in every Servlet Container.

    Description

      If there is no need or no possibilty to set a java.naming.provider.url it is impossible to use the RepositoryAccessServlet cause it won't lookup in the JNDI unless this is specified.

      The enabling of this feature should not depend on an optional Configparameter.

      Attachments

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

          People

            Unassigned Unassigned
            sqsuiddle squiddle
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment