cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sonny Sukumar" <>
Subject Re: <xsp:attr> bug?
Date Wed, 10 Sep 2003 07:24:18 GMT

Yeah, it can be worked around, but is annoying (as all bugs are).  I guess 
it's not a high enough priority to fix though, while still being a pain to 

>From: Joerg Heinicke <>
>Subject: Re: <xsp:attr> bug?
>Date: Wed, 10 Sep 2003 09:17:56 +0200
>It's not the only one: 
> These bugs can 
>more or less easily be worked around e.g. by moving the xsp:logic outside 
>the xsp:attribute IIRC.
>Sonny Sukumar wrote:
>>How comes this doesn't work?:
>><xsp:attribute name="error">
>>  <xsp:logic>
>>      if (somVar == null)
>>        errorStatus = false;
>>      else
>>        errorStatus = true;
>>  </xsp:logic>
>>  <xsp:expr>errorStatus</xsp:expr>
>>What is strange to me that Cocoon doesn't complain in producing the Java 
>>code, but that it puts the equivalent Java code for 
>>"<xsp:expr>errorStatus</xsp:expr>" *before* the equivalent code fo the

>><xsp:logic> block.  So it then fails to compile, saying that variable 
>>errorStatus may not have been initialized.
>>So why does Cocoon generate the Java code backwards?
>To unsubscribe, e-mail:
>For additional commands, e-mail:

Send and receive larger attachments with Hotmail Extra Storage.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message