Hi James, nice workaround. However I would prefer to not couple the execution of the other handlers to the move handler, as this handler only kicks in on a few specific paths where the other handlers are observing much more of the repository.
Regards, Markus On Fri, Oct 7, 2011 at 5:54 PM, James Stansell <[email protected]> wrote: > Hi Markus, > > Just thinking out loud - can the other handlers do their work after the node > has been moved? The "move" handler could send an event once it is done. I > once used a custom event for a similar purpose. > > -james. > > > On Fri, Oct 7, 2011 at 10:34 AM, Markus Joschko > <[email protected]>wrote: > >> Is there a way to to order the event handlers? >> I have multiple event handlers executing on node creation. >> >> One of these handlers will move the node to a new location. Obviously >> that should happen after the others done their changes as otherwise >> they try to operate on an outdated path. >> Can I guarantee this? I thought about the service ranking but couldn't >> find anything that strengthen that. >> Alternatively I could schedule a job that moves the node in 5 seconds >> so the other handlers have enough time to execute. But that's a bit >> ugly. >> >> Any other ideas? >> >> Thanks, >> Markus >> >
