Thanks Antonio, but the problem persists, as the cause of it, seems not to be related with the contents of <xsp:expr>, rather with the parent tag of <xsp:expr>.
-------- David -----Mensaje original----- De: Antonio Gallardo [mailto:[EMAIL PROTECTED] Enviado el: jueves, 20 de noviembre de 2003 9:55 Para: [EMAIL PROTECTED] Asunto: Re: Possible bug in XSP generator Try this: <xsp:logic> for (java.util.Iterator it = ajs.getMods().iterator(); it.hasNext(); ) { </xsp:logic> <xsp:expr>it.next().toString()</xsp:expr><br/> <xsp:logic> } </xsp:logic> Best Regards, Antonio Gallardo Carmona Perez, David dijo: > 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
