Submitted by heartin on Fri, 09/18/2015 - 14:06
JSPs are actually servlets. Container will convert all jsp files as servlets before executing it. By default, the JSP is compiled into a servlet and then loaded the first time it is accessed. This might cause a small delay for the first request, but there won’t be any delay in subsequent requests. You may also precompile JSPs before adding them into JARs. Certain application servers might even provide tools for doing so.
Submitted by heartin on Fri, 09/18/2015 - 06:17
I can suppress direct access to a JSP file and want users to go only through a registered name and a servlet mapping in web.xml. I can place the JSP page under WEB- INF and configure it in the web.xml file.
Submitted by heartin on Sat, 04/11/2015 - 22:13
JSP elements can be mainly divided into 3 categories:
Submitted by heartin on Sat, 04/11/2015 - 22:11
JSPs are actually servlets, as you have already seen. Container will convert all jsp files into servlets before executing them. JSPs just provide an easy way to create components containing non-java code.
Once a JSP page is created and deployed, container will do some life cycle events, which also includes calling some of its methods similar to servlet life cycle events.
Submitted by heartin on Fri, 04/10/2015 - 13:17