Return-Path: 
 <dev-return-68781-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 52915 invoked from network); 2 Dec 2004 20:48:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 2 Dec 2004 20:48:32 -0000
Received: (qmail 55727 invoked by uid 500); 2 Dec 2004 20:48:29 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 55668 invoked by uid 500); 2 Dec 2004 20:48:29 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 55654 invoked by uid 99); 2 Dec 2004 20:48:28 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from out2.smtp.messagingengine.com (HELO
 out2.smtp.messagingengine.com) (66.111.4.26)
  by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 02 Dec 2004 12:48:27 -0800
Received: from frontend2.messagingengine.com (frontend2.internal
 [10.202.2.151])
	by frontend1.messagingengine.com (Postfix) with ESMTP id B9BCCC3DD03
	for <dev@cocoon.apache.org>; Thu,  2 Dec 2004 15:48:24 -0500 (EST)
X-Sasl-enc: Qm8sCqIJavFnevWJ8E9tEA 1102020503
Received: from [10.0.0.102] (elfriedeholmes.demon.co.uk [80.177.165.206])
	by www.fastmail.fm (Postfix) with ESMTP id 991C356F504
	for <dev@cocoon.apache.org>; Thu,  2 Dec 2004 15:48:23 -0500 (EST)
Message-ID: <41AF7F07.20706@upaya.co.uk>
Date: Thu, 02 Dec 2004 20:45:59 +0000
From: Upayavira <uv@upaya.co.uk>
User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [Design] JXTG 2.0 (Just say no!)
References: <41A4E5EF.9050703@nada.kth.se>
 <BD8BACC8-43E7-11D9-B336-000393539234@pcextremist.com>
 <41AEFE7E.60909@nada.kth.se> <41AF5863.4080701@apache.org>
In-Reply-To: <41AF5863.4080701@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Stefano Mazzocchi wrote:
<snip/>

> What I want is something like this:
>
>  - request comes
>  - sitemap gets it
>  - matcher matches
>  - controller is executed and populates beans in the request context
>  - pipeline is invoqued with access to the request context
>  - response goes
>
> Now, this can happen right now in flow and JXtemplate. If we don't 
> need state management, this is just like having a better action model 
> with XSP-like code recompilation.
>
> But the whole point of this discussion is: do we need taglibs?
>
> I'm sorry, but I agree with Miles, we don't: all we need is a 
> velocity/garbage-like template system and recompilable java controllers.
>
> Everything else is making a step backwards.

Stefano, for those that skipped taglibs in their path to Cocoon (e.g 
me!), can you explain what you don't like about them? I presume you're 
okay with a jxtemplate like syntax, but what you don't like is the fact 
that I can write my own taglib, thus hiding logic not in my controller, 
but in a taglib class somewhere. Is that it? Presumably, you wouldn't 
also be against, for example, implementing the FormsTransformer as a 
part of a templating system? i.e. having the template put the widget 
values straight into the SAX stream.

Have I understood, or are you getting at something else?

Regards, Upayavira