1 |
<?xml version="1.0" encoding="UTF-8"?>
|
2 |
<!--
|
3 |
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
|
4 |
|
5 |
Copyright 2000-2007 Sun Microsystems, Inc. All rights reserved.
|
6 |
|
7 |
The contents of this file are subject to the terms of either the GNU
|
8 |
General Public License Version 2 only ("GPL") or the Common Development
|
9 |
and Distribution License("CDDL") (collectively, the "License"). You
|
10 |
may not use this file except in compliance with the License. You can obtain
|
11 |
a copy of the License at https://glassfish.dev.java.net/public/CDDL+GPL.html
|
12 |
or glassfish/bootstrap/legal/LICENSE.txt. See the License for the specific
|
13 |
language governing permissions and limitations under the License.
|
14 |
|
15 |
When distributing the software, include this License Header Notice in each
|
16 |
file and include the License file at glassfish/bootstrap/legal/LICENSE.txt.
|
17 |
Sun designates this particular file as subject to the "Classpath" exception
|
18 |
as provided by Sun in the GPL Version 2 section of the License file that
|
19 |
accompanied this code. If applicable, add the following below the License
|
20 |
Header, with the fields enclosed by brackets [] replaced by your own
|
21 |
identifying information: "Portions Copyrighted [year]
|
22 |
[name of copyright owner]"
|
23 |
|
24 |
Contributor(s):
|
25 |
|
26 |
If you wish your version of this file to be governed by only the CDDL or
|
27 |
only the GPL Version 2, indicate your decision by adding "[Contributor]
|
28 |
elects to include this software in this distribution under the [CDDL or GPL
|
29 |
Version 2] license." If you don't indicate a single choice of license, a
|
30 |
recipient has the option to distribute your version of this file under
|
31 |
either the CDDL, the GPL Version 2 or to extend the choice of license to
|
32 |
its licensees as provided above. However, if you add GPL Version 2 code
|
33 |
and therefore, elected the GPL Version 2 license, then the option applies
|
34 |
only if the new code is made subject to such option by the copyright
|
35 |
holder.
|
36 |
-->
|
37 |
<!--
|
38 |
This is the XML DTD for the Servlet 2.3 deployment descriptor.
|
39 |
All Servlet 2.3 deployment descriptors must include a DOCTYPE
|
40 |
of the following form:
|
41 |
|
42 |
<!DOCTYPE web-app PUBLIC
|
43 |
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
|
44 |
"http://java.sun.com/dtd/web-app_2_3.dtd">
|
45 |
|
46 |
-->
|
47 |
<!--
|
48 |
The following conventions apply to all J2EE deployment descriptor
|
49 |
elements unless indicated otherwise.
|
50 |
|
51 |
- In elements that contain PCDATA, leading and trailing whitespace
|
52 |
in the data may be ignored.
|
53 |
|
54 |
- In elements whose value is an "enumerated type", the value is
|
55 |
case sensitive.
|
56 |
|
57 |
- In elements that specify a pathname to a file within the same
|
58 |
JAR file, relative filenames (i.e., those not starting with "/")
|
59 |
are considered relative to the root of the JAR file's namespace.
|
60 |
Absolute filenames (i.e., those starting with "/") also specify
|
61 |
names in the root of the JAR file's namespace. In general, relative
|
62 |
names are preferred. The exception is .war files where absolute
|
63 |
names are preferred for consistency with the servlet API.
|
64 |
-->
|
65 |
<!--
|
66 |
The web-app element is the root of the deployment descriptor for
|
67 |
a web application.
|
68 |
-->
|
69 |
<!--
|
70 |
The auth-constraint element indicates the user roles that should
|
71 |
be permitted access to this resource collection. The role-name
|
72 |
used here must either correspond to the role-name of one of the
|
73 |
security-role elements defined for this web application, or be
|
74 |
the specially reserved role-name "*" that is a compact syntax for
|
75 |
indicating all roles in the web application. If both "*" and
|
76 |
rolenames appear, the container interprets this as all roles.
|
77 |
If no roles are defined, no user is allowed access to the portion of
|
78 |
the web application described by the containing security-constraint.
|
79 |
The container matches role names case sensitively when determining
|
80 |
access.
|
81 |
|
82 |
|
83 |
Used in: security-constraint
|
84 |
-->
|
85 |
<!--
|
86 |
The auth-method element is used to configure the authentication
|
87 |
mechanism for the web application. As a prerequisite to gaining access to any web resources which are protected by an authorization
|
88 |
constraint, a user must have authenticated using the configured
|
89 |
mechanism. Legal values for this element are "BASIC", "DIGEST",
|
90 |
"FORM", or "CLIENT-CERT".
|
91 |
|
92 |
Used in: login-config
|
93 |
-->
|
94 |
<!--
|
95 |
The context-param element contains the declaration of a web
|
96 |
application's servlet context initialization parameters.
|
97 |
|
98 |
Used in: web-app
|
99 |
-->
|
100 |
<!--
|
101 |
The description element is used to provide text describing the parent
|
102 |
element. The description element should include any information that
|
103 |
the web application war file producer wants to provide to the consumer of
|
104 |
the web application war file (i.e., to the Deployer). Typically, the tools
|
105 |
used by the web application war file consumer will display the description
|
106 |
when processing the parent element that contains the description.
|
107 |
|
108 |
Used in: auth-constraint, context-param, ejb-local-ref, ejb-ref,
|
109 |
env-entry, filter, init-param, resource-env-ref, resource-ref, run-as,
|
110 |
security-role, security-role-ref, servlet, user-data-constraint,
|
111 |
web-app, web-resource-collection
|
112 |
-->
|
113 |
<!--
|
114 |
The display-name element contains a short name that is intended to be
|
115 |
displayed by tools. The display name need not be unique.
|
116 |
|
117 |
Used in: filter, security-constraint, servlet, web-app
|
118 |
|
119 |
Example:
|
120 |
|
121 |
<display-name>Employee Self Service</display-name>
|
122 |
-->
|
123 |
<!--
|
124 |
The distributable element, by its presence in a web application
|
125 |
deployment descriptor, indicates that this web application is
|
126 |
programmed appropriately to be deployed into a distributed servlet
|
127 |
container
|
128 |
|
129 |
Used in: web-app
|
130 |
-->
|
131 |
<!--
|
132 |
The ejb-link element is used in the ejb-ref or ejb-local-ref
|
133 |
elements to specify that an EJB reference is linked to an
|
134 |
enterprise bean.
|
135 |
|
136 |
The name in the ejb-link element is composed of a
|
137 |
path name specifying the ejb-jar containing the referenced enterprise
|
138 |
bean with the ejb-name of the target bean appended and separated from
|
139 |
the path name by "#". The path name is relative to the war file
|
140 |
containing the web application that is referencing the enterprise bean.
|
141 |
This allows multiple enterprise beans with the same ejb-name to be
|
142 |
uniquely identified.
|
143 |
|
144 |
Used in: ejb-local-ref, ejb-ref
|
145 |
|
146 |
Examples:
|
147 |
|
148 |
<ejb-link>EmployeeRecord</ejb-link>
|
149 |
|
150 |
<ejb-link>../products/product.jar#ProductEJB</ejb-link>
|
151 |
|
152 |
-->
|
153 |
<!--
|
154 |
The ejb-local-ref element is used for the declaration of a reference to
|
155 |
an enterprise bean's local home. The declaration consists of:
|
156 |
|
157 |
- an optional description
|
158 |
- the EJB reference name used in the code of the web application
|
159 |
that's referencing the enterprise bean
|
160 |
- the expected type of the referenced enterprise bean
|
161 |
- the expected local home and local interfaces of the referenced
|
162 |
enterprise bean
|
163 |
- optional ejb-link information, used to specify the referenced
|
164 |
enterprise bean
|
165 |
|
166 |
Used in: web-app
|
167 |
-->
|
168 |
<!--
|
169 |
The ejb-ref element is used for the declaration of a reference to
|
170 |
an enterprise bean's home. The declaration consists of:
|
171 |
|
172 |
- an optional description
|
173 |
- the EJB reference name used in the code of
|
174 |
the web application that's referencing the enterprise bean
|
175 |
- the expected type of the referenced enterprise bean
|
176 |
- the expected home and remote interfaces of the referenced
|
177 |
enterprise bean
|
178 |
- optional ejb-link information, used to specify the referenced
|
179 |
enterprise bean
|
180 |
|
181 |
Used in: web-app
|
182 |
-->
|
183 |
<!--
|
184 |
The ejb-ref-name element contains the name of an EJB reference. The
|
185 |
EJB reference is an entry in the web application's environment and is
|
186 |
relative to the java:comp/env context. The name must be unique
|
187 |
within the web application.
|
188 |
|
189 |
It is recommended that name is prefixed with "ejb/".
|
190 |
|
191 |
Used in: ejb-local-ref, ejb-ref
|
192 |
|
193 |
Example:
|
194 |
|
195 |
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
|
196 |
-->
|
197 |
<!--
|
198 |
The ejb-ref-type element contains the expected type of the
|
199 |
referenced enterprise bean.
|
200 |
|
201 |
The ejb-ref-type element must be one of the following:
|
202 |
|
203 |
<ejb-ref-type>Entity</ejb-ref-type>
|
204 |
<ejb-ref-type>Session</ejb-ref-type>
|
205 |
|
206 |
Used in: ejb-local-ref, ejb-ref
|
207 |
-->
|
208 |
<!--
|
209 |
The env-entry element contains the declaration of a web application's
|
210 |
environment entry. The declaration consists of an optional
|
211 |
description, the name of the environment entry, and an optional
|
212 |
value. If a value is not specified, one must be supplied
|
213 |
during deployment.
|
214 |
-->
|
215 |
<!--
|
216 |
The env-entry-name element contains the name of a web applications's
|
217 |
environment entry. The name is a JNDI name relative to the
|
218 |
java:comp/env context. The name must be unique within a web application.
|
219 |
|
220 |
Example:
|
221 |
|
222 |
<env-entry-name>minAmount</env-entry-name>
|
223 |
|
224 |
Used in: env-entry
|
225 |
-->
|
226 |
<!--
|
227 |
The env-entry-type element contains the fully-qualified Java type of
|
228 |
the environment entry value that is expected by the web application's
|
229 |
code.
|
230 |
|
231 |
The following are the legal values of env-entry-type:
|
232 |
|
233 |
java.lang.Boolean
|
234 |
java.lang.Byte
|
235 |
java.lang.Character
|
236 |
java.lang.String
|
237 |
java.lang.Short
|
238 |
java.lang.Integer
|
239 |
java.lang.Long
|
240 |
java.lang.Float
|
241 |
java.lang.Double
|
242 |
|
243 |
Used in: env-entry
|
244 |
-->
|
245 |
<!--
|
246 |
The env-entry-value element contains the value of a web application's
|
247 |
environment entry. The value must be a String that is valid for the
|
248 |
constructor of the specified type that takes a single String
|
249 |
parameter, or for java.lang.Character, a single character.
|
250 |
|
251 |
Example:
|
252 |
|
253 |
<env-entry-value>100.00</env-entry-value>
|
254 |
|
255 |
Used in: env-entry
|
256 |
-->
|
257 |
<!--
|
258 |
The error-code contains an HTTP error code, ex: 404
|
259 |
|
260 |
Used in: error-page
|
261 |
-->
|
262 |
<!--
|
263 |
The error-page element contains a mapping between an error code
|
264 |
or exception type to the path of a resource in the web application
|
265 |
|
266 |
Used in: web-app
|
267 |
-->
|
268 |
<!--
|
269 |
The exception type contains a fully qualified class name of a
|
270 |
Java exception type.
|
271 |
|
272 |
Used in: error-page
|
273 |
-->
|
274 |
<!--
|
275 |
The extension element contains a string describing an
|
276 |
extension. example: "txt"
|
277 |
|
278 |
Used in: mime-mapping
|
279 |
-->
|
280 |
<!--
|
281 |
Declares a filter in the web application. The filter is mapped to
|
282 |
either a servlet or a URL pattern in the filter-mapping element, using
|
283 |
the filter-name value to reference. Filters can access the
|
284 |
initialization parameters declared in the deployment descriptor at
|
285 |
runtime via the FilterConfig interface.
|
286 |
|
287 |
Used in: web-app
|
288 |
-->
|
289 |
<!--
|
290 |
The fully qualified classname of the filter.
|
291 |
|
292 |
Used in: filter
|
293 |
-->
|
294 |
<!--
|
295 |
Declaration of the filter mappings in this web application. The
|
296 |
container uses the filter-mapping declarations to decide which filters
|
297 |
to apply to a request, and in what order. The container matches the
|
298 |
request URI to a Servlet in the normal way. To determine which filters
|
299 |
to apply it matches filter-mapping declarations either on servlet-name,
|
300 |
or on url-pattern for each filter-mapping element, depending on which
|
301 |
style is used. The order in which filters are invoked is the order in
|
302 |
which filter-mapping declarations that match a request URI for a
|
303 |
servlet appear in the list of filter-mapping elements.The filter-name
|
304 |
value must be the value of the <filter-name> sub-elements of one of the
|
305 |
<filter> declarations in the deployment descriptor.
|
306 |
|
307 |
Used in: web-app
|
308 |
-->
|
309 |
<!--
|
310 |
The logical name of the filter. This name is used to map the filter.
|
311 |
Each filter name is unique within the web application.
|
312 |
|
313 |
Used in: filter, filter-mapping
|
314 |
-->
|
315 |
<!--
|
316 |
The form-error-page element defines the location in the web app
|
317 |
where the error page that is displayed when login is not successful
|
318 |
can be found. The path begins with a leading / and is interpreted
|
319 |
relative to the root of the WAR.
|
320 |
|
321 |
Used in: form-login-config
|
322 |
-->
|
323 |
<!--
|
324 |
The form-login-config element specifies the login and error pages
|
325 |
that should be used in form based login. If form based authentication
|
326 |
is not used, these elements are ignored.
|
327 |
|
328 |
Used in: login-config
|
329 |
-->
|
330 |
<!--
|
331 |
The form-login-page element defines the location in the web app
|
332 |
where the page that can be used for login can be found. The path
|
333 |
begins with a leading / and is interpreted relative to the root of the WAR.
|
334 |
|
335 |
Used in: form-login-config
|
336 |
-->
|
337 |
<!--
|
338 |
The home element contains the fully-qualified name of the enterprise
|
339 |
bean's home interface.
|
340 |
|
341 |
Used in: ejb-ref
|
342 |
|
343 |
Example:
|
344 |
|
345 |
<home>com.aardvark.payroll.PayrollHome</home>
|
346 |
-->
|
347 |
<!--
|
348 |
The http-method contains an HTTP method (GET | POST |...).
|
349 |
|
350 |
Used in: web-resource-collection
|
351 |
-->
|
352 |
<!--
|
353 |
The icon element contains small-icon and large-icon elements that
|
354 |
specify the file names for small and a large GIF or JPEG icon images
|
355 |
used to represent the parent element in a GUI tool.
|
356 |
|
357 |
Used in: filter, servlet, web-app
|
358 |
-->
|
359 |
<!--
|
360 |
The init-param element contains a name/value pair as an
|
361 |
initialization param of the servlet
|
362 |
|
363 |
Used in: filter, servlet
|
364 |
-->
|
365 |
<!--
|
366 |
The jsp-file element contains the full path to a JSP file within
|
367 |
the web application beginning with a `/'.
|
368 |
|
369 |
Used in: servlet
|
370 |
-->
|
371 |
<!--
|
372 |
The large-icon element contains the name of a file
|
373 |
containing a large (32 x 32) icon image. The file
|
374 |
name is a relative path within the web application's
|
375 |
war file.
|
376 |
|
377 |
The image may be either in the JPEG or GIF format.
|
378 |
The icon can be used by tools.
|
379 |
|
380 |
Used in: icon
|
381 |
|
382 |
Example:
|
383 |
|
384 |
<large-icon>employee-service-icon32x32.jpg</large-icon>
|
385 |
-->
|
386 |
<!--
|
387 |
The listener element indicates the deployment properties for a web
|
388 |
application listener bean.
|
389 |
|
390 |
Used in: web-app
|
391 |
-->
|
392 |
<!--
|
393 |
The listener-class element declares a class in the application must be
|
394 |
registered as a web application listener bean. The value is the fully qualified classname of the listener class.
|
395 |
|
396 |
|
397 |
Used in: listener
|
398 |
-->
|
399 |
<!--
|
400 |
The load-on-startup element indicates that this servlet should be
|
401 |
loaded (instantiated and have its init() called) on the startup
|
402 |
of the web application. The optional contents of
|
403 |
these element must be an integer indicating the order in which
|
404 |
the servlet should be loaded. If the value is a negative integer,
|
405 |
or the element is not present, the container is free to load the
|
406 |
servlet whenever it chooses. If the value is a positive integer
|
407 |
or 0, the container must load and initialize the servlet as the
|
408 |
application is deployed. The container must guarantee that
|
409 |
servlets marked with lower integers are loaded before servlets
|
410 |
marked with higher integers. The container may choose the order
|
411 |
of loading of servlets with the same load-on-start-up value.
|
412 |
|
413 |
Used in: servlet
|
414 |
-->
|
415 |
<!--
|
416 |
|
417 |
The local element contains the fully-qualified name of the
|
418 |
enterprise bean's local interface.
|
419 |
|
420 |
Used in: ejb-local-ref
|
421 |
|
422 |
-->
|
423 |
<!--
|
424 |
|
425 |
The local-home element contains the fully-qualified name of the
|
426 |
enterprise bean's local home interface.
|
427 |
|
428 |
Used in: ejb-local-ref
|
429 |
-->
|
430 |
<!--
|
431 |
The location element contains the location of the resource in the web
|
432 |
application relative to the root of the web application. The value of
|
433 |
the location must have a leading `/'.
|
434 |
|
435 |
Used in: error-page
|
436 |
-->
|
437 |
<!--
|
438 |
The login-config element is used to configure the authentication
|
439 |
method that should be used, the realm name that should be used for
|
440 |
this application, and the attributes that are needed by the form login
|
441 |
mechanism.
|
442 |
|
443 |
Used in: web-app
|
444 |
-->
|
445 |
<!--
|
446 |
The mime-mapping element defines a mapping between an extension
|
447 |
and a mime type.
|
448 |
|
449 |
Used in: web-app
|
450 |
-->
|
451 |
<!--
|
452 |
The mime-type element contains a defined mime type. example:
|
453 |
"text/plain"
|
454 |
|
455 |
Used in: mime-mapping
|
456 |
-->
|
457 |
<!--
|
458 |
The param-name element contains the name of a parameter. Each parameter
|
459 |
name must be unique in the web application.
|
460 |
|
461 |
|
462 |
Used in: context-param, init-param
|
463 |
-->
|
464 |
<!--
|
465 |
The param-value element contains the value of a parameter.
|
466 |
|
467 |
Used in: context-param, init-param
|
468 |
-->
|
469 |
<!--
|
470 |
The realm name element specifies the realm name to use in HTTP
|
471 |
Basic authorization.
|
472 |
|
473 |
Used in: login-config
|
474 |
-->
|
475 |
<!--
|
476 |
The remote element contains the fully-qualified name of the enterprise
|
477 |
bean's remote interface.
|
478 |
|
479 |
Used in: ejb-ref
|
480 |
|
481 |
Example:
|
482 |
|
483 |
<remote>com.wombat.empl.EmployeeService</remote>
|
484 |
-->
|
485 |
<!--
|
486 |
The res-auth element specifies whether the web application code signs
|
487 |
on programmatically to the resource manager, or whether the Container
|
488 |
will sign on to the resource manager on behalf of the web application. In the
|
489 |
latter case, the Container uses information that is supplied by the
|
490 |
Deployer.
|
491 |
|
492 |
The value of this element must be one of the two following:
|
493 |
|
494 |
<res-auth>Application</res-auth>
|
495 |
<res-auth>Container</res-auth>
|
496 |
|
497 |
Used in: resource-ref
|
498 |
-->
|
499 |
<!--
|
500 |
The res-ref-name element specifies the name of a resource manager
|
501 |
connection factory reference. The name is a JNDI name relative to the
|
502 |
java:comp/env context. The name must be unique within a web application.
|
503 |
|
504 |
Used in: resource-ref
|
505 |
-->
|
506 |
<!--
|
507 |
The res-sharing-scope element specifies whether connections obtained
|
508 |
through the given resource manager connection factory reference can be
|
509 |
shared. The value of this element, if specified, must be one of the
|
510 |
two following:
|
511 |
|
512 |
<res-sharing-scope>Shareable</res-sharing-scope>
|
513 |
<res-sharing-scope>Unshareable</res-sharing-scope>
|
514 |
|
515 |
The default value is Shareable.
|
516 |
|
517 |
Used in: resource-ref
|
518 |
-->
|
519 |
<!--
|
520 |
The res-type element specifies the type of the data source. The type
|
521 |
is specified by the fully qualified Java language class or interface
|
522 |
expected to be implemented by the data source.
|
523 |
|
524 |
Used in: resource-ref
|
525 |
-->
|
526 |
<!--
|
527 |
The resource-env-ref element contains a declaration of a web application's
|
528 |
reference to an administered object associated with a resource
|
529 |
in the web application's environment. It consists of an optional
|
530 |
description, the resource environment reference name, and an
|
531 |
indication of the resource environment reference type expected by
|
532 |
the web application code.
|
533 |
|
534 |
Used in: web-app
|
535 |
|
536 |
Example:
|
537 |
|
538 |
<resource-env-ref>
|
539 |
<resource-env-ref-name>jms/StockQueue</resource-env-ref-name>
|
540 |
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
|
541 |
</resource-env-ref>
|
542 |
-->
|
543 |
<!--
|
544 |
The resource-env-ref-name element specifies the name of a resource
|
545 |
environment reference; its value is the environment entry name used in
|
546 |
the web application code. The name is a JNDI name relative to the
|
547 |
java:comp/env context and must be unique within a web application.
|
548 |
|
549 |
Used in: resource-env-ref
|
550 |
-->
|
551 |
<!--
|
552 |
The resource-env-ref-type element specifies the type of a resource
|
553 |
environment reference. It is the fully qualified name of a Java
|
554 |
language class or interface.
|
555 |
|
556 |
Used in: resource-env-ref
|
557 |
-->
|
558 |
<!--
|
559 |
The resource-ref element contains a declaration of a web application's
|
560 |
reference to an external resource. It consists of an optional
|
561 |
description, the resource manager connection factory reference name,
|
562 |
the indication of the resource manager connection factory type
|
563 |
expected by the web application code, the type of authentication
|
564 |
(Application or Container), and an optional specification of the
|
565 |
shareability of connections obtained from the resource (Shareable or
|
566 |
Unshareable).
|
567 |
|
568 |
Used in: web-app
|
569 |
|
570 |
Example:
|
571 |
|
572 |
<resource-ref>
|
573 |
<res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
|
574 |
<res-type>javax.sql.DataSource</res-type>
|
575 |
<res-auth>Container</res-auth>
|
576 |
<res-sharing-scope>Shareable</res-sharing-scope>
|
577 |
</resource-ref>
|
578 |
-->
|
579 |
<!--
|
580 |
The role-link element is a reference to a defined security role. The
|
581 |
role-link element must contain the name of one of the security roles
|
582 |
defined in the security-role elements.
|
583 |
|
584 |
Used in: security-role-ref
|
585 |
-->
|
586 |
<!--
|
587 |
The role-name element contains the name of a security role.
|
588 |
|
589 |
The name must conform to the lexical rules for an NMTOKEN.
|
590 |
|
591 |
Used in: auth-constraint, run-as, security-role, security-role-ref
|
592 |
-->
|
593 |
<!--
|
594 |
The run-as element specifies the run-as identity to be used for the
|
595 |
execution of the web application. It contains an optional description, and
|
596 |
the name of a security role.
|
597 |
|
598 |
Used in: servlet
|
599 |
-->
|
600 |
<!--
|
601 |
The security-constraint element is used to associate security
|
602 |
constraints with one or more web resource collections
|
603 |
|
604 |
Used in: web-app
|
605 |
-->
|
606 |
<!--
|
607 |
The security-role element contains the definition of a security
|
608 |
role. The definition consists of an optional description of the
|
609 |
security role, and the security role name.
|
610 |
|
611 |
Used in: web-app
|
612 |
|
613 |
Example:
|
614 |
|
615 |
<security-role>
|
616 |
<description>
|
617 |
This role includes all employees who are authorized
|
618 |
to access the employee service application.
|
619 |
</description>
|
620 |
<role-name>employee</role-name>
|
621 |
</security-role>
|
622 |
-->
|
623 |
<!--
|
624 |
The security-role-ref element contains the declaration of a security
|
625 |
role reference in the web application's code. The declaration consists
|
626 |
of an optional description, the security role name used in the code,
|
627 |
and an optional link to a security role. If the security role is not
|
628 |
specified, the Deployer must choose an appropriate security role.
|
629 |
|
630 |
The value of the role-name element must be the String used as the
|
631 |
parameter to the EJBContext.isCallerInRole(String roleName) method
|
632 |
or the HttpServletRequest.isUserInRole(String role) method.
|
633 |
|
634 |
Used in: servlet
|
635 |
|
636 |
-->
|
637 |
<!--
|
638 |
The servlet element contains the declarative data of a
|
639 |
servlet. If a jsp-file is specified and the load-on-startup element is
|
640 |
present, then the JSP should be precompiled and loaded.
|
641 |
|
642 |
Used in: web-app
|
643 |
-->
|
644 |
<!--
|
645 |
The servlet-class element contains the fully qualified class name
|
646 |
of the servlet.
|
647 |
|
648 |
Used in: servlet
|
649 |
-->
|
650 |
<!--
|
651 |
The servlet-mapping element defines a mapping between a servlet
|
652 |
and a url pattern
|
653 |
|
654 |
Used in: web-app
|
655 |
-->
|
656 |
<!--
|
657 |
The servlet-name element contains the canonical name of the
|
658 |
servlet. Each servlet name is unique within the web application.
|
659 |
|
660 |
Used in: filter-mapping, servlet, servlet-mapping
|
661 |
-->
|
662 |
<!--
|
663 |
The session-config element defines the session parameters for
|
664 |
this web application.
|
665 |
|
666 |
Used in: web-app
|
667 |
-->
|
668 |
<!--
|
669 |
The session-timeout element defines the default session timeout
|
670 |
interval for all sessions created in this web application. The
|
671 |
specified timeout must be expressed in a whole number of minutes.
|
672 |
If the timeout is 0 or less, the container ensures the default
|
673 |
behaviour of sessions is never to time out.
|
674 |
|
675 |
Used in: session-config
|
676 |
-->
|
677 |
<!--
|
678 |
The small-icon element contains the name of a file
|
679 |
containing a small (16 x 16) icon image. The file
|
680 |
name is a relative path within the web application's
|
681 |
war file.
|
682 |
|
683 |
The image may be either in the JPEG or GIF format.
|
684 |
The icon can be used by tools.
|
685 |
|
686 |
Used in: icon
|
687 |
|
688 |
Example:
|
689 |
|
690 |
<small-icon>employee-service-icon16x16.jpg</small-icon>
|
691 |
-->
|
692 |
<!--
|
693 |
The taglib element is used to describe a JSP tag library.
|
694 |
|
695 |
Used in: web-app
|
696 |
-->
|
697 |
<!--
|
698 |
the taglib-location element contains the location (as a resource
|
699 |
relative to the root of the web application) where to find the Tag
|
700 |
Libary Description file for the tag library.
|
701 |
|
702 |
Used in: taglib
|
703 |
-->
|
704 |
<!--
|
705 |
The taglib-uri element describes a URI, relative to the location
|
706 |
of the web.xml document, identifying a Tag Library used in the Web
|
707 |
Application.
|
708 |
|
709 |
Used in: taglib
|
710 |
-->
|
711 |
<!--
|
712 |
The transport-guarantee element specifies that the communication
|
713 |
between client and server should be NONE, INTEGRAL, or
|
714 |
CONFIDENTIAL. NONE means that the application does not require any
|
715 |
transport guarantees. A value of INTEGRAL means that the application
|
716 |
requires that the data sent between the client and server be sent in
|
717 |
such a way that it can't be changed in transit. CONFIDENTIAL means
|
718 |
that the application requires that the data be transmitted in a
|
719 |
fashion that prevents other entities from observing the contents of
|
720 |
the transmission. In most cases, the presence of the INTEGRAL or
|
721 |
CONFIDENTIAL flag will indicate that the use of SSL is required.
|
722 |
|
723 |
Used in: user-data-constraint
|
724 |
-->
|
725 |
<!--
|
726 |
The url-pattern element contains the url pattern of the mapping. Must
|
727 |
follow the rules specified in Section 11.2 of the Servlet API
|
728 |
Specification.
|
729 |
|
730 |
Used in: filter-mapping, servlet-mapping, web-resource-collection
|
731 |
-->
|
732 |
<!--
|
733 |
The user-data-constraint element is used to indicate how data
|
734 |
communicated between the client and container should be protected.
|
735 |
|
736 |
Used in: security-constraint
|
737 |
-->
|
738 |
<!--
|
739 |
The web-resource-collection element is used to identify a subset
|
740 |
of the resources and HTTP methods on those resources within a web
|
741 |
application to which a security constraint applies. If no HTTP methods
|
742 |
are specified, then the security constraint applies to all HTTP
|
743 |
methods.
|
744 |
|
745 |
Used in: security-constraint
|
746 |
-->
|
747 |
<!--
|
748 |
The web-resource-name contains the name of this web resource
|
749 |
collection.
|
750 |
|
751 |
Used in: web-resource-collection
|
752 |
-->
|
753 |
<!--
|
754 |
The welcome-file element contains file name to use as a default
|
755 |
welcome file, such as index.html
|
756 |
|
757 |
Used in: welcome-file-list
|
758 |
-->
|
759 |
<!--
|
760 |
The welcome-file-list contains an ordered list of welcome files
|
761 |
elements.
|
762 |
|
763 |
Used in: web-app
|
764 |
-->
|
765 |
<!--
|
766 |
The ID mechanism is to allow tools that produce additional deployment
|
767 |
information (i.e., information beyond the standard deployment
|
768 |
descriptor information) to store the non-standard information in a
|
769 |
separate file, and easily refer from these tool-specific files to the
|
770 |
information in the standard deployment descriptor.
|
771 |
|
772 |
Tools are not allowed to add the non-standard information into the
|
773 |
standard deployment descriptor.
|
774 |
-->
|
775 |
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:web="http://xmlns.jcp.org/xml/ns/javaee" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
|
776 |
<display-name>DaoAdresseService</display-name>
|
777 |
<description></description>
|
778 |
<welcome-file-list>
|
779 |
<welcome-file>index.html</welcome-file>
|
780 |
<welcome-file>index.jsp</welcome-file>
|
781 |
</welcome-file-list>
|
782 |
<resource-ref>
|
783 |
<description>MySQL fulddaekning on info.dao.int</description>
|
784 |
<res-ref-name>jdbc/fulddaekning</res-ref-name>
|
785 |
<res-type>javax.sql.DataSource</res-type>
|
786 |
<res-auth>Container</res-auth>
|
787 |
</resource-ref>
|
788 |
<filter>
|
789 |
<filter-name>SetCharacterEncoding</filter-name>
|
790 |
<filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class>
|
791 |
<init-param>
|
792 |
<param-name>encoding</param-name>
|
793 |
<param-value>UTF-8</param-value>
|
794 |
</init-param>
|
795 |
</filter>
|
796 |
<filter-mapping>
|
797 |
<filter-name>SetCharacterEncoding</filter-name>
|
798 |
<url-pattern>/*</url-pattern>
|
799 |
</filter-mapping>
|
800 |
|
801 |
<context-param>
|
802 |
<description>Bool: use google geocoding to help with streetnames</description>
|
803 |
<param-name>useGoogle</param-name>
|
804 |
<param-value>true</param-value>
|
805 |
</context-param>
|
806 |
|
807 |
<context-param>
|
808 |
<description>Bool: use OSM geocoding to help with streetnames</description>
|
809 |
<param-name>useOpenStreetMaps</param-name>
|
810 |
<param-value>true</param-value>
|
811 |
</context-param>
|
812 |
|
813 |
<context-param>
|
814 |
<description>Int: Timeout for HTTPRequest (ms)</description>
|
815 |
<param-name>osmTimeout</param-name>
|
816 |
<param-value>750</param-value>
|
817 |
</context-param>
|
818 |
|
819 |
<context-param>
|
820 |
<description>String: Base for nominatim URL</description>
|
821 |
<param-name>nominatimBase</param-name>
|
822 |
<param-value>http://nominatim.openstreetmap.org</param-value>
|
823 |
</context-param>
|
824 |
|
825 |
|
826 |
|
827 |
</web-app> |