Felix Meschberger wrote:
This in fact applies not just to post processing but also to
pre-processing. In fact, we might emply the same basic mechanism for
pre- and post-processing as we envision for servlet filters: Registered
services are entered as pre/post-processor resources into the virtual
resource tree at a pre-defined location. pre/post-processor scripts
might be located at the same place and selected for execution.
>
You mean registering all services in the resource tree even the Java
based ones?
Nevertheless, I would keep on seing the SlingPostServlet as the
controller and _not_ any script handling post requests -- something like
"don't call us, we'll call you".
Yes, definitly.
For now I have the problem of seeing a nice way to actually call the
script. Do we envision that the script contains some defined methods?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
