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:
<tagA><tagB>text</tagB><tagA>
appears just like that in the output, without wrapping the
text in a <jsp:text> tag. I assumed this was because the
text was being considered part of an "XML fragment", but the
precise definition of that is unclear.
However, this JSP fragment:
<tagA><tagB></tagB>text<tagB></tagB></tagA>
appears as
<tagA><tagB></tagB><tagB></tagB></tagA>text
unless the text is wrapped in a <jsp:text>, in which case it
appears as written in the JSP. I can clearly see where in
the Jasper code it does this reshuffling.
I tend to agree with you that the first example ought NOT to
to work without the <jsp:text> (unfortunately, since it is convenient),
so the fact that it does is a bug. Clarification would be great if
you can get it.
And the second example should not silently reshuffle the text
either; in both cases the parser should flag the lack of a
<jsp:text> as an error, I guess.
I'll file a bug on this, since it seems something must be wrong in any case...
Thanks! Mark
