Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (athena.apache.org: domain of grek@tuffmail.com designates
 216.86.168.179 as permitted sender)
Message-ID: <47E8FEF4.10603@tuffmail.com>
Date: Tue, 25 Mar 2008 14:32:36 +0100
From: Grzegorz Kossakowski <grek@tuffmail.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20070801)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Servlet via Servlet Services only
References: <EF967B9A-35C7-4E77-8CB0-CFAA1DEA3A33@robinwyles.com>
 <47E8FC6E.4000902@tuffmail.com>
 <74181329-5E24-4391-9044-6E8F7FEADD3A@reverycodes.com>
In-Reply-To: <74181329-5E24-4391-9044-6E8F7FEADD3A@reverycodes.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Vadim Gritsenko pisze:
> On Mar 25, 2008, at 9:21 AM, Grzegorz Kossakowski wrote:
>>
>> What about creating Spring AOP's advice on service() method? You could
>> check there type of Request
>> object and if it's non-SSF instance then you could return HTTP 405
>> (Method Not Allowed) status code
>> as response.
> 
> IMHO Robin's scenario is not unique and ability to declare 'internal'
> servlets should be a standard feature of SSF.

Vadim, I agree that Robin's scenario is rather common but I don't think it's a reason to bloat SSF
with such specific feature that can be easily achieved using Spring AOP.

It's more about providing a good documentation.

-- 
Grzegorz

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org