Here's the story...(using JWS 2.0...I know, I know :()
I have a page, call it foo.jsp. Inside of foo.jsp is
<jsp:include page="fooTable.jsp" flush="true" />
Both foo.jsp and fooTable.jsp have
<%@ page contentType="text/html" [etc] %>
When I look at the generated Java source, both
have calls to response.setContentType("text/html").
But despite the fact that fooTable.jsp is called via
a jsp:include action, I get no complaints about it messing
with response headers.
Now the plot thickens...
For various reasons, I want to specify a character set. So
in both cases I change the page directive to
<%@ page contentType="text/html; charset=SJIS" [etc] %>
and sure enough, both generated Java files now have
response.setContentType("text/html; charset=SJIS") in them.
But now an exception IS thrown (IllegalStateException, MIME type
already set) by the server! So I try removing the contentType=XXXX
attribute from the directive in fooTable.jsp and I still
get the exception.
Is this a bug with JWS2.0?
And if not, how on earth ARE you supposed to deal with
non-standard charsets when you use the jsp:include
action?
== Rich
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
