Hello David, > > Hi Bartosz and all ! > > Our clustering is working fine when we editing content or > properties but not at all with the "lock". > > Actually if we lock a document using the cms, this > information is not propagate between the different clustered > repositories.
Correct > > AFAIU a lock is not really a property and a lock on a Exactly > document won't trigger a JMS message and this information > will not be correctly clustered. Indeed > > Nobody has an idea how to fix the issue which is not very > comfortable :-( Yes I understand. I know that a lock won't trigger a JMS, but I am not sure wether locks are not propagated between repositories. So, I hoped you could do a test for me: if you make sure that in one cms, you get a lock. Then, go to the other cms, and try to edit the document and save it. Does this work or do you get a message that the document is locked? If it is locked, locking is propagated between repositories, but the cms is just not informed, because no JMS has been sent. Pls let me know your findings, -Ard > > Many thanks, > > > David Calcus > Smals - F. Manini - Web Content Management Rue du Prince > Royal 102, 1050 Bruxelles [EMAIL PROTECTED] > +32 (0)2 787 54 92 > ______________________________________________________________ > ________________________________ > Smals sluit elke aansprakelijkheid uit in verband met de > juistheid, de volledigheid of het tijdig toekomen van de > informatie in deze e-mail. Aan deze e-mail kunnen geen > rechten worden ontleend en deze e-mail houdt in geen geval > een erkenning van welkdanige aansprakelijkheid in. > Dit bericht is alleen bestemd voor de geadresseerde. Indien > dit bericht niet voor u bestemd is, verzoeken wij u dit > onmiddellijk aan ons te melden en het bericht te vernietigen. > > Smals décline toute responsabilité quant à l'exactitude, à > l'exhaustivité et au délai de transmission des informations > contenues dans cet e-mail. Aucun droit ne peut être > revendiqué sur cet e-mail et cet e-mail n'implique en aucun > cas une reconnaissance de responsabilité, quelle qu'elle soit. > Ce message s'adresse uniquement au destinataire. Si ce > message ne vous est pas destiné, nous vous prions de nous le > signaler immédiatement et de détruire le message. > > > > Bartosz Oudekerk <[EMAIL PROTECTED]> Sent by: > [EMAIL PROTECTED] > > 14/05/2008 16:51 > Please respond to > [EMAIL PROTECTED] > > > > > To > [EMAIL PROTECTED] > cc > Subject > Re: [Smals] Yet Another Clustering Problem > > > > > > > [EMAIL PROTECTED] wrote: > > > > Bartosz, > > > > I think I found the problem with the clustering ! ;-) > > I have added this line in the events.xml on the repository : > > > > <listener role="java.util.EventListener/jms-cluster-propagator"/> > > > > And now, it work correctly and we have our repository in > clustering, I > > see in the slide.log file the publication of messages \o/ > > > > So, when I have made the repository, I based myself on the template > > given with the repository 1.2.15 (J2EE-Template folder). > But this line > > is not in events.xml ! > > It's a forget ? Can maybe cause the same behaviour in the > future (for > > others people) ?!? > > Thanks, wel spotted! I will commit this immediately. > > Regards, > -- > Bartosz Oudekerk > .---------------------------------.--------------------------- > --------. > | Hippo B.V. | Hippo USA Inc. > | > | Oosteinde 11 | 101 H Street, suite Q > Petaluma CA | > | 1017 WT Amsterdam | 94952-3329 San Francisco > | > | The Netherlands | United States > | > | Tel +31 (0)20 5224466 | +1 (707) 773-4646 > | > +---------------------------------+--------------------------- > --------+ > | [EMAIL PROTECTED] | > http://www.onehippo.com | > `---------------------------------^--------------------------- > --------' > _______________________________________________ > Smals mailing list > [EMAIL PROTECTED] > http://lists.hippo.nl/mailman/listinfo/smals > > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
