1) If you keep reading, it also says: "JSP fragments that are not
complete pages should always use the .jspf suffix and should always be
placed in /WEB-INF/jspf"
2) Try requesting test2.jsp (the jsp which was the fragment earlier in
this thread) from the browser - it won't compile
3) The documentation is straightforward - look for *.jsp and compile it.
If a page is not meant to be compiled - then don't give it the jsp
suffix. When writing in C, people don't compile *.h - they compile *.c.
People don't write headers with file extensions of .c
-Tim
Martin Lambert wrote:
Hi Tim,
Thanks for you reply, it fixed the problem!
A few points though for the Tomcat people:
1)
http://java.sun.com/developer/technicalArticles/javaserverpages/code_convention/
states that: 'JSP fragments can use either .jsp or .jspf as a suffix' i.e. it
should work for .jsp includes
2) .jsp includes work in the container so why not (apparently) for the Ant task
they supply
3) As this is so useful, i.e. you can find out whether your applications JSPs
work without the servlet container, the documentation of the Ant task should be
better
4) I see the same problem with the Tomcat 4.1 libraries, so it appears to be a
long standing problem.
Don't get me wrong, I think this is a great extension to Ant that just needs
some small wrinkles ironing out to become excellent.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
