Bertrand Delacretaz wrote:
On Fri, Jul 4, 2008 at 9:53 AM, Dominik Süß <[EMAIL PROTECTED]> wrote:
...After thinking a bit I wondered if it wouldn't make sense to define
interceptionpoints for pre and post processing of any servlet in the request
cycle. This would give the developers a consistent and flexible way to
extend the given functionality by their own needs without being to
intrusive....
IIUC this is pretty much what Carsten suggests - my alternative
proposal is to let the script take complete control and use only bits
of the standard processing, as needed. Both approaches are probably
ok, we'd need more concrete use cases to decide I guess (and this is
the ASF - whoever does it gets to decide, at least for an initial
implementation).
I'm just talking about the sling post servlet - general pre and post
processing
of any servlet (and therefore script) can easily be done by a servlet
filter which is already possible.
What I need is the logic of the post servlet, which detects what has to
be done, which nodes are created, updated etc. I could do my stuff in a
servlet filter but this would mean recoding all the logic of the sling
post servlet.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
