Of course, I can perfectly understand that in non-XML JSP mode there may be glitches in the way the XML is parsed. However, I don't believe it is acceptable to output something that isn't XML when you've explicitly demanded to have XML. (For example, Mozilla-based browsers refuse to display the page and show an "XML Parsing Error" instead (when an XML mime-type is used).)
Jeff Beal wrote:
I'm not familiar enough with the JSPX portion of the JSP documentation to be able to definitively say what is and is not according to the specification. My guess is that the behavior you are seeing is in accordance with the specification. The '&' is parsed normally as XML, creating a simple '&' which is written to the response. The XML parser at the other end sees a stand-alone '&' as non-well-formed and throws an error. '&' will allow '&' to be written to the response, which the XML parser at the other end can then handle appropriately.
-- Jeff
Laurent wrote:
I just realised the problem only occures when my JSP files have the ".jspx" file extension. Files whose names end in ".jsp" do not have this problem. However, my question remains...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
