Sorry, this is not true.  You can have JSP code in a file included through
<jsp:include ... />: the only difference between the two approaches is that
<jsp:include ... /> executes at runtime, whereas <%@include ... %> executes
at compile time.  Thus, <%@include ... /> can be seen as somewhat analogous
to a C #include statement, whereas <jsp:include ... /> is more like a Java
import statement.  When the server executes a <jsp:include ... /> it
dispatches a request to the indicated URL and includes the response from
that request in the document being served.  A <%@include ... %>, in
contrast, simply dumps in all of the (compiled) JSP code from the included
file into your compiled JSP servlet (i.e. there is no separate request
dispatching going on).

You will need to recompile all JSP's using a <%@include %> when the included
file is changed, but the same is not true of <jsp:include ... />'d files.

--Chris

-----Original Message-----
From: Jeff Kilbride [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 11, 2001 11:19 AM
To: Tomcat Users List
Subject: 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

----- Original Message -----
From: "Scott Hodson" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 11, 2001 10:58 AM
Subject: RE: Change an include file requires re-compiling all JSP that
include it (?)


> 1) Where do they go?  I don't see them anywhere under my webapp's folder
(I
> thought they go in WEB-INF/classes but they're not there)
>
> 2) Blech, that's what I do now.  If I have 100 JSP files all including the
> same header file I'm doomed!
>
> -----Original Message-----
> From: James Chuang [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 11, 2001 10:06 AM
> To: Tomcat Users List
> Subject: Re: Change an include file requires re-compiling all JSP that
> include it (?)
>
>
> A couple of things you can do, both would be easier than resaving all the
> JSPs
>
> 1. Delete the generated class files...
>
> 2. Touch the JSP files.
>
>
> ----- Original Message -----
> From: "Scott Hodson" <[EMAIL PROTECTED]>
> To: "Tomcat User" <[EMAIL PROTECTED]>
> Sent: Tuesday, December 11, 2001 10:00 AM
> Subject: Change an include file requires re-compiling all JSP that include
> it (?)
>
>
> > I come from an ASP background where we would frequently change include
> files
> > and see the results immediately.  However, in JSP, since JSP pages are
> > compiled into servlet classes, if I change an include file the JSP file
> > including it won't get re-compiled because the JSP hasn't changed, just
> the
> > include file.  Even if I restart Tomcat it still won't recompile the
JSPs.
> > So for now every time I make a change to an include file I have to
re-save
> > all of my JSPs so Tomcat forces a recompile.  That's a big pain.
> >
> > Can somebody help me out here?  Is there a way to force re-compilation
of
> > JSPs if the files they include ever change?
> > ___________________________
> >
> > Scott Hodson
> > (949) 709-4496 office
> > (949) 709-3890 fax
> > [EMAIL PROTECTED]
> > http://www.ubero.com
> >
> >
> >
>
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to