Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <4561FEDD.4000309@nada.kth.se>
Date: Mon, 20 Nov 2006 20:15:41 +0100
From: Daniel Fagerstrom <danielf@nada.kth.se>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Shielded class loading between blocks
References: <ejs2ho$2cj$1@sea.gmane.org> <45618FC0.1070706@apache.org>
 <4561A6C0.7030000@nada.kth.se> <4561AAD5.7080703@apache.org>
In-Reply-To: <4561AAD5.7080703@apache.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Reinhard Poetz skrev:
> Daniel Fagerstrom wrote:
> 
>> Seem like a good solution to me. I would prefer putting this 
>> functionality in a ShieldingBlockServlet that extends the BlockServlet 
>> though. If we put to much extras in the BlockServlet it will be hard 
>> for people to understand what it does and to contribute to make it 
>> stable.
> 
> Wouldn't be servlet filters the best solutions for these cross-cutting 
> concerns? (another example is the reloading classloader that we should 
> move from sitemap level to the block level).

That would require that we created some kind of block filters analog to 
the block servlet and created some mechanism for wiring these together 
in the Spring container. Entirely possible, but do we really like to add 
that level of complexity?

/Daniel