Hi, Mike Müller schrieb: > I just updated the documentation about Resources under [1] and stumbled > over an old page in the public wiki about Resources under [2] which seems > to be pretty up to date.
Yes, [2] is the design concept which stood at the beginning of the current ResourceResolver, Resource and ResourceProvider infrastructure. > There's an paragraph about Filters and Filter Scripts. > I haven't seen that before, so my question is if the this applies to the > actual version of Sling or not. If yes, does that mean I can store some > scripts under /filters/ in the JCR or not. And if yes again, what do this > Filter Scripts filter? No, this is still in the conceptual phase. > I do not mean Servlet Filter Support, which is well documented under [3] Well, actually, it *is*. The point of the filer section in [2] is, that we had the idea to support script based filters much like we have rendering scripts. The filters would be available from the resource tree (through the ResourceResolver) and applied according to the current resource. Just like servlets which are mapped into the resource tree by means of the ServletResourceProvider, there would be FilterResourceProvider, which would map registered Filter services into the resource tree. The request processor would then select the appropriate filters to call in order. This mechanism, though, has never been implemented. And maybe it never will be ... But it showed as another nice example of how the resource tree could be used to make request processing in Sling much more versatile. HTH Regards Felix > > > [1] http://cwiki.apache.org/confluence/display/SLINGxSITE/Resources > [2] http://cwiki.apache.org/SLING/everything-is-a-resource.html > [3] http://incubator.apache.org/sling/site/filters.html > > best regards > mike >
