Return-Path: 
 <dev-return-58326-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 23728 invoked from network); 30 Mar 2004 00:23:55 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 30 Mar 2004 00:23:55 -0000
Received: (qmail 17432 invoked by uid 500); 30 Mar 2004 00:23:36 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 17368 invoked by uid 500); 30 Mar 2004 00:23:36 -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 17354 invoked from network); 30 Mar 2004 00:23:36 -0000
Received: from unknown (HELO exchange.sun.com) (192.18.33.10)
  by daedalus.apache.org with SMTP; 30 Mar 2004 00:23:36 -0000
Received: (qmail 7458 invoked by uid 50); 30 Mar 2004 00:24:20 -0000
Date: 30 Mar 2004 00:24:20 -0000
Message-ID: <20040330002420.7457.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 28017]  -
    xsp: generating a XSP computed attribute does not work for ROOT element
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

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28017>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28017

xsp: generating a XSP computed attribute does not work for ROOT element





------- Additional Comments From joerg.heinicke@gmx.de  2004-03-30 00:24 -------
> (I think that) I'd suggested already prohibiting all events (except empty
>whitespace) between <element> and <xsp:attribute>. This would make any confusion
> impossible. WDYT?

Quoting you from bug #15841:
"To prevent out-of-order execution of xsp:logic... I would recommend enforcing
that xsp:attribute or xsp:logic[xsp:attribute] elements go right after opening
tag, without other nodes in between (except whitespace)."

In which way?

<xsl:template match="xsp:attribute | xsp:logic[xsp:attribute]">
  <xsl:if test="preceding-sibling::*[not(self::xsp:attribute |
self::xsp:logic[xsp:attribute])]">
    <xsl:message terminate="yes">ERROR</xsl:message>
  </xsl:if>
</xsl:template>