Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v606)
In-Reply-To: <3FA6C99F.4050202@apache.org>
References: <3FA65ECC.4030707@apache.org> <3FA67FD2.6090900@apache.org>
 <3FA684D2.9040409@vafer.org> <3FA6868E.1000405@apache.org>
 <3FA690BD.5020302@vafer.org> <bo6b46$pll$1@sea.gmane.org>
 <3FA6C99F.4050202@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B69B60BC-0E72-11D8-AE16-000393B61B56@apache.org>
Content-Transfer-Encoding: 7bit
From: peter royal <proyal@apache.org>
Subject: Re: [VOTE] rollback Cocoon 2.2 and do Fortress merge later (was Re:
 Fortress Conversion Stalled)
Date: Mon, 3 Nov 2003 21:58:06 -0500
To: dev@cocoon.apache.org

On Nov 3, 2003, at 4:33 PM, Berin Loritsch wrote:
> Anyhoo, the basic solution is to either build a tree/graph of pure 
> components
> or a tree/graph of pure beans.  Either solution will work.  We need to 
> get rid
> of the need for the LifecycleHelper type class.  I would lean more 
> toward the
> bean approach for assembling the actual pipelines.  It might make 
> things a bit
> simpler, even to make custom hard-coded sitemaps.

Anyone:

Any thoughts about using Jelly as the builder for the sitemap?

Its usage can be completely hidden, but as a tag processor, it might 
work very well. We could use it to construct a bean-graph to model the 
sitemap.

-pete