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 fix.
From: Joerg Heinicke <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: <xsp:attr> bug? Date: Wed, 10 Sep 2003 09:17:56 +0200
It's not the only one: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15841. These bugs can more or less easily be worked around e.g. by moving the xsp:logic outside the xsp:attribute IIRC.
Joerg
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> </xsp:attribute>
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?
Thanks,
Sonny
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Send and receive larger attachments with Hotmail Extra Storage. http://join.msn.com/?PAGE=features/es
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
