As some other already statet this is not true. One important thing to consider is the scope of variables.
As <%@ include... %> works at compile time, the included page sees all variables that are defined before the directive in the calling page. <jsp:include... /> invokes a servlet at runtime and the included page doesn't see any java variables that are defined in the calling jsp. To enable the access to variables from the calling page they have to to be stored in one of the servlet stores (request,session,pageContext) or they must be added as parameters to the include directive. > -----Urspr�ngliche Nachricht----- > Von: Jeff Kilbride [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 11. Dezember 2001 20:19 > An: Tomcat Users List > Betreff: Re: Change an include file requires re-compiling all JSP that > include it (?) > > > If your included files don't contain any JSP code, you can use the > <jsp:include... /> directive. This directive includes the > file at request > time, rather than page translation time -- so changes to your > included file > will show up immediately. > > If your included files contain JSP code, then you're stuck > with using the > <%@ include... %> and you'll need to recompile all your JSPs > whenever the > included file changes. > > Thanks, > --jeff -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
