Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4848517B.3000002@seatadvisor.com>
Date: Thu, 05 Jun 2008 13:50:03 -0700
From: Bill Davidson <billd@seatadvisor.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: <jsp:include> versus <% include %>
References: <f5af14000806030952i20b6d4bau4315687ae82c5588@mail.gmail.com>
 <913936E7-51AC-49A5-B4E5-A15663E90B59@tchijov.com>
 <48484FB2.1080006@seatadvisor.com>
In-Reply-To: <48484FB2.1080006@seatadvisor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bill Davidson wrote:
> <%@include ... %> happens at compile time.  That is, only the first
> time the JSP page is loaded.  The included data ends up in the compiled
> servlet.  It has been my experience that you can have other JSP 
> directives
> in the included file and they will be properly interpreted.
I forgot to add, if the included file changes, then the JSP will not reflect
that change unless you force it to be recompiled.
> <jsp:include ... /> happens at run time, every time the JSP page is
> loaded.  The included data is not compiled into the servlet, rather
> the generated servlet has code to re-read the included file every time
> it runs.  It has been my experience that JSP tags in the included file
> will not be interpreted so you're pretty much limited to HTML (or 
> whatever
> your final output format to the user agent is) in the included file.
In this case, if the included file changes, the JSP should reflect the
changes on the next page load, without a recompile.


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org