Hello Arron,
There are some underground features...
With static include we have one servlet for every page and for dynamic
include we have one servlet plus additional servlets for every
include. Every include page can be used in a number of pages so this
code will processed by JIT as common used
Hi all,
I tend to think that
%@ include file=my_page.jsp % is bad,
%jsp: include page=my_page.jsp % is best.
Any opinions on this?
If you change an included file I assume all the jsp's that access it are recompiled
next time they
are used (or can be manually recompiled). Which could be very
Actually... for performance, the first one is best. Why?... as when the
main page is compiled, the files included by this method are included as
if they were written in the one file, and then compiled. If a change is
made to the include, it wont be picked up unless the main page is
Hi -
This is really more of a JSP question, but since it involves struts
tags I figured I'd give it a shot here. I have a page which contains a
form built using the html:form taglib. Based on the users selection from
that form, I go off and do some processing and redirect the user back to
the
The type of include you're using here is a dynamic include. Meaning that
the page to be included isn't simply added, it's compiled into its own
servlet, and the page's context is passed to the included servlet. For
the tags to work in the included servlet, they need all the taglib
imports
5 matches
Mail list logo
