I think Jackalope is the PHP option, but I guess you know that if you
googled "PHP JCR" at all. :)

Best regards,
Clay Ferguson
[email protected]


On Fri, Aug 28, 2015 at 11:12 AM, mike osterhout <[email protected]>
wrote:

> I am seeing the same error when using jackrabbit 2.10.1. Oak sounds like a
> nice option, I hope to migrate to that in the near feature when there is a
> good PHPCR implementation. For now just need to get jackrabbit running
> properly under tomcat. All suggestions are welcome.
>
> On Fri, Aug 28, 2015 at 11:25 AM, Clay Ferguson <[email protected]> wrote:
>
> > Lukas,
> > Thanks for clarifying. I looked in the Oak code for the line throwing the
> > NPE, and the entire class didn't exist, so I assumed it was older
> version,
> > and totally forgot to also suggest he go to new version. May not even be
> > among his options or needs. Thanks.
> >
> > Best regards,
> > Clay Ferguson
> > [email protected]
> >
> >
> > On Fri, Aug 28, 2015 at 10:07 AM, Lukas Kahwe Smith <
> [email protected]>
> > wrote:
> >
> > >
> > > > On 28 Aug 2015, at 17:05, Clay Ferguson <[email protected]> wrote:
> > > >
> > > > Mike,
> > > > I think using MongoDb as your storage will perform about 10x (at
> least)
> > > > faster than MySql, for certain operations (bulk inserts for one), and
> > > also
> > > > I think perhaps most people are using MongoDb with JCR, for a fully
> > NoSQL
> > > > stack. Just my opinion, but you should seriously consider using
> Mongo.
> > I
> > > > also have a project using mongo I'll share with you if you decide to
> go
> > > > that route.
> > >
> > > he is asking about Jackrabbit 2.x not about Oak. afaik there is no OSS
> > > MongoDB persistence manager for Jackrabbit 2.0
> > > note he is asking about Jackrabbit 2.x because he wants to use
> Jackrabbit
> > > with PHPCR and since the Oak HTTP layer isn’t ready and implemented for
> > > PHPCR, moving to Oak is not yet an option.
> > >
> > > regards,
> > > Lukas Kahwe Smith
> > > [email protected]
> > >
> > >
> > >
> > >
> >
>
>
>
> --
> Regards,
> Mike
>

Reply via email to