Hi Peter!
apologize for not having been more precise on explaining my idea:
while they look similar, I would consider the Sitemap a superset of
pure Pipeline fluent APIs.
Indeed, while a Sitemap woud _describe_ an "action" would be performed
if the current pattern matches against the input, the P
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, Au
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 -
Hi Simone,
long time ago we had discussions on alternate languages for the C2 Sitemap,
I used to want to do them in XSLT (as opposed to XML) with Java extensions
to implement the actual interface from the XSLT to the resulting Cocoon
object tree for the sitemap. These days I sometimes wonder if I
Hi all guys,
I've had this mail draft for a long while and I think it's time to
shout it out to get your feedbacks.
Due to my involvement in Apache Commons and being strongly influenced
by the Google-Guice design, I think we could get benefit from a vision
that mixes the power of:
* modularity;
