cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Hunsberger <>
Subject Re: [Discuss] Sitemap NG
Date Mon, 06 Aug 2012 15:40:19 GMT
Hi Simone,

I guess the part I'm missing is how would this differ from what is already
in Cocoon 3 as an API?  I do get that part (most, all?) of you objective is
to get rid of the Spring layer, so maybe the end result is essentially the
same as the C3 API in the end?

Peter Hunsberger

On Mon, Aug 6, 2012 at 10:33 AM, Simone Tripodi <>wrote:

> Hi Peter!
> My proposal is writing an intermediate layer to create sitemaps, it
> doesn't aim to replace the existing infrastructure but IMHO it could
> be used as the foundation to create sitemaps; while all textual
> configurations work fine, having a more expressive and type checking
> APIs could help - and users could still wrap them in their bigger
> picture, making the tree objects construction easier.
> You could have a look at the Apache Commons Digester binder[1] APIs,
> which are wrapped by the XML configuration[2] and annotated
> elements[3]. One expressive layer to create the sitemap, multiple way
> to bind them.
> I agree that building tree objects would still work, but Fluent
> Interfaces would help on respecting the configuration status, i.e. the
> first element of a Pipeline can only be a Starter, when using the "old
> way" users are still able to setup a pipeline with no starter and find
> the error only when executing it.
> I am sure there are cases I am not taking in consideration that would
> break my PoC as well :P
> what do you think? You would be still able to load a graph from Neo4j
> and setup the pipeline using directly native Java APIs - no parsing,
> no transforming, a little faster :P
> Many thanks in advance, all the best!
> -Simo
> [1]
> [2]
> [3]
> On Mon, Aug 6, 2012 at 4:21 PM, Peter Hunsberger

View raw message