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

Reply via email to