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
On Thu, 23 Aug 2001, Mark Abbott wrote:
Date: Thu, 23 Aug 2001 15:04:49 -0700
From: Mark Abbott [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [BUG] Jasper parsing of XML documents
On the off chance anyone needs to know (and I appear
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
