Hi, I'd hesitate customizing the key activation feature, instead you can write a custom listener class saving you from this infinite loops, i.e. invoke the activation command only when the node at the target instance doesn't exist yet. For the job you might want to consider subclassing CommandEventListener or implementing EventListener interface.
Alternatively: * modify the templates so that users are stored to and read from always only one public instance. * if your instances are keen to load balancing, let him respond the only one Public for PUR requests. HTH, -zdenek On Wed, 2012-02-29 at 09:53 +0100, Magnolia Forums (on behalf of Vineet Mehta) wrote: > Hi Antti, > > Thanks for your prompt response and suggestion, infact we did look at the > clustering option. > It seems to be tedious, since we have 2 database's corresponding to 2 pairs > of public-author instances. And it will be a bit of overhead to maintain a > partial cluster for users. Also, guess we need to get Infra guys involved for > new database. > > I was digging into the activation code, so that I could add a check some > where to break the cycle. > I tried to add a (custom) property to ActivationContent in activate method of > SimpleSyndicator so that same content does not get activated again, but > doesnt seem to work. > > Quick and dirty solution, that works is to hook the custom activation code in > the Controller where we create/modify the user. > > Thanks > ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
