5.3.2
Translation Time Class Loader
The set of classes available at translation time is the same as available at runtime: the classes 
in the underlying Java platform, those in the JSP container, and those in the class files in 
WEB INF/classes
, in the JAR files in 
WEB INF/lib
, and, indirectly through the use of 
the 
class path
 attribute in the 
META INF/MANIFEST
 file of these JAR files.
5.3.3
Assembling a Web Application
As part of the process of assembling a Web Application together, the Application Assembler 
will create a 
WEB INF/ 
directory, with appropriate 
lib/
 and 
classes/
 subdirectories, 
place JSP pages, Servlet classes, auxiliary classes, and tag libraries in the proper places and 
then create a 
WEB INF/web.xml
 that ties everything together.
Tag libraries that have been delivered in the standard format can be dropped directly into 
WEB INF/lib
.  The assembler may create 
taglib
 entries in 
web.xml
 for each of the 
libraries that are to be used.
Part of the assembly (and later the deployment) may create and/or change information that 
customizes a tag library; see Section 5.8.3.
5.3.4
Well Known URIs
A JSP container may "know of" some specific URIs and may provide alternate 
implementations for the tag libraries described by these URIs, but the user must see the same 
behavior as that described by the, required, portable tag library description described by the 
URI.
A JSP container must always use the mapping specified for a URI in the web.xml 
deployment descriptor if present.  If the deployer wants to use the platform specific 
implementation of the well known URI, the mapping for that URI should be removed at 
deployment time.
If there is no mapping for a given URI and the URI is not well known to the JSP container, 
a translation time error will occur.
There is no guarantee that this  well known URI  mechanism will be preserved in later 
releases of the JSP specification.  As experience accumulates on how to use tag extensions, 
the JSP specification may incorporate new functionality that will make the  well known 
URI  mechanism unnecessary; at that point it may be removed.
95
JavaServer Pages 1.1 Specification  
November 30, 1999




JSP Web Hosting JavaServer Pages Specifications JSP Hosting




 
TotalRoute.net Business web hosting division of Vision Web Hosting Inc. All rights reserved.