hi eli,
unfortunately you got that right. jackalope-doctrine-dbal does not do
versioning at the moment. only jackalope-jackrabbit does it, because it
can rely on jackrabbit to do the hard work of it.
i think it should not be insanely complicated to implement. you would
have to implement the interface
https://github.com/jackalope/jackalope/blob/master/src/Jackalope/Transport/VersioningInterface.php
in the class
https://github.com/jackalope/jackalope-doctrine-dbal/blob/master/src/Jackalope/Transport/DoctrineDBAL/Client.php
though there is some additional hidden things here. either we would have
to implement full versioning and expose the versions as phpcr paths as
well, or we would need to refactor jackalope core to work with simple
versioning too and add methods to the VersioningInterface to support
getting the version history directly.
so all in all i think it would be rather challenging, but we would be
glad to help you if you want to do this.
your other option would be to use jackalope-jackrabbit for now. its not
harder than using some other java based things like elasticsearch. just
drop the jar and do java -jar (but of course needs java on the server,
there are use cases to want to use jackalope-doctrine-dbal, which is why
it exists)
cheers,david
> --
> You received this message because you are subscribed to the Google
> Groups "Jackalope" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
jackalope-de...@googlegroups.com.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>
--
Liip AG // Agile Web Development // T
+41 26 422 25 11
CH-1700 Fribourg // PGP 0xA581808B //
www.liip.ch