Here's one perspective based on one way I have used them. there are others.
%@ include% is useful when you know the name of the page you want to
include at coding time.
jsp:include is useful when you do not know the name of the page you want
to include until execution time, because it can
On Tue, 2004-12-07 at 11:28, Zerol Tib wrote:
Howdy,
As we know, %@ include% can include another jsp page
at translation time while jsp:include can include another
jsp at runtime. But when to use each? Could anyone give me
a scenario?
One small note to add to the other responses...
At
On Wed, Dec 08, 2004 at 12:28:35AM +0800, Zerol Tib wrote:
: As we know, %@ include% can include another jsp page
: at translation time while jsp:include can include another
: jsp at runtime. But when to use each? Could anyone give me
: a scenario?
Adding to the fine responses you've already
1/ name your JSP fragments something other than .jsp (.jspf is the
unofficial standard) such that they aren't picked up by a precompiler
If you do this, I would recommend that you do something to keep your
source from being viewed by a browser. This can be done with a mapping,
or filter that
