we know that the xsp.xsl is somewhat buggy. In this special case a bug already exists: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15841. The reason for your problem is, that first xsp:attribute is collected and afterwards all the other elements.
Joerg
On 19.01.2004 17:34, Marcin Okraszewski wrote:
Hi,
I have a filling that there is some bug with xsp:attribute. It seems, that attributes are always created, no matter if there is some logic that should prohibit to create the attribute.
For instance: <layout:data-source> <xsp:logic> if (false) { </xsp:logic> <xsp:attribute name="should-not-be">true</xsp:attribute> <xsp:logic> } </xsp:logic> </layout:data-source>
is transformed to:
xspAttr.addAttribute( "", "should-not-be", "should-not-be", "CDATA", "true" );
this.contentHandler.startElement( "http://www.eti.pg.gda.pl/layout";, "data-source", "layout:data-source", xspAttr );
if (false) {
}
Well, this is far from what I expected :-(
I'm working with Cocoon 2.1.4-dev (version from something like 1-2 months ago).
Regards, Marcin Okraszewski
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
