| |
|
| java.lang.Object org.mortbay.jetty.webapp.TagLibConfiguration
All known Subclasses: org.mortbay.jetty.plugin.Jetty6MavenTagLibConfiguration,
TagLibConfiguration | public class TagLibConfiguration implements Configuration(Code) | | TagLibConfiguration.
The class searches for TLD descriptors found in web.xml, in WEB-INF/*.tld files of the web app
or *.tld files withing jars found in WEB-INF/lib of the webapp. Any listeners defined in these
tld's are added to the context.
<bile>This is total rubbish special case for JSPs! If there was a general use-case for web app
frameworks to register listeners directly, then a generic mechanism could have been added to the servlet
spec. Instead some special purpose JSP support is required that breaks all sorts of encapsualtion rules as
the servlet container must go searching for and then parsing the descriptors for one particular framework.
It only appears to be used by JSF, which is being developed by the same developer who implemented this
feature in the first place!
</bile>
author: gregw |
configureClassLoader | public void configureClassLoader() throws Exception(Code) | | |
getServerTagLibClasses | public String[] getServerTagLibClasses()(Code) | | |
setServerTagLibClasses | public void setServerTagLibClasses(String[] serverTagLibClasses)(Code) | | Parameters: serverTagLibClasses - An array of class names. The jars that these classes are loaded from will be examined for TLD files (even if these jars are on the server or system classpath). |
|
|
|