Return-Path: Delivered-To: apmail-sling-dev-archive@www.apache.org Received: (qmail 73254 invoked from network); 1 Dec 2009 15:30:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Dec 2009 15:30:45 -0000 Received: (qmail 67565 invoked by uid 500); 1 Dec 2009 15:30:44 -0000 Delivered-To: apmail-sling-dev-archive@sling.apache.org Received: (qmail 67502 invoked by uid 500); 1 Dec 2009 15:30:44 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 67368 invoked by uid 99); 1 Dec 2009 15:30:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2009 15:30:44 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2009 15:30:41 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B4605234C1F0 for ; Tue, 1 Dec 2009 07:30:20 -0800 (PST) Message-ID: <1515703253.1259681420737.JavaMail.jira@brutus> Date: Tue, 1 Dec 2009 15:30:20 +0000 (UTC) From: "Mike Pfaff (JIRA)" To: dev@sling.apache.org Subject: [jira] Created: (SLING-1213) Filters to support servlet-API-level scope configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Filters to support servlet-API-level scope configuration -------------------------------------------------------- Key: SLING-1213 URL: https://issues.apache.org/jira/browse/SLING-1213 Project: Sling Issue Type: Improvement Components: Engine Reporter: Mike Pfaff Currently the filter.scope supports either - component (comparable to INCLUDE,FORWARD,ERROR of the servlet API) or - request (comparable to REQUEST of the servlet API) In certain cases one wants to have finer control over the filter scopes, e.g. have a filter that would do REQUEST,FORWARD, so that the filter is applied first for the request and then again when you do a requestDispatcher.forward(). Therefore i suggest that the filter.scope should be enhanced as follows: - Make filter.scope a multi-value property - Add filter scopes: include, forward and error - The existing filter scope "component"(quasi an alias for "include,forward,error") should for backward-compatibility not change. - Add filter chains for the new filter scopes (don't know if this is needed internally?) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.