[ 
https://issues.apache.org/jira/browse/JCR-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jukka Zitting resolved JCR-3128.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.2
                   2.2.10
         Assignee: Jukka Zitting

I committed such a escapeIllegalJcr10Chars() method in revision 1188590 and 
merged it to the 2.2 branch in revision 1188595.

Introducing new method signature in a patch release like 2.2.10 is a bit 
troublesome (ideally there'd be no API changes), but since this is a workaround 
for a backwards compatibility issue I consider the benefits to outweight the 
potential drawbacks.
                
> Problem with formerly escaped JCR node names when upgrading to Jackrabbit 
> 2.2.9
> -------------------------------------------------------------------------------
>
>                 Key: JCR-3128
>                 URL: https://issues.apache.org/jira/browse/JCR-3128
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.2.9
>            Reporter: Sascha Theves
>            Assignee: Jukka Zitting
>             Fix For: 2.2.10, 2.3.2
>
>
> The following unit test fails:
> {code}
> 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));
>    }
> }
> {code}
> 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. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to