Hi Eyji Re CRX / Jackrabbit questions:
On Tue, Dec 16, 2008 at 2:21 PM, Eyji <[email protected]> wrote: > You were right, we hade remnants left of our previously used > TarPersistanceManager, but we switched over to Derby, and our environment > now works well. > To add on to our problem, we are using JackRabbit 1.5 deployed on Tomcat 6 > with CRX 1.4, which could have added some classpath failures? If that is > so, > how do we best deploy JR 1.5 with CRX 1.4? CRX starting with 1.4 is drop-in/source-code compatible with the corresponding Jacrkabbit release (specifically, Jackrabbit branch). Newer Jackrabbit releases are not guaranteed to work out-of-the-box, as there might be incompatible changes in the newer JR code (especially for modules not maintained in Jackrabbit). Because of that, I would not generally recommend to deploy CRX 1.4 with some modules upgraded to JR 1.5. > Do you know if CRX will soon be > upgraded according to the new version of JR? > We're discussing the Jackrabbit version, on which we're going to base our next major CRX update. There's quite some interesting JSR-283 forward-looking(*) enhancements going on in JR trunk a.t.m., which we'd like to embrace in CRX a.s.a.p., and this surely is a certain challenge from the commercial product, standards-compliance, and engineering perspective :) Jackrabbit 1.5 already includes some of these of course. (*) Surely neither CRX nor Jackrabbit claim to be compliant with the upcomings standard, it's not possible (legal) before it's published. Cheers Greg > > Jukka Zitting wrote: > > > > Hi, > > > > On Tue, Dec 16, 2008 at 1:19 PM, Eyji <[email protected]> wrote: > >> We have a project using JackRabbit 1.5, Spring 2.5.6, Spring-modules 0.9 > >> (the > >> JCR parts), deployed on Tomcat 6. When deploying the project, this > >> exception > >> is thrown: > >> > >> http://www.nabble.com/file/p21032058/stack.txt stack.txt > >> > >> It seems that the StringIndex class has been moved in JCR 1.5 and the > >> Spring > >> JCR module references it from the old package namespace. Does anyone > have > >> an > >> idea of how to get around this, or is there a way to patch > >> spring-modules-jcr to fix this? > > > > The following part of the stack trace suggest that the problem is the > > persistence manager class you have configured in the <Versioning> > > section of your repository.xml file: > > > > Caused by: java.lang.NoClassDefFoundError: > > org/apache/jackrabbit/core/persistence/bundle/util/StringIndex > > at java.lang.Class.forName0(Native Method) > > at java.lang.Class.forName(Class.java:242) > > at > > > org.apache.jackrabbit.core.config.BeanConfig.newInstance(BeanConfig.java:104) > > at > > > org.apache.jackrabbit.core.RepositoryImpl.createPersistenceManager(RepositoryImpl.java:1338) > > at > > > org.apache.jackrabbit.core.RepositoryImpl.createVersionManager(RepositoryImpl.java:450) > > > > Are you using a custom persistence manager? > > > > BR, > > > > Jukka Zitting > > > > > > -- > View this message in context: > http://www.nabble.com/Deployment-problems-when-deploying-Jackrabbit-1.5-with-spring-modules-jcr-tp21032058p21032962.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > >
