Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Tue, 25 Oct 2011 09:04: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: 
 <1825996025.12384.1319533472724.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=
50#comment-13134850 ]=20

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

Hi,

The upgrade was successfully on a stronger server but on every start of the=
 server i get this exception

java.lang.NullPointerException
=09at com.atlassian.greenhopper.upgrade.GhUpgradeTask004.removeProjectIdInL=
ayoutsProperties(GhUpgradeTask004.java:92)
=09at com.atlassian.greenhopper.upgrade.GhUpgradeTask004.doUpgrade(GhUpgrad=
eTask004.java:57)

and on every click this one ..
2011-10-25 10:55:35,295 http-8081-3 ERROR udvt0047@tirol.gv.at 655x650x1 1c=
r9evu 10.12.135.4 /browse/AEICP [greenhopper.jira.license.GreenHopperLicens=
eManagerImpl] com.atlassian.extras.decoder.api.LicenseDecoderNotFoundExcept=
ion: Could not find any valid decoders in [com.atlassian.extras.decoder.v2.=
Version2LicenseDecoder@7b86b0e9, com.atlassian.extras.decoder.v1.Version1Li=
censeDecoder@47c8d05a] for license string <P0g8o6w+aM5iUdprKwTX9nVysnCfoMZT=
TSsv9w8nHb77bXHye8t+VSohqQ7rS9tkZDntOQX0yHjWvocXSsMvrN8AhzXci3mhxSPdOp4tBrC=
rQG2dP8dgvM/bXWCNx3fAf4+CRoiLmzzRS3wlH//uFclKjc/fin4V4sZNFeUpyuaHNFvX721hxr=
7A2pRF87JvLvRLcO/RNkQkeb/yCcd55pLBQmzi3+A4sGoGXGrRM4RyTx273HRCV4zD6L1ZDzM+g=
gTR5donqqNEkux5imQl/lcRI1xrQQg+3BrsIHkcwVza682rkZoJmwkSDVs+pXWXr9M+wgRPiP1W=
zKjp5zjYvnH4yhTy94B9mITbXjwUN6aKFCbi+sEIsClIFFG1qf4xaSXuKG+upZau1cjEM9wgKzd=
hB7MRKYtm8uSxKdlxi8wVB3VvsKLlpwLLsnKqhW028DCjS/G1Z7TCIJn3OXfI+6OQiPE7k4RtUu=
BhlpsmFAcopsfYKORp5HyJqvXVEuXyRFkZlrYgoM4J1250hZYaKnHZpglqm6cAWjSgJsVcYeynV=
oueuG/Rv2dcgxpTNdN3tzETm4DQt/AaUDpc1TZVQXkzR3XPHwUtRqTJ32T2Z551ERqSEn9Mpd77=
IMg3E09Es6ZL4HrMhTFkoZP8bX8ysAymAdymnJrzlgGONKl0+bz8XCrLNeByDmAA7sR7XG4ZaFM=
Bs93U6vOlB15vpMqJPkF//vYpDMMTAL3/Lesnkx//rRFPe8cf3pR6Bjo+2SHmhnhH10x+iZFIc7=
QBfV15bVIettWcjBuEZKa+al8XNlZNZ5oqoblWAOHopG5LY+VKADNMXGN7xkGsIdSJw1RFvgWmO=
HD9C1DBUFfX5snwVp6MLC0qYux9lTd2BGljkjET93N6U6HTZ2vx3dxM7DRQ3P27gWRv4FiBrQS+=
qARihJIcOFPmj5z5iZI8XGsU4fchaDtYtPcPEwJBF0ShYwZbILXtIwrmN8zEzrplwGjI5EDM7XS=
GStN/VXtvD2PKNyv1MIsJdM+WB2Y=3D>

We had years ago greenhopper activated but yet no more ?
What can i do to disable greenhopper ?

thanks=20
claus

               =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