<!--
The servlet element contains the declarative data of a
servlet. If a jsp-file is specified and the load-on-startup element is
-present, then the JSP should be precompiled and loaded.
+present, then the JSP should be pre-compiled and loaded.
-->
<!ELEMENT servlet (icon?, servlet-name, display-name?, description?,
<!--
The load-on-startup element indicates that this servlet should be
-loaded on the startup of the web application. The optional contents of
+loaded on the start-up of the web application. The optional contents of
these element must be a positive integer indicating the order in which
the servlet should be loaded. Lower integers are loaded before higher
integers. If no value is specified, or if the value specified is not a
<!--
The ID mechanism is to allow tools to easily make tool-specific
references to the elements of the deployment descriptor. This allows
-tools that produce additional deployment information (i.e information
+tools that produce additional deployment information (i.e. information
beyond the standard deployment descriptor information) to store the
non-standard information in a separate file, and easily refer from
these tools-specific files to the information in the standard web-app
env-entry-type)>
<!--
-The env-entry-name element contains the name of a web applications's
+The env-entry-name element contains the name of a web application's
environment entry. The name is a JNDI name relative to the
java:comp/env context. The name must be unique within a web application.
or on url-pattern for each filter-mapping element, depending on which
style is used. The order in which filters are invoked is the order in
which filter-mapping declarations that match a request URI for a
-servlet appear in the list of filter-mapping elements.The filter-name
+servlet appear in the list of filter-mapping elements. The filter-name
value must be the value of the <filter-name> sub-elements of one of the
<filter> declarations in the deployment descriptor.
<!--
The load-on-startup element indicates that this servlet should be
-loaded (instantiated and have its init() called) on the startup
+loaded (instantiated and have its init() called) on the start-up
of the web application. The optional contents of
these element must be an integer indicating the order in which
the servlet should be loaded. If the value is a negative integer,
file must not contain multiple elements of session-config,
jsp-config, and login-config. When there are multiple elements of
welcome-file-list or locale-encoding-mapping-list, the container
- must concatinate the element contents. The multiple occurrence
+ must concatenate the element contents. The multiple occurrence
of the element distributable is redundant and the container
treats that case exactly in the same way when there is only
one distributable.
element, depending on which style is used. The order in
which filters are invoked is the order in which
filter-mapping declarations that match a request URI for a
- servlet appear in the list of filter-mapping elements.The
+ servlet appear in the list of filter-mapping elements. The
filter-name value must be the value of the filter-name
sub-elements of one of the filter declarations in the
deployment descriptor.
The servletType is used to declare a servlet.
It contains the declarative data of a
servlet. If a jsp-file is specified and the load-on-startup
- element is present, then the JSP should be precompiled and
+ element is present, then the JSP should be pre-compiled and
loaded.
Used in: web-app
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
- its init() called) on the startup of the web
+ its init() called) on the start-up of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
session-config, jsp-config, and login-config. When there
are multiple elements of welcome-file-list or
locale-encoding-mapping-list, the container must
- concatenate the element contents. The multiple occurence
+ concatenate the element contents. The multiple occurrence
of the element distributable is redundant and the
container treats that case exactly in the same way when
there is only one distributable.
which filters are invoked is the order in which
filter-mapping declarations that match a request URI for
a servlet appear in the list of filter-mapping
- elements.The filter-name value must be the value of the
+ elements. The filter-name value must be the value of the
filter-name sub-elements of one of the filter
declarations in the deployment descriptor.
</xsd:documentation>
<xsd:documentation>
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
- its init() called) on the startup of the web
+ its init() called) on the start-up of the web
application. The optional contents of these
element must be an integer indicating the order
in which the servlet should be loaded. If the