On Tue, Feb 10, 2009 at 2:52 PM, Felix Meschberger <[email protected]> wrote: >> However whereas this is one important use case I see another use case >> where I simply want to "run" a pipeline on generated output of some >> script like for doing link checking or doing other general purpuse stuff. >> >> In this case the sling:resourceType would still point to the original >> script doing the html representation and the pipeline would take the >> (html) output and process it. Not sure if we can find a good solution >> for this as well. But we can have a look at the first use case first and >> then see where this leads. > > This kind of post-processing would probably best be placed into a > Servlet Filter ?
+1 I don't know what the latest state of the discussion of a generic filter mechanism is that also includes the ability to use scripts as filters. I think the simplest thing would be if scripts for filters would resolved just as scripts for the main "rendering". Then the .pipeline script type can be used for both use cases. The open question is probably how the "interface" for such a filter script looks like. Regards, Alex -- Alexander Klimetschek [email protected]
