First of all sorry if I'm annoying anyone but I couldn't find any suitable answer within the Developer Wiki which might be based upon the fact that I'm just starting to play around with Magnolia.
While trying to implement a new renderer I obviously encountered the [code]RenderingModule[/code] class which doesn't contain an implementation of the [code]stop[/code] method. The [code]start[/code] method obviously allows to start it's managers ([code]ConfiguredTemplateDefinitionManager[/code] and [code]ConfiguredRendererManager[/code]). Both are descendants from [code]WorkspaceObservingManager[/code]. This manager registers a listener as part of it's own [code]start[/code] method causing a [code]reload[/code] but it doesn't support any kind of [code]stop[/code]. Telling from the code I would expect that a sequence like this: * RenderingModule.start - registers a first listener per manager * RenderingModule.stop * RenderingModule.start - registers a second listener per manager * ... would result in multiple listeners registered for the same nodes (after all the concrete managers are singletons) thus causing the listener function to be executed multiple times for the same change (hopefully it's clear what I mean here). I suspect that the module never gets restarted so this wouldn't be an issue after all but than the [code]stop[/code] method would be useless. Am I missing something or could it simply be an implementation error ? Bye -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=ca0592d4-9258-4148-8671-167d6da75e3c ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
