Oh, I just remembered something. There might be overhead/risk to jsps hitting the dtd on the Internet vs. the local tld, no?
Preston -----Original Message----- From: Crawford, Preston [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 3:27 PM To: 'Struts Users Mailing List' Subject: RE: [S1] The proper way to define taglibs in a jsp file Yeah, actually I was the guy (way back when) who helped define those TLDs in the web.xml. Now I'm back on contract and want to clean up my work. I would like to just refer to the dtd in the URI and forgo having the TLDs located in the build process. We use WebSphere 6.1, so this should be fine. Preston -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Benedict Sent: Thursday, April 19, 2007 3:20 PM To: Struts Users Mailing List Subject: Re: [S1] The proper way to define taglibs in a jsp file On 4/19/07, Crawford, Preston <[EMAIL PROTECTED]> wrote: > > So I'm helping my company clean up some JSP files, things like that > and I'm seeing declarations like this. > > <%@ taglib uri="/bean" prefix="bean" %> <%@ taglib uri="/html" > prefix="html" %> > > The ability to automatically find TLD files is a feature of the web container, not of Struts. If you're using a 2.3 container, the tag libraries will be found under the URI that's specified in their DTDs. While I may be wrong, I think between Struts 1.2.9 and 1.3.5, Struts switched from jakarta.apache.org to struts.apache.org and thus you find different URIs between versions. As for the URIs you see above, those are from developers defining the location of the TLD explicitly in their web.xml Paul CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
