Works for me. Every mime-type usually lays claim to a default suffix
or two and we should definitely pick one and say that there is an
implicit mapping for that prefix. So if I name my pages jspx then I
don't have to worry about setting any mappings to get a JSP container
to interpret the page
Tom Reilly wrote,
So here's my proposal:
JSP 1.2 engines have mime type mappings like so (or something
like this):
*.jsp - application/jsp
*.jspx - application/jsp-xml
And documents of type application/jsp and application/jspx (or
whatever names we decide on) are handled appropriately
Tom Reilly wrote,
It seems to me there are a couple solutions:
1) look for jsp:root
2) use DOCTYPE
3) based it on file extension
I don't like 1 because it adds overhead to the translation
process, and you have to deal with cases like: %-- jsp:root
--%
I don't like 2 because if your
Nathan Abramson wrote,
I don't think it should be done through a server's MIME type
mapping - that means that someone writing a web app needs to
know about the mappings installed on the target server, which
makes the web app less portable.
Hmm ... not convinced.
I'd have thought that
It seems to me there are a couple solutions:
1) look for jsp:root
2) use DOCTYPE
3) based it on file extension
I don't like 1 because it adds overhead to the translation process,
and you have to deal with cases like: %-- jsp:root --%
I don't like 2 because if your JSP page is generating XML
I am sorry to start this thread here, but I believe that jasper-4.0's
behavior is in error. The behavior I think the spec calls for in
determining if a page is a JSP Document (xml jsp) or an XMl document
with JSP markup is the presence or absence of a jsp:root element.
This is further
Danno Ferrin wrote:
I am sorry to start this thread here, but I believe that jasper-4.0's
behavior is in error. The behavior I think the spec calls for in
determining if a page is a JSP Document (xml jsp) or an XMl document
with JSP markup is the presence or absence of a jsp:root element.
Thanks Craig. I was mixing two things.I got it to work by removing the ?xml
version="1.0"?
directive for now.
-- dims
--- "Craig R. McClanahan" [EMAIL PROTECTED] wrote:
Davanum Srinivas wrote:
Hi all,
Attached is a JSP Sample file which generates WML. It works with no problems
Hi all,
Attached is a JSP Sample file which generates WML. It works with no problems on
Tomcat3.1, but
fails miserably with the latest dev nightly snapshot and m4. Can someone shed light?
Thanks in advance,
dims
PS: Am not currently subscribed to the list. So please CC me at "[EMAIL
Is there a way to get the compiler to ignore the "?xml version="1.0"?" syntax?
Otherwise this means that serving any page that is XML compliant (WML, XHTML, etc) now
requires a complete
rewrite of all JSP files to run in 4.0.
Thanks.
...alex...
"Craig R. McClanahan" wrote:
Davanum
10 matches
Mail list logo
