>>>>> "David" == David Graham <[EMAIL PROTECTED]> writes:
>> From: [EMAIL PROTECTED] (David M. Karr)
>> Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
>> To: [EMAIL PROTECTED]
>> Subject: Re: cvs commit: jakarta-struts/doc/userGuide struts-bean.xml
>> struts-html.xml struts-logic.xml struts-nested.xml struts-template.xml (fwd)
>> If you use that pattern, you probably want to consider changing your extent to
>> ".jspf". Some IDEs aggressively compile all ".jsp" files, but files which are
>> specifically included by an include directive often will not compile as a
>> standalone JSP file.
David> I'm not sure I see the problem here. The taglibs.jsp file is a valid jsp
file
David> so it will compile. My IDE doesn't compile jsps anyway, the container does.
David> What am I missing?
Nothing. I said "often", not "always". If your file included by an include
directive is a valid standalone JSP page, then it's fine. However, if you
architect a set of pages by using include directives to include JSP fragments,
then it's likely that one or more of them would not be valid standalone JSP
pages. If you use an IDE that doesn't compile JSPs, then you're also fine.
Other IDEs take a more "hands-on" approach. It's just something to be aware
of.
--
===================================================================
David M. Karr ; Java/J2EE/XML/Unix/C++
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
