Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <4612A6F8.1060906@apache.org>
Date: Tue, 03 Apr 2007 21:11:52 +0200
From: Grzegorz Kossakowski <gkossakowski@apache.org>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Circular deps in servlet connections (was Re: Servlet Services
 + Shielding)
References: <eut5il$b2s$1@sea.gmane.org> <eutusa$rdk$1@sea.gmane.org>
 <euu6dk$vvf$1@sea.gmane.org>
In-Reply-To: <euu6dk$vvf$1@sea.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Alexander Klimetschek napisał(a):
> Oh, I got it: there was a circular dependency in the servlet connections 
> (A using B, B using A as super). It did work with the old block 
> servlets, but now you get the very unhelpful exception. I don't think we 
> actually need this circular connection in particular. But generally, two 
> solutions are available:
> 
> Is it possible to allow circular dependencies in the servlet connections?
> 
> If not, there should be at least some kind of check that prints a better 
> message.
> 

My opinion is that circular dependencies should not be allowed and I 
agree that more meaningful exception is needed here.

Could you please create an issue for this? Providing a patch would be 
even more appreciated. If you are going to work on it please let me know 
to not duplicate the effort.

-- 
Grzegorz Kossakowski