On Nov 15, 2007 10:18 PM, Grégory Joseph <
dev-list@...> wrote:
> On Nov 15, 2007, at 21:39 , Fabrizio Giustina wrote:
> I thought I did, and moved the implementation accordingly: the
> alternative is ModuleLifecycle.start(). See the CacheModule class,
> for instance. [1]
there are two important thinks missing:
- the automatic handling of a global save/rollback
- the ability to use "normal" update tasks that you can also use in a
module upgrade. If the sample you were referring at is the static
AddCacheVoterTask.addVoter() that is definitively only an hack, not
anything really usable.
So, I would be glad to agree that this kind of tasks could fit well in
a ModuleLifecycle implementation, but please rollback that change
until there is a real alternative that fulfill those needs please.
Mark the method with a clear "this will be moved somewhere else soon",
but put it back...
fabrizio
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html----------------------------------------------------------------
