As I stated, I used the jsp:directive syntax. You'd think the spec would be
a little more clear about this. It's pretty easy to miss that brief
sentence while scanning for answers...
Thanks for the help.
Andrew
At 09:53 PM 8/17/2004, you wrote:
JSPs don't use the mime-mappings from web.xml (per
Despite having set a mime mapping for the .faces extension in my web.xml,
Tomcat 5 still insists on returning a JSP 2 documents with the .faces
extension as text/xml.
Am I doing something wrong?
mime-mapping
extensionfaces/extension
mime-typetext/html/mime-type
/mime-mapping
It sounds like there is another servlet/filter/?? setting the content type to
text/xml.
-Tim
Andrew Shirk wrote:
Despite having set a mime mapping for the .faces extension in my
web.xml, Tomcat 5 still insists on returning a JSP 2 documents with the
.faces extension as text/xml.
Am I doing
This is pretty much a stock T5 install. No filters are configured for this
app. So if it is indeed a servlet, it must be the faces servlet or the jsp
servlet that is applying the text/xml mime type. However, as a work around,
I am able to use a jsp directive to set the mime type from the
JSPs don't use the mime-mappings from web.xml (per the JSP spec). You have
to use the jsp:directive.page contentType=... / syntax.
Andrew Shirk [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
This is pretty much a stock T5 install. No filters are configured for this
app. So if it is
