RE: Possible bug in XSP generator

[Carmona Perez, David]

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:[EMAIL PROTECTED] 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