#: (Jean-Sebastien Bournival) changed the world a bit at a time by saying on
11/14/2005 3:26 PM :#
Well the only solution I found to this is to create a servlet Filter in
front of the ActivationServlet (this is the servlet called when a content is
activated). Then, from the request headers, I can extract data so that I
can call whatever business actions.
As a general solution it sounds good to me.
How does this sounds to you? Is there another way? An interface to
implement?
Don't think so. However, right now Sameer and myself are working on implementing a more general
activation/deactivation mechanism and maybe this addition would make sense. I am not sure how
helpfull the workflows will be here, cause I don't want to reach a point where this feature is
present in 2 ways.
Maybe the guys involved with the workflow can comment on this. Thanks
./alex
--
.w( the_mindstorm )p.
Thanks,
JS.
-----Message d'origine-----
De : [email protected] [mailto:[EMAIL PROTECTED]
Envoyé : 9 novembre 2005 16:41
À : [email protected]
Objet : Re: [magnolia-user] Listeners on content activation
#: (Jean-Sebastien Bournival) changed the world a bit at a time by saying
on 11/9/2005 11:21 PM :#
Hi I browsed the user list archive and didn't found any answer to this
question :
Is it possible to have a listener/event handler upon a content activation?
e.g. : An author creates a "news" item. He activates it. A listener
(or event handler) is alerted and take appropriate actions regarding this
event.
Thanks.
afaik currently this is not possible. However, the workflow integration is
starting and I think this might be one of the things that will be solved.
I am not sure if from the pov of JCR this is possible (change on a property
to trigger an event), but we can check with the spec.
./alex
--
.w( the_mindstorm )p.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
