Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Daniel Slack" <dslack@langui.com>
To: <users@jackrabbit.apache.org>
Subject: Jackrabbit upgrade from 1.6 to 2.x problem
Date: Fri, 14 Oct 2011 11:20:13 -0500
Message-ID: <005a01cc8a8d$27551150$75ff33f0$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_005B_01CC8A63.3E7F0950"
Thread-Index: AcyKjSb4i5tAJZK5RieGiNCobaYZcw==
Content-Language: en-ca

------=_NextPart_000_005B_01CC8A63.3E7F0950
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 
For one of our projects, I've decided to upgrade Jackrabbit from 1.6.0 to
2.3.0.  I may end up reverting back, just because I am using the RMI
interface, however, that remains to be seen.  Anyways, from reading the
documentation, it appears that the RMI interface for 2.0 will only work for
a "2.0" repository.  So, I was going to use the RepositoryCopier to see if I
can migrate my repository over.

 
However, when I attempt to create a 2.x Repository instance using my
existing repository, it fails when attempting to create the version manager.
When its attempting to check if the Node exists, it throws an exception:

 
org.apache.jackrabbit.core.state.ItemStateException: failed to read bundle:
deadbeef-face-babe-cafe-babecafebabe: java.lang.IllegalArgumentException:
Invalid namespace index: 6086317

 
I'm not really sure why this is the case, as I assumed the repository was
backwards compatible between 1.6 and 2.x.  Is there something I'm missing?

 
Thanks,

 
Dan Slack


------=_NextPart_000_005B_01CC8A63.3E7F0950--