Hi Craig -
I'm curious whether the expert group has discussed what
might be done in the future about this unfortunate
aspect of JSP. In what I would think would be a
really common case in the future, where one wants to
design an app using clean, readable, and purely XML
templates (perhaps
On the off chance anyone needs to know (and I appear to be
the only one who cares about XML syntax issues :) it looks
from the code like what Jasper is doing is that, while parsing a tag,
it outputs any uninterpreted child tags it encounters, but accumulates
all child sections of character data
At 04:02 PM 8/23/2001, Craig R. McClanahan wrote:
Do you have uninterpreted text that is *not* inside a jsp:text block?
I don't think that is actually allowed. I will check with the spec lead.
What I actually see is that the following JSP fragment:
tagAtagBtext/tagBtagA
appears just like
Has anyone seen this sort of behavior out of Jasper (tc4b7) before?
I give it a trivially simple JSP page in XML syntax:
?xml version=1.0 ?
jsp:root version=1.2
xmlns:jsp=http://java.sun.com/JSP/Page;
html
body
table
tr
td
Hi again - since no one voiced an opinion on the right way to
approach this bug, I've done the simplest possible fix and attached a patch.
This change will cause Jasper to always emit its own hardcoded values
for the xmlns:jsp and version attributes of the jsp:root tag, ignoring any
Hi all -
I've noticed a couple of problems with Jasper when processing
JSP documents, that is, JSP pages authored in the XML syntax.
I'm using the tomcat-b7 release.
The documents I've tried contain explicit jsp:root elements,
as it seems they ought to. Unfortunately, the XmlOutputter class
in
I believe the Java Language Spec makes specific requirements on the
order of evaluation of static finals to facilitate this kind of usage. In
the past I have
gone so far as to compile test programs and disassemble the byte code
and on every JVM I have ever tried, code wrapped in if statements
