On Sun, 29 Jun 2003, Michael Duffy wrote: > Actually, step 3. is unnecessary. When you create the JAR file for > your handler, the TLD file goes inside it. It's already got the URI > string you should use in your JSP. When the JSP compiler goes looking > for your TLD, it'll find it in the JAR because it's already in the > CLASSPATH.
Indeed, under JSP 1.2, the <taglib> element is unnecessary. As for duplicating the JAR files for each application, it's simply the cost -- and an exceedingly minor one in any reasonable environment -- of appropriate architecture. The advantages of including JAR files with an individual application include - a clear statement of the dependencies of the application and the ability to easily WAR it up and redeploy elsewhere - automatic detection of the JAR files' taglibs - isolation of 'static' data from other applications because a classloader specific to the web application loads the JAR files' classes; this can be important for security and for troubleshooting Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
