Ahh, excellent, I wasn't 100% sure what that reference was to. I will
give that a try since we really don't want our repository.xml files
sitting somewhere on the file system (if we have to make a change
that's a real pain to have to do everywhere and I will invariable
forget that it needs to get changed everywhere).
-warner
On Oct 1, 2008, at 9:13 AM, Alexander Klimetschek wrote:
On Wed, Oct 1, 2008 at 5:15 PM, Warner Onstine
<[EMAIL PROTECTED]> wrote:
Wow, that's, um, special. Any ideas as to when this will get rolled
into the
main build?
As noted in the issue, it will be included in the 1.5 release, which
will take a few months I guess.
As a workaround you could either extract the repository.xml from your
war files (which I recommend, because it simplifies server
administration, even if the standard jackrabbit webapp includes it
inside), or remove the cluster id attribute and set the magic system
property "org.apache.jackrabbit.core.cluster.node_id" in your
instances before jackrabbit is started.
Regards,
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
