David, >From specification:
--------- (7.3.2) A URI in a taglib directive is mapped into a context relative path (as discussed in Section JSP.2.2.1). The context relative path is a URL without a protocol and host components that starts with "/" and is called the TLD resource path. The TLD resource path is interpreted relative to the root of the webapplication and should resolve to a TLD file directly, or to a JAR file that has a (2.2.1) A context-relative path is a path that starts with a "/". It is to be interpreted as relative to the application to which the JSP page belongs, that is to say that its servletContext object provides the base context URL. A page relative path is a path that does not start with a "/". It is to be interpreted as relative to the current JSP page or the current JSP file -------- The path you've specified is not a context-relative one. It's a page relative. So it should be interpred relative to the curretn JSP. -- Best regards, Mike Aizatsky. ------------------------------ JetBrains, Inc / IntelliJ Software http://www.intellij.com "Develop with pleasure!" "David Smiley" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > If the taglib URI appears to be a relative file path, i.e. > "WEB-INF/foo.tld", then it is considered relative to the web > application, NOT the current file. See section 7.3.2 of the JSP spec 1.2. > > ~ David Smiley > _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
