Return-Path: 
 <dev-return-51619-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 12512 invoked from network); 18 Nov 2003 13:09:23 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 18 Nov 2003 13:09:23 -0000
Received: (qmail 28099 invoked by uid 500); 18 Nov 2003 13:09:16 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 28020 invoked by uid 500); 18 Nov 2003 13:09:15 -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 27808 invoked from network); 18 Nov 2003 13:09:13 -0000
Received: from unknown (HELO out003.verizon.net) (206.46.170.103)
  by daedalus.apache.org with SMTP; 18 Nov 2003 13:09:13 -0000
Received: from verizon.net ([209.237.227.194]) by out003.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20031118130914.BAVC1420.out003.verizon.net@verizon.net>
          for <dev@cocoon.apache.org>; Tue, 18 Nov 2003 07:09:14 -0600
Message-ID: <3FBA1207.3010809@verizon.net>
Date: Tue, 18 Nov 2003 07:35:19 -0500
From: Vadim Gritsenko <vadim.gritsenko@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: XSP "official" position
References: <3FB97CAB.5080401@apache.org> <3FB98BE0.7020304@verizon.net>
 <3FB98F07.1000800@umn.edu>
In-Reply-To: <3FB98F07.1000800@umn.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from
 [209.237.227.194] at Tue, 18 Nov 2003 07:09:13 -0600
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Tony Collen wrote:

> Vadim Gritsenko wrote:
>
>> XSP if not perfect, but we still need some kind of "official" 
>> templating. What's the alternatives here?
>>
>> ... and it's not that convinient to assemble DOM (or something) in 
>> flow and then pass it to the templates... ;-)
>
>
>
> Even the JXTemplateGenerator?  I think it's nice and useful.



Sure, it might be nice, and it is useful. Is it cacheable? To give you 
simple example:

<xsp:page language="java"
          xmlns:xsp="http://apache.org/xsp"
          xmlns:xsp-session="http://apache.org/xsp/session/2.0">
  <xsp:logic>
    public java.io.Serializable getKey()
    {
        if (request.getSession(false) == null) {
          return "0";
        } else if(request.getSession().getAttribute("user") != null) {
          return "1";
        } else {
          return "0";
        }
    }
    public SourceValidity getValidity() {
       return NOPValidity.SHARED_INSTANCE;
    }
  </xsp:logic>

  <menu>
    <page name="Home" link="welcome"/>
...
        <xsp:logic>
            if(<xsp-session:get-attribute name="user"/> != null) {
                <page name="Logout" link="logout"/>
            } else {
                <page name="Login" link="login"/>
            }
        </xsp:logic>
  </menu>
</xsp:page>


> Perhaps the problem is that the flow layer isn't as "up-front" as 
> other things...


What JXTemplateGenerator has to do with flow? AFAIK, it is good without 
flow too! :)

Vadim