Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3BC6E6D8.26D1300D@apache.org>
Date: Fri, 12 Oct 2001 14:49:28 +0200
From: Stefano Mazzocchi <stefano@apache.org>
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: The Problems with Sitemap Factories
References: <GMEBIBHGAOFGJCDPJANDIEJOCOAA.cziegeler@sundn.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Carsten Ziegeler wrote:
> 
> Hi Team,
> 
> I would like to propose that we get rid of the sitemap factories,
> the selector and matcher factory.
> 
> I see at least three reasons for this:
> - If you want to use a matcher factory inside a subsitemap,
>   you currently MUST redefine it in the subsitemap as it is
>   not "inherited" from the parent sitemap. This is true
>   of course also true for selectors (I entered this already
>   in bugzilla).
>   Using matchers and selectors in subsitemaps becomes very
>   error prone as you always as a sitemap editor have to be
>   aware if it is *implemented* as a factory or not. I think
>   the sitemap editor does not have to know about such technical
>   details.
> - The factories are hard to code. Java code generated from strings
>   is not so easy to write.
> - This is needed for the new RT, like the recent Tree traversal approach
> 
> So I'm +3 on removing the factories and this even for the final release!

+1, whatever makes it easier to write subsitemaps I'm all for it.

Let's start removing the code compilation thing.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------


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