cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carmona Perez, David" <DPerez...@fcc.es>
Subject RE: Possible bug in XSP generator
Date Thu, 20 Nov 2003 08:45:00 GMT
Additional note:
 
If I change 
<xsp:expr>mod</xsp:expr>
to
<span><xsp:expr>mod</xsp:expr></span>
then it is working ok.
 
Must <xsp:expr> be enclosed inside another tag?
--------
David
 
-----Mensaje original-----
De: Carmona Perez, David [mailto:DPerezCar@fcc.es]
Enviado el: jueves, 20 de noviembre de 2003 9:43
Para: Cocoon (E-mail)
Asunto: Possible bug in XSP generator
 
Hi all,
 
I have this snippet in an XSP file:
 
<xsp:logic>
      for (java.util.Iterator it = ajs.getMods().iterator(); it.hasNext(); ) {
      String mod = it.next().toString();
            <xsp:expr>mod</xsp:expr><br/>
      }
</xsp:logic>
 
and the following code is generated:
 
for (java.util.Iterator it = ajs.getMods().iterator(); it.hasNext(); ) {
                        String mod = it.next().toString();
(mod)
this.contentHandler.startElement("", "br", "br", xspAttr);
    xspAttr.clear();
            }
 
 
I think that the right code would be:
 
for (java.util.Iterator it = ajs.getMods().iterator(); it.hasNext(); ) {
                        String mod = it.next().toString();
this.characters(mod);                          <------------------------
this.contentHandler.startElement("", "br", "br", xspAttr);
    xspAttr.clear();
            }
 
Is this really a bug of the XSP generator?
--------
David
 

Mime
View raw message