Re: bit by JCR-1558 - what are valid workarounds?

Hi, I am not completely sure if that solves the problem, but could you try sharing the repository-level FileSystem between cluster nodes? That means, configure the first FileSystem entry in the repository.xml (the one directly within the Repository element; not the one within the Workspace

Re: bit by JCR-1558 - what are valid workarounds?

*bump* Surely I can't be the only one who uses custom namespaces and clustering together? On Tue, Jul 6, 2010 at 9:26 AM, Justin Edelson justinedel...@gmail.comwrote: I got hit by JCR-1558[1] (Namespaces aren't registered on cluster nodes) and started to look at how Sling could potentially

bit by JCR-1558 - what are valid workarounds?

I got hit by JCR-1558[1] (Namespaces aren't registered on cluster nodes) and started to look at how Sling could potentially work around this problem. For those that don't know, in Sling, namespaces can be registered via an OSGi bundle header (Sling-Namespaces). Namespaces registered in this