Hi
I am looking for a developer who really knows how to setup and integrate
jackrabbit within a high-availability clustered environment (50Mio
content nodes and 50K concurrent sessions, whereas it will keep growing)
who helps us in a one or two day session to understand and avoid pitfalls.
Hello,
JeCARS version history backup works for straightforwards versioning... which
means it has
problems with version nodes which contains child nodes with version
etc...etc..
The JeCARS backup algorithme is (I think) a bit different it tries to
redo the checkin()/checkout() calls from the
JeCARS backup also restore the original jcr:created property in
versions? This is a protected property as I know.
El sáb, 15-03-2008 a las 10:06 +0100, Jacco van Weert escribió:
Hello,
JeCARS version history backup works for straightforwards versioning... which
means it has
problems with
Hi,
Here's a draft of the Jackrabbit board report that I'm planning to
send tomorrow. Let me know if there's anything you'd like to changes
or add.
Apache Jackrabbit is a fully conforming implementation of the Content
Repository for Java Technology API (JCR, specified in JSR 170).
The
[
https://issues.apache.org/jira/browse/JCR-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Brosius updated JCR-1479:
--
Attachment: no_reflective_toarray.patch
[PATCH] don't use the reflective form of {Collection}.toArray
[PATCH] don't use the reflective form of {Collection}.toArray
-
Key: JCR-1479
URL: https://issues.apache.org/jira/browse/JCR-1479
Project: Jackrabbit
Issue Type: Improvement