Dave is correct since Servlet 2.3/JSP 1.2 TLD files no longer have to be specified in the web.xml - they can be auto-discovered if they're in the web applications "resource path" which includes the META-INF section of jar files - Struts ships the TLDs in its jars so you don't have to specify this. This mechanism is documented in Section "JSP.7.3.2 TLD resource path" of the JSP 1.2 Specification.
Also documented in section 5.4.3.1 Configure the Struts JSP Tag Libraries (Servlet 2.3/2.4) in the Struts User Guide: http://struts.apache.org/1.x/userGuide/configuration.html Niall On 4/19/07, Crawford, Preston <[EMAIL PROTECTED]> wrote:
That's my impression, the part about not being able to find it locally. Part of what I was thinking of doing is not having the tld's locally available. But it occurs to me that then it might spin out to the Interwebs whenever it compiles a JSP page. Trying to find a reference on this to get a definitive answer. I'm trying to make it cleaner this time. Preston -----Original Message----- From: Dave Newton [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 3:44 PM To: Struts Users Mailing List Subject: RE: [S1] The proper way to define taglibs in a jsp file --- "Crawford, Preston" wrote: > Oh, I just remembered something. There might be overhead/risk to jsps > hitting the dtd on the Internet > vs. the local tld, no? I'm not sure that that's what the URI really does; they *look* like URLs but I think they're just look-up values to find the corresponding TLD. (This has always been a somewhat murky area for me, because I've never really cared, but I think the only time it spins out to the 'net is if it can't find the TLD locally... it might depend on the IDE and/or server, though.) d.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
