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

Problem with formerly escaped JCR node names when upgrading to Jackrabbit 2.2.9

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.9
    • Fix Version/s: 2.2.10, 2.3.2
    • Component/s: jackrabbit-core
    • Labels:
      None

      Description

      The following unit test fails:

      import static org.junit.Assert.*;
      
      import org.apache.jackrabbit.util.Text;
      import org.junit.Test;
      
      public class TestEscaping
      {
         @Test
         public void testEscaping() throws Exception
         {
            // expect this as an escaped string (e.g. formerly escaped with jackrabbit 1.6)
            String escaped = "nam%27e";
            String unescaped = Text.unescapeIllegalJcrChars(escaped);
            assertEquals(escaped, Text.escapeIllegalJcrChars(unescaped));
         }
      }
      

      This is a major problem when upgrading from 1.6.x to 2.2.9. The node names that were escaped in jackrabbit 1.6 are not longer escaped and that breaks the backward compatibility. I think the problem comes in with JCR-2198.

        Attachments

          Activity

            People

            • Assignee:
              jukkaz Jukka Zitting
              Reporter:
              sascha0137 Sascha Theves
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: