Len, agreed to the most of what you said, however, I still do not see why JSPs have to go (or should go) into WEB-INF.
Even in this tutorial (linked directly fom java.sun.com) http://www.apl.jhu.edu/~hall/java/Servlet-Tutorial/ the JSP-file goes directly into the app-dir where also the static HTML resides. On Mon, Mar 9, 2009 at 8:23 PM, Len Popp <len.p...@gmail.com> wrote: > What I mean is, clients *never* access a .jsp file by URL, e.g. > "http://www.example.com/app/foo.jsp";. This is definately wrong. When you call a jsp directly from within a Servlet-Container, the file gets compiled to a servlet and the output of the servlet is displayed. I've googled for this issue, and what I find, is, that some frameworks recommend putting JSPs into WEB-INF/jsp. However, I also found the statement that not all Servlet-Containers are supporting it. Now I'm wondering ("Mr. Servlet-Spec" Chuck, you comment on that one): Is this directory-structure really part of the specs? I just found this recomendation in context with frameworks like Struts or Spring. I'm wondering: How does Tomcat find a JSP within WEB-INF/jsp? Do I have to specify it in the deployment-descriptor? Rgds Gregor -- just because your paranoid, doesn't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
