tags:

views:

234

answers:

2

Hi, I'm trying to implement a sitemesh decorator in my site. The example on their site has a full URI linking to their site for the taglib part of the decorator file:

<%@ taglib uri="http://www.opensymphony.com/sitemesh/decorator" prefix="decorator" %>

Does this mean that my site is reliant on being able to access that site? Because i want to deploy inside an intranet which can't access the outside world.

Thanks

+5  A: 

No, it does not. The URI declared in taglib will be resolved locally as long as it matches the URI declared in tag library descriptor (or in your web.xml, depending on what JSP version your container implements).

See Java EE tutorial for more details.

ChssPly76
When you say 'resolved locally' do you mean that if i have the TLD file in my LIB folder i'll be fine?
Chris
TLD doesn't belong in `lib`, it should either be in `/WEB-INF` or in `/META-INF` of the jar providing tags. But yes, you'll be fine.
ChssPly76
Awesome, i opened the JAR in 7-zip and it does indeed have those files in the meta-inf folder. You've set my mind at rest. Thanks
Chris
PS: The jar i looked in was 'sitemesh-2.4.2.jar'
Chris
+3  A: 

No. The URI is a Universal Resource Identifier, it is NOT a locator (URL). This means that the URI is used to uniquely identify each taglib in an internal registry of taglibs, much like a key is used to set/get values from a HashMap or Hashtable in Java.

According to the web application spec from Sun, resolving the URIs to actual tag libraries that can be loaded/called by the application takes place in the following order:

  1. Check the web.xml file for matching taglib tags that have the given URI in them and then follow the taglib-location tag to actually load the TLD.
  2. If no match with #1 was found, recursively check the META-INF directory of all the JARs in the application for TLDs that contain the URI that was specified.
Pascal Thivent
But it **is** a URL in this case :-) Depending on how your JSPs are marked up / handled it can even be used like one (for parsing XML form, for example).
ChssPly76
I have the feeling that answering this won't make things clearer :)
Pascal Thivent