The taglib URI does not necessarily point to a real web resource. The taglib URI must match the <uri> declaration in any of the .tld files that is present in the classpath.
Given this fact, two reasons are possible:
- The TLD file (at least the JAR file containing it) is not at all in the classpath.
- The TLD file declared a different URI.
I have no experience with JodaTime tags, so I cannot say from above if this incorrect behavior is incorrect. The best I can offer is to extract the JAR file containing the TLD files using some ZIP tool and then read the actual <uri> in the .tld file in the META-INF JAR folder.
If this turns out to be the same, you are likely to have a problem with the classpath or build options. Are JAR files really present in the extended WAR file in a running webapp environment?
Unrelated to a specific issue, Servlet 2.4 implies JSP 2.0, not JSP 2.1. Also, why are you using Servlet 2.4 instead of 2.5 or even 3.0? Glassfish 3 supports servlet 3.0.
source share