I am considering the use of PHPCR and its reference implementation of
Jackalope for a production project. Are they ready with all the JCR
features implemented. Also, are they in a stable condition for using
in production applications. I am not able to find this information
anywhere so wanted to check it here.
Thanks,
gg
There are still 2 major features missing:
- ACLs
- observers
Aside from this there are still a few minor features missing.
But in general with Jackalope+Jackrabbit you can use tree traversal, versioning, queries etc.
It definitely works reliable enough with the available features and the API is very stable.
But we are still working hard on implementing all the missing features.
We here at Liip.ch are using Jackalope with Jackrabbit in production already with one of our biggest clients ever, but obviously its easier to feel confident if you are involved in the development. We are absolutely committed to continue investing heavily into improving this entire stack. But do feel invited to join the development :)
You can see the status of our test suite on travis ci:
http://travis-ci.org/#!/jackalope/jackalope/builds/363803
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
Thanks,
gg
> Thanks a lot Lukas for your reply. It is good to know that you are
> already using it in production. Also, which backend is more stable -
> Jackrabbit or Doctrine? We prefer Doctrine but is it as stable and
> feature complete as Jackrabbit?
Doctrine is still in its infancy. We expect it to eventually be a fairly viable alternative for small to midsized needs. It will however never reach the performance and scalability of Jackrabbit or the Midgard (written in C).
Here is the test state of Jackalope using Doctrine DBAL to store data in MySQL:
http://travis-ci.org/#!/jackalope/jackalope/builds/363885
hi,
disclaimer: lukas and i work both at liip, both at this project.
* one more example of production project using the jackalope+jackrabbit
setup is http://www.liip.ch :-)
* jackrabbit is like solr. you put it on a server and there is some
startup script and a monitoring script [1]
* we have an extensive api test suite that covers the api usage. you can
run it with the --coverage-html option to see coverage. its not perfect
but i'd say quite good, and we work on it :-)
* there will be an official announcement later, but it seems we probably
found an intern who will work on jackalope bugfixing and the doctrine
transport one day per week from january until summer.
one way to go could be to start the project with jackrabbit as backend
(as its more feature complete) and then switch to doctrine-dbal once it
is ready - if by then you are still not comfortable with jackrabbit,
that is :-)
cheers,david
[1] https://github.com/sixty-nine/Jackrabbit-startup-script
- --
Liip AG // Agile Web Development // T +41 26 422 25 11
CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7YhA8ACgkQqBnXnqWBgIsKDgCfZm785mpPxxSjqY3/spK742/M
QoQAoIteZAO/mo1e16LVC2fNGxTDs2Sc
=GGAe
-----END PGP SIGNATURE-----
I am specifically interested in the ACL feature for Jackalope +
Jackrabbit. Can you please tell me if someone is already working on
this and if so, when can it be available.
Thanks,
gg
On Dec 2, 9:53 am, David Buchmann <david.buchm...@liip.ch> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> hi,
>
> disclaimer: lukas and i work both at liip, both at this project.
>
> * one more example of production project using the jackalope+jackrabbit
> setup ishttp://www.liip.ch:-)
> Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
ACL's are not yet implemented. The interfaces also are not yet ported
from JCR to PHPCR.
We would love to have some help there and would support anyone taking
a stab at this!
regards,
Lukas
On 02.12.11 17:11, Lukas Smith wrote:
> On Dec 2, 1:10 pm, gg <ggeh...@gmail.com> wrote:
>> Thanks a lot for helping clarify my doubts.
>>
>> I am specifically interested in the ACL feature for Jackalope +
>> Jackrabbit. Can you please tell me if someone is already working on
>> this and if so, when can it be available.
>
> ACL's are not yet implemented. The interfaces also are not yet ported
> from JCR to PHPCR.
And looks like there's ne HTTP (WebDAV/Davex) interface for ACL yet in
jackrabbit. A little test java program throws me a
javax.jcr.UnsupportedRepositoryOperationException: JCR-1104
at
org.apache.jackrabbit.jcr2spi.SessionImpl.getAccessControlManager(SessionImpl.java:503)
at Client.main(Client.java:29)
So at least for setting and reading ACLs, you need a different way right
now. Of course, they would be applied if you do operations from
jackalope/php, you just can't change or read the permissions right now.
BUT:
***
16.3.11 Exposing Policies in Content
A repository may expose a node's access control policies as child nodes
or properties. If it does so, then the add, remove and save semantics of
the item must match those of the policy it represents.
***
and I think jackrabbit does it this way. So we could manipulate those
nodes instead of using the API calls (no idea if possible), but this is
of course quite some work as you have to simulate the API, so it may be
easier to just extend Jackrabbit with the necessary API calls on the
HTTP level.
chregu
> We would love to have some help there and would support anyone taking
> a stab at this!
>
> regards,
> Lukas
>
--
Liip AG // Feldstrasse 133 // CH-8004 Zurich
Tel +41 43 500 39 81 // Mobile +41 76 561 88 60
www.liip.ch // blog.liip.ch // GnuPG 0x0748D5FE
https://issues.apache.org/jira/browse/JCR-2003
if it's a known issue :)
chregu