Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Tue, 25 Oct 2011 07:24:32 +0000 (UTC)
From: =?utf-8?Q?Claus_K=C3=B6ll_=28Commented=29_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <1197189444.12207.1319527472101.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <431793465.12163.1319526512387.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (JCR-3128) Problem with formerly escaped JCR
 node names when upgrading to Jackrabbit 2.2.9
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-3128?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D131348=
06#comment-13134806 ]=20

Claus K=C3=B6ll commented on JCR-3128:
---------------------------------

Hi,
Single and double quote are valid since JCR 2.0
               =20
> 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
>
> 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 jac=
krabbit 1.6)
>       String escaped =3D "nam%27e";
>       String unescaped =3D 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 name=
s that were escaped in jackrabbit 1.6 are not longer escaped and that break=
s the backward compatibility. I think the problem comes in with JCR-2198.=
=20

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