JspServlet
From Resin 3.0
(Difference between revisions)
(renamed tag to directive) |
|||
| Line 9: | Line 9: | ||
|- | |- | ||
||load-tld-on-init||if true, tlds are loaded when the JSP servlet is initialized||false | ||load-tld-on-init||if true, tlds are loaded when the JSP servlet is initialized||false | ||
| + | |- | ||
| + | ||page-cache-max||how many .class files to save in the load cache (3.0.19)||1024 | ||
|} | |} | ||
.tld loading can take some time on server startup because the JspServlet must scan every .jar file and classes directory looking for .tld files. This scanning is necessary in some cases for libraries like [[JSF]] because they rely on <[[listener]]> directives for their initialization. | .tld loading can take some time on server startup because the JspServlet must scan every .jar file and classes directory looking for .tld files. This scanning is necessary in some cases for libraries like [[JSF]] because they rely on <[[listener]]> directives for their initialization. | ||
Latest revision as of 20:36, 27 February 2006
The JspServlet handles processing of .jsp files. It has the following init parameters:
| param | description | default |
|---|---|---|
| xml | if true, JSP files are in XML format, i.e. like .jspx | false |
| load-tld-on-init | if true, tlds are loaded when the JSP servlet is initialized | false |
| page-cache-max | how many .class files to save in the load cache (3.0.19) | 1024 |
.tld loading can take some time on server startup because the JspServlet must scan every .jar file and classes directory looking for .tld files. This scanning is necessary in some cases for libraries like JSF because they rely on <listener> directives for their initialization.
