1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
|
<html xmlns:Assertions="https://raw.githubusercontent.com/eclipse-ee4j/jakartaee-tck/master/internal/docs">
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<!--
Copyright (c) 2018, 2022 Oracle and/or its affiliates and others.
All rights reserved.
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-->
<title>Specification Assertion Detail</title>
</head>
<body bgcolor="white">
<br>
<CENTER>
<h2>Jakarta Servlet<br>Servlet - 6.1<br>
Specification Assertion Detail
</h2>
</CENTER>
<TABLE width="900" border="1" frame="box" cellpadding="5">
<TH bgcolor="#BFBFBF"><FONT size="1PT">Totals</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Total</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Active</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Deprecated</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Removed</FONT></TH>
<tr>
<TD align="center" valign="center"><font size="2PT">
# of Assertions
</font></TD><TD align="center" valign="center"><font size="2PT">566</font></TD><TD align="center" valign="center"><font size="2PT">543</font></TD><TD align="center" valign="center"><font size="2PT">2</font></TD><TD align="center" valign="center"><font size="2PT">21</font></TD>
</tr>
<tr>
<TD align="center" valign="center"><font size="2PT">
# of Required Assertions
</font></TD><TD align="center" valign="center"><font size="2PT">530</font></TD><TD align="center" valign="center"><font size="2PT">510</font></TD><TD align="center" valign="center"><font size="2PT">2</font></TD><TD align="center" valign="center"><font size="2PT">18</font></TD>
</tr>
<tr>
<TD align="center" valign="center"><font size="2PT">
# of Optional Assertions
</font></TD><TD align="center" valign="center"><font size="2PT">36</font></TD><TD align="center" valign="center"><font size="2PT">33</font></TD><TD align="center" valign="center"><font size="2PT">0</font></TD><TD align="center" valign="center"><font size="2PT">3</font></TD>
</tr>
</TABLE>
<br>
<TABLE width="900" border="1" frame="box" cellpadding="5" summary="Specification Assertions">
<TH bgcolor="#BFBFBF"><FONT size="1PT">ID</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Chapter</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Section</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Description</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Required</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Dependency</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Implementation Specific</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Defined by</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Status</FONT></TH><TH bgcolor="#BFBFBF"><FONT size="1PT">Testable</FONT></TH>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:1"></a><font size="1PT">Servlet:SPEC:1</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">All servlet containers must support HTTP/1.0 and HTTP/1.1 protocols</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:2"></a><font size="1PT">Servlet:SPEC:2</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Java SE 7 is the minimum version of the underlying Java platform with which containers must be built.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:269"></a><font size="1PT">Servlet:SPEC:269</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="center" valign="center"><font size="1PT">6.1</font></TD><TD align="left" valign="center"><font size="1PT">In Servlet 2.5, metadata-complete only affected the scanning of annotations at
deployment time. The notion of web-fragments did not exist in servlet 2.5. However
in servlet 3.0 and later, metadata-complete affects scanning of all annotations that
specify deployment information and web-fragments at deployment time. The
version of the descriptor MUST not affect which annotations you scan for in a web
application. An implementation of a particular version of the specification MUST
scan for all annotations supported in that configuration, unless metadata-complete
is specified.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:3"></a><font size="1PT">Servlet:SPEC:3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">A servlet hosted in a non-distributed environment, the servlet container must use only one instance per servlet declaration.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:4"></a><font size="1PT">Servlet:SPEC:4</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">A servlet deployed as part of an application marked in the deployment descriptor as distributable, a container may have only one instance per servlet declaration per virtual machine (VM).</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:5"></a><font size="1PT">Servlet:SPEC:5</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">The life cycle of a servlet is expressed in the API by the 'init', 'service', and 'destroy' methods of the jakarta.servlet.Servlet interface that all servlets must implement directly, or indirectly through the GenericServlet or HttpServlet abstract classes.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:6"></a><font size="1PT">Servlet:SPEC:6</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">The servlet container is responsible for loading and instantiating servlets. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:6.1"></a><font size="1PT">Servlet:SPEC:6.1</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">When the servlet engine is started, needed servlet classes must be located by the servlet container using normal Java class loading facilities.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:7"></a><font size="1PT">Servlet:SPEC:7</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.2</font></TD><TD align="left" valign="center"><font size="1PT">After the servlet object is instantiated, the container must initialize the servlet before it can handle requests from clients by calling the init method of the Server interface with a unique (per servlet declaration) object implementing the ServerConfig interface.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:8"></a><font size="1PT">Servlet:SPEC:8</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.2.1</font></TD><TD align="left" valign="center"><font size="1PT">The servlet container must not call the destroy method on a Servlet that threw an Exception during the initialization process.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:9"></a><font size="1PT">Servlet:SPEC:9</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.2.1</font></TD><TD align="left" valign="center"><font size="1PT">A servlet throwing an UnavailableException that indicates a minimum time of unavailability, the container must wait for the period of time specified to pass before creating and initializing a new servlet instance.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:10"></a><font size="1PT">Servlet:SPEC:10</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.1</font></TD><TD align="left" valign="center"><font size="1PT">For servlets where the service method (or methods such as doGet or doPost which are dispatched to the service method of the HttpServlet abstract class) has been defined with the synchronized keyword, the servlet container must serialize request through it.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">deprecated</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11"></a><font size="1PT">Servlet:SPEC:11</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.2</font></TD><TD align="left" valign="center"><font size="1PT">If a permanent unavailability is indicated by the UnavailableException, the servlet container must remove the servlet from service, call its destroy method, and release the servlet instance.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11.1"></a><font size="1PT">Servlet:SPEC:11.1</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.2</font></TD><TD align="left" valign="center"><font size="1PT">Any requests refused by the container by the cause, must be returned with a SC_NOT_FOUND(404) response.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:270"></a><font size="1PT">Servlet:SPEC:270</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.3</font></TD><TD align="left" valign="center"><font size="1PT">public ServletRequest getRequest() - returns the request that was used to
initialize the AsyncContext by calling one of the startAsync methods. Calling
getRequest when complete or any of the dispatch methods has been
previously called in the asynchronous cycle will result in an IllegalStateException.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:271"></a><font size="1PT">Servlet:SPEC:271</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.3</font></TD><TD align="left" valign="center"><font size="1PT">public ServletResponse getResponse() - returns the response that was used
to initialize the AsyncContext by calling one of the startAsync methods.
Calling getResponse when complete or any of the dispatch methods has
been previously called in the asynchronous cycle will result in an
IllegalStateException.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:272"></a><font size="1PT">Servlet:SPEC:272</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.5</font></TD><TD align="left" valign="center"><font size="1PT">The servlet container provides an HTTP upgrade mechanism. However the servlet
container itself does not have knowledge about the upgraded protocol. The protocol
processing is encapsulated in the HttpUpgradeHandler.
Data reading or writing between the servlet container and the HttpUpgradeHandler is in byte streams..
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:273"></a><font size="1PT">Servlet:SPEC:273</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.5</font></TD><TD align="left" valign="center"><font size="1PT">When an upgrade request is received, the servlet can invoke the
HttpServletRequest.upgrade method, which starts the upgrade process.
This method instantiates the given HttpUpgradeHandler class.
The returned HttpUpgradeHandler instance may be further customized. The application
prepares and sends an appropriate response to the client. After exiting the service
method of the servlet, the servlet container completes the processing of all filters and
marks the connection to be handled by the HttpUpgradeHandler. It then calls
the HttpUpgradeHandler's init method, passing a WebConnection to allow the protocol handler
access to the data streams.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:274"></a><font size="1PT">Servlet:SPEC:274</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.5</font></TD><TD align="left" valign="center"><font size="1PT">The servlet filters only process the initial HTTP request and response. They are not
involved in subsequent communications. In other words, they are not invoked once
the request has been upgraded.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:275"></a><font size="1PT">Servlet:SPEC:275</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.5</font></TD><TD align="left" valign="center"><font size="1PT">The HttpUpgradeHandler may use non blocking IO to consume and produce messages. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:299"></a><font size="1PT">Servlet:SPEC:299</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.3.5</font></TD><TD align="left" valign="center"><font size="1PT">When the upgrade processing is done, HttpUpgradeHandler.destroy will be invoked.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:12"></a><font size="1PT">Servlet:SPEC:12</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.4</font></TD><TD align="left" valign="center"><font size="1PT">When the servlet container determines that a Servlet should be removed from service, it must call the destroy method of the Servlet interface to allow the servlet to release any resources it is using and save any persistent state.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:12.1"></a><font size="1PT">Servlet:SPEC:12.1</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.4</font></TD><TD align="left" valign="center"><font size="1PT">Before the container calls the destroy method, it must allow any threads that are currently running in the service method of the servlet to complete execution, or exceed a server defined time limit.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:12.2"></a><font size="1PT">Servlet:SPEC:12.2</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.4</font></TD><TD align="left" valign="center"><font size="1PT">Once the destroy method is called on a servlet instance, the container must not route other requests to that instance of the Servlet.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:12.3"></a><font size="1PT">Servlet:SPEC:12.3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">3.4</font></TD><TD align="left" valign="center"><font size="1PT">After the destroy method completes, the servlet container must release the servlet instance so that it is eligible for garbage collection.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:20"></a><font size="1PT">Servlet:SPEC:20</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">Data from the query string and the post body are aggregated into the request
parameter set. Query string data is presented before post body data.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:21"></a><font size="1PT">Servlet:SPEC:21</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">Path parameters that are a part of a GET request (as defined by HTTP 1.1) are not exposed by these APIs.
They must be parsed from the String values returned by the getRequestURI method or the getPathInfo method.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:22"></a><font size="1PT">Servlet:SPEC:22</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The following conditions must be met before post form data will be populated to the parameter set:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:22.1"></a><font size="1PT">Servlet:SPEC:22.1</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The request is an HTTP or HTTPS request</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:22.2"></a><font size="1PT">Servlet:SPEC:22.2</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The HTTP method is POST</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:22.3"></a><font size="1PT">Servlet:SPEC:22.3</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The content type is application/x-www-form-urlencoded</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:22.4"></a><font size="1PT">Servlet:SPEC:22.4</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The servlet has made an initial call to any of the getParameter family of methods on the request object.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:22.5"></a><font size="1PT">Servlet:SPEC:22.5</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">If the conditions are not met, and the post form data is not included in the parameter
set, the post data must still be available to the servlet via the request object's input stream.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:22.6"></a><font size="1PT">Servlet:SPEC:22.6</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">If the conditions are met, post form data will no longer be available for
reading directly from the request object?s input stream.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:276"></a><font size="1PT">Servlet:SPEC:276</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Servlet container allows files to be uploaded when data is sent as multipart/form-data.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:277"></a><font size="1PT">Servlet:SPEC:277</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The servlet container provides multipart/form-data processing if any one of the following conditions is met.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:277.1"></a><font size="1PT">Servlet:SPEC:277.1</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The servlet handling the request is annotated with the @MultipartConfig
as defined in Section 8.1.5, "@MultipartConfig" on page8-68.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:277.2"></a><font size="1PT">Servlet:SPEC:277.2</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Deployment descriptors contain a multipart-config element for the servlet handling the request.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:278"></a><font size="1PT">Servlet:SPEC:278</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">How data in a request of type multipart/form-data is made available depends on
whether the servlet container provides multipart/form-data processing:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:278.1"></a><font size="1PT">Servlet:SPEC:278.1</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">If the servlet container provides multipart/form-data processing,
the data is made available through the following methods in HttpServletRequest:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:278.1.1"></a><font size="1PT">Servlet:SPEC:278.1.1</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">public Collection <Part> getParts()
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:278.1.2"></a><font size="1PT">Servlet:SPEC:278.1.2</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">public Part getPart(String name)</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:278.1.3"></a><font size="1PT">Servlet:SPEC:278.1.3</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Each part provides access to the headers, content type related with it
and the content via the Part.getInputStream method.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:278.1.4"></a><font size="1PT">Servlet:SPEC:278.1.4</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">For parts with form-data as the Content-Disposition, but without a filename,
the string value of the part will also be available through the getParameter and
getParameterValues methods on HttpServletRequest, using the name of the part.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:278.2"></a><font size="1PT">Servlet:SPEC:278.2</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">If the servlet container does not provide the multi-part/form-data processing,
the data will be available through the HttpServletReuqest.getInputStream.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:23"></a><font size="1PT">Servlet:SPEC:23</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">(Servlet Path)This path starts with a '/' character except in the case
where the request is matched with the '/*' or "" pattern, in which case it is an
empty string.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:24"></a><font size="1PT">Servlet:SPEC:24</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">(Servlet Path)The path section that directly corresponds to the mapping which
activated this request. This path starts with a '/' character except...
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:25"></a><font size="1PT">Servlet:SPEC:25</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The part of the request path that is not part of the Context Path or the
Servlet Path. It is either null if there is no extra path, or is a string with a leading
'/'.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:279"></a><font size="1PT">Servlet:SPEC:279</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">It is important to note that, except for URL encoding differences between the request
URI and the path parts, the following equation is always true:
requestURI = contextPath + servletPath + pathInfo
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:280"></a><font size="1PT">Servlet:SPEC:280</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">In situations where the servlet container cannot determine a valid file path for these
methods, such as when the Web application is executed from an archive, on a remote
file system not accessible locally, or in a database, these methods must return null.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:281"></a><font size="1PT">Servlet:SPEC:281</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">Resources inside the META-INF/resources directory of JAR file must be considered
only if the container has unpacked them from their containing JAR file when a call to
getRealPath() is made, and in this case MUST return the unpacked location.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:282"></a><font size="1PT">Servlet:SPEC:282</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">The ReadListener provides the following callback methods for non blocking IO -
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:282.1"></a><font size="1PT">Servlet:SPEC:282.1</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">ReadListener.onDataAvailable(). The onDataAvailable method is invoked on the
ReadListener when data is available to read from the incoming request
stream. The container will invoke the method. This method will be invoked
once for every set of data available.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:282.2"></a><font size="1PT">Servlet:SPEC:282.2</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">ReadListener.onAllDataRead(). The onAllDataRead method is invoked when you have
finished reading all the data for the ServletRequest for which the listener was registered.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:282.3"></a><font size="1PT">Servlet:SPEC:282.3</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">ReadListener.onError(Throwable t). The onError method is invoked if there is any error or
exception that occurs while processing the request.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:282.5"></a><font size="1PT">Servlet:SPEC:282.5</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">boolean ServletInputStream.isFinished(). The isFinished method returns true when all the
data for the request associated with the ServletInputStream has been read.
Otherwise it returns false.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:282.6"></a><font size="1PT">Servlet:SPEC:282.6</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">boolean ServletInputStream.isReady(). The isReady method returns true if data can be read
without blocking. If no data can be read without blocking it returns false. If
isReady returns false it is illegal to call the read method and an
IllegalStateException MUST be thrown.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:282.7"></a><font size="1PT">Servlet:SPEC:282.7</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">void ServletInputStream.setReadListener(ReadListener listener). Sets the ReadListener
defined above to get invoked to read data in a non-blocking fashion. Once the
listener is associated for the given ServletInputStream, the container invokes
the methods on the ReadListener when data is available to read, all the data
has been read or if there was an error processing the request. Registering a
ReadListener will start non-blocking IO. It is illegal to switch to the traditional
blocking IO at that point and an IllegalStateException MUST be thrown.
A subsequent call to setReadListener in the scope of the current request is
illegal and an IllegalStateException MUST be thrown..
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:26"></a><font size="1PT">Servlet:SPEC:26</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="left" valign="center"><font size="1PT">If a request has been transmitted over a secure protocol, such as HTTPS, this
information must be exposed via the isSecure method of the ServletRequest
interface. The Web container must expose the following attributes to the servlet
programmer:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:26.1"></a><font size="1PT">Servlet:SPEC:26.1</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="left" valign="center"><font size="1PT">attribute: cipher suite - attribute name: jakarta.servlet.request.cipher_suite - Java type: String </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:26.2"></a><font size="1PT">Servlet:SPEC:26.2</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="left" valign="center"><font size="1PT">attribute: bit size of the algorithm - attribute name: jakarta.servlet.request.key_size - Java type: Integer</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:26.4"></a><font size="1PT">Servlet:SPEC:26.4</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="left" valign="center"><font size="1PT">attribute: SSL session id - attribute name: jakarta.servlet.request.ssl_session_id - Java type: String</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:26.3"></a><font size="1PT">Servlet:SPEC:26.3</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="left" valign="center"><font size="1PT">If there is an SSL certificate associated with the request, it must be exposed by the
servlet container to the servlet programmer as an array of objects of type
java.security.cert.X509Certificate and accessible via a ServletRequest
attribute of jakarta.servlet.request.X509Certificate.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:26.3.1"></a><font size="1PT">Servlet:SPEC:26.3.1</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="left" valign="center"><font size="1PT">The order of this array (associated with the jakarta.servlet.request.X509Certificate request attribute)
is being defined as being in ascending order of trust.
The first certificate in the chain is the one set by the client,
the next is the one used to authenticate first, and so on.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:27"></a><font size="1PT">Servlet:SPEC:27</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">The default encoding of a request the container uses to create the request reader
and parse POST data must be "ISO-8859-1", if none has been specified by the client request.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:28"></a><font size="1PT">Servlet:SPEC:28</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">Calling the (setCharacterEncoding(String enc)) method after once data has been read will not affect the encoding.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:29"></a><font size="1PT">Servlet:SPEC:29</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="left" valign="center"><font size="1PT">Each request object is valid only within the scope of a servlet's service method, or
within the scope of a filter's doFilter method, unless the asynchronous processing
is enabled for the component and the startAsync method is invoked on the request object.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:283"></a><font size="1PT">Servlet:SPEC:283</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="left" valign="center"><font size="1PT">In the case where asynchronous processing occurs, the request object remains
valid until complete is invoked on the AsyncContext.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:305"></a><font size="1PT">Servlet:SPEC:305</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="left" valign="center"><font size="1PT">In case of upgrade, the above is still true.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:13"></a><font size="1PT">Servlet:SPEC:13</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">There is only one instance object of the ServletContext interface
associated with each web application deployed into a container.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:14"></a><font size="1PT">Servlet:SPEC:14</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">In cases where the container is distributed over many virtual machines,
a Web application will have an instance of the ServletContext for each JVM.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:15"></a><font size="1PT">Servlet:SPEC:15</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">A default ServletContext must be made available to servlets not deployed as a web application.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:15.1"></a><font size="1PT">Servlet:SPEC:15.1</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">In a distributed container, the default ServletContext is non-distributable and must only exist in one VM.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:16"></a><font size="1PT">Servlet:SPEC:16</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">Any attribute bound into a context is available to any other servlet
that is part of the same web application.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:17"></a><font size="1PT">Servlet:SPEC:17</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">Web servers may support multiple logical hosts sharing one IP address on a server.
This capability is sometimes referred to as "virtual hosting".
In this case, each logical host must have its own servlet context or set of servlet contexts.
Servlet contexts can not be shared across virtual hosts.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:18"></a><font size="1PT">Servlet:SPEC:18</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">Although a Container Provider implementation of a class reloading scheme
for ease of development is not required, any such implementation must ensure that all servlets,
and classes that they may use, are loaded in the scope of a single class loader.
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:18.1"></a><font size="1PT">Servlet:SPEC:18.1</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">The full semantics of notification to session binding listeners
should be supported by containers for use in the monitoring of session termination
upon class reloading.
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:19"></a><font size="1PT">Servlet:SPEC:19</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">Servlet containers must provide a private temporary directory for each servlet context.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:19.1"></a><font size="1PT">Servlet:SPEC:19.1</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">(The container must) make it available via the jakarta.servlet.context.tempdir context attribute.
The objects associated with the attribute must be of type java.io.File.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:19.2"></a><font size="1PT">Servlet:SPEC:19.2</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">Servlet containers are required to ensure that the contents of the temporary directory
of one servlet context is not visible to the servlet contexts of other Web applications
running on the servlet container.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:30"></a><font size="1PT">Servlet:SPEC:30</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">A servlet container is allowed, but not required,
to buffer output going to the client for efficiency purposes.
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:31"></a><font size="1PT">Servlet:SPEC:31</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">If a response has been committed and the reset or resetBuffer methods have been called,
an IllegalStateException must be thrown. The response and its associated buffer will be unchanged.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:32"></a><font size="1PT">Servlet:SPEC:32</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">When using a buffer, the container must immediately flush the contents of a filled buffer
to the client. If this is the first data sent to the client, the response is considered to be committed.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:33"></a><font size="1PT">Servlet:SPEC:33</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">To be successfully transmitted back to the client, headers must be set before the response is committed.
Headers set after the response is committed will be ignored by the servlet container.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:34"></a><font size="1PT">Servlet:SPEC:34</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Servlet containers must not set a default content type when the servlet programmer does not set the type.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:183"></a><font size="1PT">Servlet:SPEC:183</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The setHeader method sets a header with a given name and value.
A previous header is replaced by the new header.
Where a set of header values exist for the name,
the values are cleared and replaced with the new value.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:300"></a><font size="1PT">Servlet:SPEC:300</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">Non-blocking IO only works with async request processing in Servlets and Filters
as defined in Section 2.3.3.3, "Asynchronous processing" on page 2-10,
and upgrade processing (as defined in Section 2.3.3.5, ?Upgrade Processing? on page 2-20).
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:306"></a><font size="1PT">Servlet:SPEC:306</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">Otherwise, an IllegalStateException must be thrown when ServletInputStream.setReadListener
or ServletOutputStream.setWriteListener is invoked.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:35"></a><font size="1PT">Servlet:SPEC:35</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">If a partial URL is given and, for whatever reason, cannot be converted into a valid URL,
then this method(sendRedirect) must throw an IllegalArgumentException.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:36"></a><font size="1PT">Servlet:SPEC:36</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">These methods(sendError) will have the side effect of committing the response,
if it has not already been committed, and terminating it. No further output to the client should
be made by the servlet after these methods are called.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:37"></a><font size="1PT">Servlet:SPEC:37</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">These methods(sendRedirect) will have the side effect of commiting the response,
if it has not already been committed, and terminating it. No further output to the client should
be made by the servlet after these methods are called.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:38"></a><font size="1PT">Servlet:SPEC:38</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">If data has been written to the response buffer, but not returned to the client (i.e., the response is not committed), the data in the response buffer must be cleared and replaced with the data set by sendRedirect.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:39"></a><font size="1PT">Servlet:SPEC:39</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">If data has been written to the response buffer,
but not returned to the client(i.e., the response is not committed),
the data in the response buffer must be cleared and replaced with the data set by sendError.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:40"></a><font size="1PT">Servlet:SPEC:40</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">If data is written to the response after sendRedirect has been called,
the data is ignored.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:41"></a><font size="1PT">Servlet:SPEC:41</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">If data is written to the response after sendError has been called,
the data is ignored.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:284"></a><font size="1PT">Servlet:SPEC:284</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">When a response is closed, the container must immediately flush all remaining
content in the response buffer to the client.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:42"></a><font size="1PT">Servlet:SPEC:42</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The following events indicate that the servlet has satisfied the request
and that the response object is to be closed:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:42.1"></a><font size="1PT">Servlet:SPEC:42.1</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The termination of the service method of the servlet.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:42.2"></a><font size="1PT">Servlet:SPEC:42.2</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The amount of content specified in the setContentLength
or setContentLengthLong method of the response
has been greater than zero and has been written to the response.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:42.3"></a><font size="1PT">Servlet:SPEC:42.3</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The sendError method is called.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:42.4"></a><font size="1PT">Servlet:SPEC:42.4</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The sendRedirect method is called.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:42.5"></a><font size="1PT">Servlet:SPEC:42.5</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The complete method on AsyncContext is called.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:43"></a><font size="1PT">Servlet:SPEC:43</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">Each response object is valid only within the scope of a servlet's service method,
or within the scope of a filter's doFilter method, unless the associated request object
has asynchronous processing enabled for the component.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:285"></a><font size="1PT">Servlet:SPEC:285</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">If asynchronous processing on the associated request is started,
then the request object remains valid until complete method on AsyncContext is called.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:44"></a><font size="1PT">Servlet:SPEC:44</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">After deployment of a web application,
and before a request causes the container to access a web resource,
The container must locate the list of filters that must be applied to the Web resource as described below.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:45"></a><font size="1PT">Servlet:SPEC:45</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The container must ensure that it has instantiated a filter of the appropriate class
for each filter in the list, and called its init(FilterConfig config) method.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:286"></a><font size="1PT">Servlet:SPEC:286</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The filter may throw an exception to indicate that it cannot function properly.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:46"></a><font size="1PT">Servlet:SPEC:46</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">If the exception thrown by a Filter is of type UnavailableException,
the container may examine the isPermanent attribute of the exception
and may choose to retry the filter at some later time.
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:47"></a><font size="1PT">Servlet:SPEC:47</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Only one instance per <filter> declaration in
the deployment descriptor is instantiated per JVM of the container.
The container provides the filter config as declared in the filter's deployment descriptor,
the reference to the ServletContext for the Web application, and the set of initialization parameters.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:48"></a><font size="1PT">Servlet:SPEC:48</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">When the container receives an incoming request it takes the first filter instance
in the list and calls its doFilter method, passing in the ServletRequest and ServletResponse,
and a reference to the FilterChain object it will use.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287"></a><font size="1PT">Servlet:SPEC:287</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The doFilter method of a filter will typically be implemented following this
or some subset of the following pattern:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.1"></a><font size="1PT">Servlet:SPEC:287.1</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The method examines the request's headers.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.2"></a><font size="1PT">Servlet:SPEC:287.2</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The method may wrap the request object with a customized implementation of
ServletRequest or HttpServletRequest in order to modify request headers or data.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.3"></a><font size="1PT">Servlet:SPEC:287.3</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The method may wrap the response object passed in to its doFilter method with a
customized implementation of ServletResponse or HttpServletResponse to
modify response headers or data.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.4"></a><font size="1PT">Servlet:SPEC:287.4</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The filter may invoke the next entity in the filter chain. The next entity may be
another filter, or if the filter making the invocation is the last filter configured in the
deployment descriptor for this chain, the next entity is the target Web resource. The
invocation of the next entity is effected by calling the doFilter method on the
FilterChain object, and passing in the request and response with which it was
called or passing in wrapped versions it may have created.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:50"></a><font size="1PT">Servlet:SPEC:50</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The filter chain's implementation of the doFilter method, provided by the
container, must locate the next entity in the filter chain and invoke its doFilter
method, passing in the appropriate request and response objects.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.5"></a><font size="1PT">Servlet:SPEC:287.5</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Alternatively, the filter chain can block the request by not making the call
to invoke the next entity, leaving the filter responsible for filling out the response object.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.6"></a><font size="1PT">Servlet:SPEC:287.6</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The service method is required to run in the same thread as all filters
that apply to the servlet.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.7"></a><font size="1PT">Servlet:SPEC:287.7</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">After invocation of the next filter in the chain, the filter may examine response
headers.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.8"></a><font size="1PT">Servlet:SPEC:287.8</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Alternatively, the filter may have thrown an exception to indicate an error in
processing. If the filter throws an UnavailableException during its doFilter
processing, the container must not attempt continued processing down the filter
chain. It may choose to retry the whole chain at a later time if the exception is not
marked permanent.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:287.9"></a><font size="1PT">Servlet:SPEC:287.9</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">When the last filter in the chain has been invoked, the next entity accessed is the
target servlet or resource at the end of the chain.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:49"></a><font size="1PT">Servlet:SPEC:49</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Before a filter instance can be removed from service by the container,
the container must first call the destroy method on the filter to enable the filter
to release any resources and perform other cleanup operations.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:288"></a><font size="1PT">Servlet:SPEC:288</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">When a filter invokes the doFilter method on the container's filter
chain implementation, the container must ensure that the request and response
object that it passes to the next entity in the filter chain, or to the target web resource
if the filter was the last in the chain, is the same object that was passed into the
doFilter method by the calling filter.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:51"></a><font size="1PT">Servlet:SPEC:51</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">The same requirement of wrapper object identity applies to the calls from a servlet
or a filter to RequestDispatcher.forward or RequestDispatcher.include, when
the caller wraps the request or response objects. In this case, the request and
response objects seen by the called servlet must be the same wrapper objects that
were passed in by the calling servlet or filter.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:52"></a><font size="1PT">Servlet:SPEC:52</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">The order the container uses in building the chain of filters to be applied for
a particular request URI is as follows:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:52.1"></a><font size="1PT">Servlet:SPEC:52.1</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">the <url-pattern> matching filter-mappings in the same order
that these elements appear in the deployment descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:52.2"></a><font size="1PT">Servlet:SPEC:52.2</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">The <servlet-name> matching filter-mappings in the same order
that these elements appear in the deployment descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:53"></a><font size="1PT">Servlet:SPEC:53</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">It is expected that high performance Web containers will cache filter chains
so that they do not need to compute them on a per-request basis.
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:302"></a><font size="1PT">Servlet:SPEC:302</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">By using the new <dispatcher> element in the deployment descriptor,
the developer can indicate for a filter-mapping whether he would like the filter
to be applied to requests when:
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:54"></a><font size="1PT">Servlet:SPEC:54</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">The request comes directly from the client.
This is indicated by a <dispatcher> element with value REQUEST,
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:58"></a><font size="1PT">Servlet:SPEC:58</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">The request comes directly from the client.
This is indicated by the absence of any <dispatcher> elements.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:55"></a><font size="1PT">Servlet:SPEC:55</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">The request is being processed under a request dispatcher representing
the Web component matching the <url-pattern> or <servlet-name> using a forward() call.
This is indicated by a <distpatcher> element with value FORWARD.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:56"></a><font size="1PT">Servlet:SPEC:56</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">The request is being processed under a request dispatcher representing
the Web component matching the <url-pattern> or <servlet-name> using an include() call.
This is indicated by a <distpatcher> element with value INCLUDE.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:57"></a><font size="1PT">Servlet:SPEC:57</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">The request is being processed with the error page mechanism
specified in ?Error Handling? on page 106 to an error resource matching
the <url-pattern>. This is indicated by a <dispatcher> element
with the value ERROR.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:301"></a><font size="1PT">Servlet:SPEC:301</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">The request is being processed with the async context dispatch mechanism
specified in ?Asynchronous processing? on page 10 to a web component using a dispatch call.
This is indicated by a <dispatcher> element with the value ASYNC.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:59"></a><font size="1PT">Servlet:SPEC:59</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">(The container must be able to support) any combination of 1, 2, 3, 4 or 5 above.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:202"></a><font size="1PT">Servlet:SPEC:202</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">Session tracking through HTTP cookies is the most used session tracking mechanism
and is required to be supported by all servlet containers.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:303"></a><font size="1PT">Servlet:SPEC:303</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The container sends a cookie to the client.
The client will then return the cookie on each subsequent request to the server,
unambiguously associating the request with a session.
The name of the session tracking cookie must be JSESSIONID.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:60"></a><font size="1PT">Servlet:SPEC:60</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">1.3</font></TD><TD align="left" valign="center"><font size="1PT">When a client will not accept a cookie, URL rewriting may be used by the server
as the basis for session tracking. URL rewriting involves adding data, a session ID,
to the URL path that is interpreted by the container to associate the request with a session.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:60.2"></a><font size="1PT">Servlet:SPEC:60.2</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">1.3</font></TD><TD align="left" valign="center"><font size="1PT"> The session ID must be encoded as a path parameter in the URL string.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:60.1"></a><font size="1PT">Servlet:SPEC:60.1</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">1.3</font></TD><TD align="left" valign="center"><font size="1PT">The name of the parameter must be 'jsessionid'.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:61"></a><font size="1PT">Servlet:SPEC:61</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">1.4</font></TD><TD align="left" valign="center"><font size="1PT">Web container must be able to support HTTP session tracking
while servicing HTTP request from clients that do no support the use of cookies.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:62"></a><font size="1PT">Servlet:SPEC:62</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">A session is considered 'new' if either of the following are true:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:62.1"></a><font size="1PT">Servlet:SPEC:62.1</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The client does not yet know about the session.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:62.2"></a><font size="1PT">Servlet:SPEC:62.2</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The client chooses not to join a session.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:63"></a><font size="1PT">Servlet:SPEC:63</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">HttpSession objects must be scoped at the application (or servlet context) level.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:63.1"></a><font size="1PT">Servlet:SPEC:63.1</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">The underlying mechanism, such as the cookies used to establish the session,
including the attributes in that object, must never be shared between context by the container.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:63.2"></a><font size="1PT">Servlet:SPEC:63.2</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">Additionally, sessions of a context must be resumable by requests into
that context regardless of whether their associated context was being accessed
directly or as the target of a request dispatch at the time the sessions were created.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:64"></a><font size="1PT">Servlet:SPEC:64</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">The valueBound method must be called before the object is made available vai the getAttribute method of the HttpSession interface.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:65"></a><font size="1PT">Servlet:SPEC:65</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">The valueUnbound method must be called after the object is no longer available via the getAttribute method of the HttpSession interface.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:66"></a><font size="1PT">Servlet:SPEC:66</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The default timeout period for sessions is defined by the servlet container and can be obtained via the getMaxInactiveInterval method of the HttpSession interface.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:67"></a><font size="1PT">Servlet:SPEC:67</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">Invalidation will not take effect until all servlets using that session have exited the service method.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:203"></a><font size="1PT">Servlet:SPEC:203</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The getLastAccessedTime method of the HttpSession interface allows a servlet to determine the last time the session was accessed before the current request. The session is considered to be accessed when a request that is part of the session is first handled by the servlet container.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:68"></a><font size="1PT">Servlet:SPEC:68</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">Within an application marked as distributable, all request that are part of a session must be handled by one virtual machine at a time.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:69"></a><font size="1PT">Servlet:SPEC:69</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">The container must be able to handle all objects placed into instances of the HttpSession class using the setAttribute or putValue methods appropriately, with the following restrictions:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:69.1"></a><font size="1PT">Servlet:SPEC:69.1</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">The container must accept objects that implement the Serializable interface.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:69.2"></a><font size="1PT">Servlet:SPEC:69.2</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">The container may choose to support storage of other designated objects in the HttpSession, such as references to Jakarta Enterprise Bean components and transactions.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:69.3"></a><font size="1PT">Servlet:SPEC:69.3</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">Migration of sessions will be handled by container-specific facilities.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:70"></a><font size="1PT">Servlet:SPEC:70</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">The distributed servlet container must throw an IllegalArgumentException for objects where the container cannot support the mechanism necessary for migration of the session storing them.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:71"></a><font size="1PT">Servlet:SPEC:71</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">The distributed servlet container must support the mechanism necessary for migrating objects that implement Serializable.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:72"></a><font size="1PT">Servlet:SPEC:72</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">Distributed servlet containers must support the mechanism necessary for migrating objects that implements Serializable.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:73"></a><font size="1PT">Servlet:SPEC:73</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">If distributed contains persist or migrate sessions to provide quality of service features, they are not restricted to using the native JVM Serialization mechanism for serializing HttpSessions and their attributes.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:74"></a><font size="1PT">Servlet:SPEC:74</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">Containers must notify any session attributes implementing the HttpSessionActivationListener during migration of a session. They must notify listeners of passivation prior to serialization of a session, and of activation after deserialization of a session</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:307"></a><font size="1PT">Servlet:SPEC:307</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">In a web application, classes using annotations will have their annotations processed
only if they are located in the WEB-INF/classes directory, or if they are packaged
in a jar file located in WEB-INF/lib within the application.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:308"></a><font size="1PT">Servlet:SPEC:308</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">The web application deployment descriptor contains a new ?metadata-complete?
attribute on the web-app element. The ?metadata-complete? attribute defines
whether the web descriptor is complete, or whether the class files of the jar file
should be examined for annotations and web fragments at deployment time. If
?metadata-complete? is set to "true", the deployment tool MUST ignore any
servlet annotations that specify deployment information present in the class files of
the application and web fragments. If the metadata-complete attribute is not
specified or is set to "false", the deployment tool must examine the class files of the
application for annotations, and scan for web fragments.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221"></a><font size="1PT">Servlet:SPEC:221</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">This annotation(@WebServlet) is used to define a Servlet component in a web application. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.1"></a><font size="1PT">Servlet:SPEC:221.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">This annotation is specified on a class and contains metadata about the Servlet being declared. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.2"></a><font size="1PT">Servlet:SPEC:221.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The urlPatterns or the value attribute on the annotation MUST be present. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.3"></a><font size="1PT">Servlet:SPEC:221.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">All other attributes are optional with default settings (see javadocs for more details). </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.4"></a><font size="1PT">Servlet:SPEC:221.4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">It is recommended to use value when the only attribute on the annotation is the url pattern and to use the urlPatterns attribute when the other attributes are also used. </font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.5"></a><font size="1PT">Servlet:SPEC:221.5</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">It is illegal to have both value and urlPatterns attribute used together on the same annotation. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.6"></a><font size="1PT">Servlet:SPEC:221.6</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The default name of the Servlet if not specified is the fully qualified class name.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.7"></a><font size="1PT">Servlet:SPEC:221.7</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">The annotated servlet MUST specify at least one url pattern to be deployed. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.8"></a><font size="1PT">Servlet:SPEC:221.8</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">If the same servlet class is declared in the deployment descriptor under a different name,
a new instance of the servlet MUST be instantiated.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.9"></a><font size="1PT">Servlet:SPEC:221.9</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">If the same servlet class is added to the ServletContext via the programmatic API
defined in Section 4.4.1, "Programmatically adding and configuring Servlets" on page 4-35,
the attribute values declared via the @WebServlet annotation MUST be ignored and
a new instance of the servlet with the name specified MUST be created.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:221.10"></a><font size="1PT">Servlet:SPEC:221.10</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">Classes annotated with @WebServlet class MUST extend the jakarta.servlet.http.HttpServlet class.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:222"></a><font size="1PT">Servlet:SPEC:222</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.5</font></TD><TD align="left" valign="center"><font size="1PT">This annotation(@MultipartConfig), when specified on a Servlet, indicates that the request it expects is of type mime/multipart. The HttpServletRequest object of the corresponding servlet MUST make available the mime attachments via the getParts and getPart methods to iterate over the various mime attachments. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:223"></a><font size="1PT">Servlet:SPEC:223</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.5</font></TD><TD align="left" valign="center"><font size="1PT">The location attribute of the jakarta.servlet.annotation.MultipartConfig and the <location> element of the <multipart-config> is interpreted as an absolut path and defaults to the value of the jakarta.servlet.context.tempdir. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:224"></a><font size="1PT">Servlet:SPEC:224</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.5</font></TD><TD align="left" valign="center"><font size="1PT">If a relative path is specified(in <location>), it will be relative to the tempdir location.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:225"></a><font size="1PT">Servlet:SPEC:225</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">1.5</font></TD><TD align="left" valign="center"><font size="1PT">The test for absolute path vs relative path (in <location>) MUST be done via java.io.File.isAbsolute. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:226"></a><font size="1PT">Servlet:SPEC:226</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Using the annotations(@WebServlet, @WebFilter, @WebInitParam, @WebListener, @MultipartConfig)
defined above makes the use of web.xml optional.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:227"></a><font size="1PT">Servlet:SPEC:227</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">However for overriding either the default values or the values set via annotations,
the deployment descriptor is used.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:228"></a><font size="1PT">Servlet:SPEC:228</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">As before, if the metadata-complete element is set to true in the web.xml
descriptor, annotations that specify deployment information present
in the class files and web-fragments bundled in jars will not be processed.
It implies that all the metadata for the application is specified
via the web.xml descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:229"></a><font size="1PT">Servlet:SPEC:229</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">A plain old jar file in the WEB-INF/lib directory with no web-fragment.xml is also considered a fragment. Any annotations specified in it will be processed according to the rules defined in 8.2.3. The container will pick up and use the configuration as per the rules defined below. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:230"></a><font size="1PT">Servlet:SPEC:230</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">A web-fragment.xml may have a top level <name> element of type javaee:java-identifierType.
There can only be one <name> element in a web-fragment.xml. If a <name> element is present,
it must be considered for the ordering of artifacts (unless the duplicate name exception applies, as described below).
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:231"></a><font size="1PT">Servlet:SPEC:231</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">There can only be one <absolute-ordering> element in a web.xml.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:232"></a><font size="1PT">Servlet:SPEC:232</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">The web.xml and WEB-INF/classes MUST be processed before any of the web-fragments
listed in the absolute-ordering element.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:233"></a><font size="1PT">Servlet:SPEC:233</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">Any <name> element direct children of the <absolute-ordering>
MUST be interpreted as indicating the absolute ordering in which those named web-fragments,
which may or may not be present, must be processed.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:234"></a><font size="1PT">Servlet:SPEC:234</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">The <absolute-ordering> element may contain zero or one <others /> element. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:235"></a><font size="1PT">Servlet:SPEC:235</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">If the <absolute-ordering> element does not contain an <others/>
element, any web-fragment not specifically mentioned within <name /> elements
MUST be ignored.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:236"></a><font size="1PT">Servlet:SPEC:236</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">Excluded jars are not scanned for annotated servlets, filters or listeners. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:237"></a><font size="1PT">Servlet:SPEC:237</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">However, if a servlet, filter or listener from an excluded jar is listed in web.xml
or a non-excluded web-fragment.xml, then it's annotations will apply unless otherwise
excluded by metadata-complete.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:238"></a><font size="1PT">Servlet:SPEC:238</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">ServletContextListeners discovered in TLD files of excluded jars are not
able to configure filters and servlets using the programmatic APIs.
Any attempt to do so will result in an IllegalStateException.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:239"></a><font size="1PT">Servlet:SPEC:239</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">If a discovered ServletContainerInitializer is loaded from an excluded jar,
it will be ignored. Irrespective of the setting of metadata-complete,
jars excluded by <absolute-ordering> elements are not scanned
for classes to be handled by any ServletContainerInitializer.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:240"></a><font size="1PT">Servlet:SPEC:240</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">Duplicate name exception: if, when traversing the children of <absolute-ordering>, multiple children with the same <name> element are encountered, only the first such occurrence must be considered. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:241"></a><font size="1PT">Servlet:SPEC:241</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">There can only be one <ordering> element in a web-fragment.xml.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:242"></a><font size="1PT">Servlet:SPEC:242</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">A web-fragment.xml may have an <ordering> element. If so, this element must contain zero or one <before> element and zero or one <after> element. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:243"></a><font size="1PT">Servlet:SPEC:243</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">Duplicate name exception: if, when traversing the web-fragments, multiple members with the same <name> element are encountered, the application must log an informative error message including information to help fix the problem, and must fail to deploy. For example, one way to fix this problem is for the user to use absolute ordering, in which case relative ordering is ignored. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:244"></a><font size="1PT">Servlet:SPEC:244</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT"><before> means the document must be ordered before the document with the name matching what is specified within the nested <name> element. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:245"></a><font size="1PT">Servlet:SPEC:245</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT"><after> means the document must be ordered after the document with the name matching what is specified within the nested <name> element.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:246"></a><font size="1PT">Servlet:SPEC:246</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">There is a special element <others/> which may be included zero or one time within the <before> or <after> element, or zero or one time directly within the <absolute-ordering> element. The
element must be handled as follows.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:246.1"></a><font size="1PT">Servlet:SPEC:246.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">If the <before> element contains a nested
, the document will be moved to the beginning of the list of sorted documents. If there are multiple documents stating <before>
, they will all be at the beginning of the list of sorted documents, but the ordering within the group of such documents is unspecified.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:246.2"></a><font size="1PT">Servlet:SPEC:246.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">If the <after> element contains a nested
, the document will be moved to the end of the list of sorted documents. If there are multiple documents requiring <after>
, they will all be at the end of the list of sorted documents, but the ordering within the group of such documents is unspecified.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:246.3"></a><font size="1PT">Servlet:SPEC:246.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">Within a <before> or <after> element, if an
element is present, but is not the only <name> element within its parent element, the other elements within that parent must be considered in the ordering process.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:246.4"></a><font size="1PT">Servlet:SPEC:246.4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">If the
element appears directly within the <absolute-ordering> element, the runtime must ensure that any web-fragments not explicitly named in the <absolute-ordering> section are included at that point in the processing order. `
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:247"></a><font size="1PT">Servlet:SPEC:247</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">If a web-fragment.xml file does not have an <ordering> or the web.xml does not have an <absolute-ordering> element the artifacts are assumed to not have any ordering dependency. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:248"></a><font size="1PT">Servlet:SPEC:248</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">If the runtime discovers circular references, an informative message must be logged, and the application must fail to deploy. Again, one course of action the user may take is to use absolute ordering in the web.xml. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:249"></a><font size="1PT">Servlet:SPEC:249</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If the order in which the listeners, servlets, filters are invoked is important to an
application then a deployment descriptor must be used.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:250"></a><font size="1PT">Servlet:SPEC:250</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">when using annotations to define the listeners, servlets and filters, the order in which they are invoked is unspecified.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:251"></a><font size="1PT">Servlet:SPEC:251</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The order for listeners, servlets, filters if relevant must be specified in either the web-fragment.xml or the web.xml. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:252"></a><font size="1PT">Servlet:SPEC:252</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> The ordering will be based on the order in which they are defined in the descriptor and on the absolute-ordering element in the web.xml or an ordering element in the web-fragment.xml, if present.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:253"></a><font size="1PT">Servlet:SPEC:253</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Filters that match a request are chained in the order in which they are declared in the web.xml. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:254"></a><font size="1PT">Servlet:SPEC:254</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Servlets are initialized either lazily at request processing time or eagerly during deployment. In the latter case, they are initialized in the order indicated by their load-on-startup elements. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:255"></a><font size="1PT">Servlet:SPEC:255</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The listeners are invoked in the order in which they are declared
in the web.xml as specified below:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:255.1"></a><font size="1PT">Servlet:SPEC:255.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Implementations of jakarta.servlet.ServletContextListener are invoked at their contextInitialized method in the order in which they have been declared, and at their contextDestroyed method in reverse order. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:255.2"></a><font size="1PT">Servlet:SPEC:255.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Implementations of jakarta.servlet.ServletRequestListener are invoked at their requestInitialized method in the order in which they have been declared, and at their requestDestroyed method in reverse order. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:255.3"></a><font size="1PT">Servlet:SPEC:255.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Implementations of jakarta.servlet.http.HttpSessionListener are invoked at their sessionCreated method in the order in which they have been declared, and at their sessionDestroyed method in reverse order. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:255.4"></a><font size="1PT">Servlet:SPEC:255.4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The methods of implementation of
jakarta.servlet.ServletContextAttributeListener,
jakarta.servlet.ServletRequestAttributeListener and
jakarta.servlet.HttpSessionAttributeListener are invoked in
the order in which they are declared when corresponding events are fired.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:256"></a><font size="1PT">Servlet:SPEC:256</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If a servlet is disabled using the enabled element introduced in the web.xml then the servlet will not be available at the url-pattern specified for the servlet. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:257"></a><font size="1PT">Servlet:SPEC:257</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The web.xml of the web application has the highest precedence when resolving conflicts between the web.xml, web-fragment.xml and annotations. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258"></a><font size="1PT">Servlet:SPEC:258</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If metadata-complete is not specified in the descriptors, or is set to false in the deployment descriptor, then the effective metadata for the application is derived by combining the metadata present in the annotations and the descriptors. The rules for merging are specified below -</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.1"></a><font size="1PT">Servlet:SPEC:258.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Configuration settings in web fragments are used to augment those specified in the main web.xml in such a way as if they had been specified in the same web.xml. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.2"></a><font size="1PT">Servlet:SPEC:258.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The order in which configuration settings of web fragments are added to those in the main web.xml is as specified above in Section 8.2.2, Ordering of web.xml and web-fragment.xml on page 8-66 </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.3"></a><font size="1PT">Servlet:SPEC:258.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The metadata-complete attribute when set to true in the main web.xml, is considered complete and scanning of annotations and fragments will not occur at deployment time. The absolute-ordering and ordering elements will be ignored if present. When set to true on a fragment, the metadata-complete attribute applies only to scanning of annotations in that particular jar.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.4"></a><font size="1PT">Servlet:SPEC:258.4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Web fragments are merged into the main web.xml unless the metadata-complete is set to true. The merging takes place after annotation processing on the corresponding fragment.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.5"></a><font size="1PT">Servlet:SPEC:258.5</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The following are considered configuration conflicts when augmenting a web.xml with web fragments: </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.5.1"></a><font size="1PT">Servlet:SPEC:258.5.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Multiple <init-param> elements with the same <param-name> but different <param-value> </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.5.2"></a><font size="1PT">Servlet:SPEC:258.5.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Multiple <mime-mapping> elements with the same <extension> but different <mime-type> </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.6"></a><font size="1PT">Servlet:SPEC:258.6</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The above configuration conflicts are resolved as follows</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.6.1"></a><font size="1PT">Servlet:SPEC:258.6.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Configuration conflicts between the main web.xml and a web fragment are resolved such that the configuration in the web.xml takes precedence. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.6.2"></a><font size="1PT">Servlet:SPEC:258.6.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Configuration conflicts between two web fragments, where the element at the center of the conflict is not present in the main web.xml, will result in an error. An informative message must be logged, and the application must fail to deploy</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7"></a><font size="1PT">Servlet:SPEC:258.7</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">After the above conflicts have been resolved, these additional rules are applied:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.1"></a><font size="1PT">Servlet:SPEC:258.7.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Elements that may be declared any number of times are additive across the web-fragments in the resulting web.xml. For example, <context-param> elements with different <param-name> are additive.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.2"></a><font size="1PT">Servlet:SPEC:258.7.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Elements that may be declared any number of times, if specified in the web.xml overrides the values specified in the web-fragments with the same name.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.3"></a><font size="1PT">Servlet:SPEC:258.7.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If an element with a minimum occurrence of zero, and a maximum occurrence of one, is present in a web fragment, and missing in the main web.xml, the main web.xml inherits the setting from the web fragment. If the element is present in both the main web.xml and the web fragment, the configuration setting in the main web.xml takes precedence. For example, if both the main web.xml and a web fragment declare the same servlet, and the servlet declaration in the web fragment specifies a <load-on-startup> element, whereas the one in the main web.xml does not, then the <load-on-startup> element from the web fragment will be used in the merged web.xml. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.4"></a><font size="1PT">Servlet:SPEC:258.7.4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">It is considered an error if an element with a minimum occurrence of zero, and a maximum occurrence of one, is specified differently in two web fragments, while absent from the main web.xml. For example, if two web fragments declare the same servlet, but with different <load-on-startup> elements, and the same servlet is also declared in the main web.xml, but without any <load-on-startup>, then an error must be reported. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.5"></a><font size="1PT">Servlet:SPEC:258.7.5</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"><welcome-file> declarations are additive. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.6"></a><font size="1PT">Servlet:SPEC:258.7.6</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"><servlet-mapping> elements with the same <servlet-name> are additive across web-fragments. <servlet-mapping> specified in the web.xml overrides values specified in the web-fragments with the same <servlet-name>. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.7"></a><font size="1PT">Servlet:SPEC:258.7.7</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"><filter-mapping> elements with the same <filter-name> are add itive across web-fragments. <filter-mapping> specified in the web.xml overrides values specified in the web-fragments with the same <filter-name>.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.8"></a><font size="1PT">Servlet:SPEC:258.7.8</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Multiple <listener> elements with the same <listener-class> are treated as a single <listener> declaration </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.9"></a><font size="1PT">Servlet:SPEC:258.7.9</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The web.xml resulting from the merge is considered <distributable> only if all its web fragments are marked as <distributable> as well. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.10"></a><font size="1PT">Servlet:SPEC:258.7.10</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">The top-level <icon> and it's children elements, <display-name>>, and <description> elements of a web fragment are ignored.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.7.11"></a><font size="1PT">Servlet:SPEC:258.7.11</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">jsp-property-group is additive. It is recommended that jsp-config element use the url-pattern as opposed to extension mappings when bundling static resources in the META-INF/resources directory of a jar file. Further more JSP resources for a fragment should be in a sub-directory same as the fragment name, if there exists one. This helps prevent a web-fragment's jsp-property-group from affecting the JSPs in the main docroot of the application and the jsp-property-group from affecting the JSPs in a fragment's META-INF/resources directory.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.8"></a><font size="1PT">Servlet:SPEC:258.8</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> For all the resource reference elements (env-entry, ejb-ref, ejb-local-ref, service-ref, resource-ref, resource-env-ref, message-destination-ref, persistence-context-ref and persistence-unit-ref) the following rules apply:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.8.1"></a><font size="1PT">Servlet:SPEC:258.8.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> If any resource reference element is present in a web fragment, and is missing in the main web.xml, the main web.xml inherits the value from the web fragment. If the element is present in both the main web.xml and the web fragment, with the same name, the web.xml takes precedence. None of the child elements from the fragment are merged into the main web.xml except for the injection-target as specified below. For example, if both the main web.xml and a web fragment declare a <resource-ref> with the same <resource-ref-name>, the <resource-ref> from the web.xml will be used without any child elements being merged from the fragment except <injection-target> as described below. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.8.2"></a><font size="1PT">Servlet:SPEC:258.8.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> If a resource reference element is specified in two fragments, while absent from the main web.xml, and all the attributes and child elements of the resource reference element are identical, the resource reference will be merged into the main web.xml. It is considered an error if a resource reference element has the same name specified in two fragments, while absent from the main web.xml and the attributes and child elements are not identical in the two fragments. An error must be reported and the application MUST fail to deploy. For example, if two web fragments declare a <resource-ref> with the same <resource-ref-name> element but the type in one is specified as javax.sql.DataSource while the type in the other is that of a JavaMail resource, it is an error and the application will fail to deploy </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.8.3"></a><font size="1PT">Servlet:SPEC:258.8.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">For resource reference element with the same name <injection-target> elements from the fragments will be merged into the main web.xml. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.9"></a><font size="1PT">Servlet:SPEC:258.9</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">In addition to the merging rules for web-fragment.xml defined above, the following rules apply when using the resource reference annotations (@Resource, @Resources, @EJB, @EJBs, @WebServiceRef, @WebServiceRefs, @PersistenceContext, @PersistenceContexts,@PersistenceUnit, and @PersistenceUnits)</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.9.1"></a><font size="1PT">Servlet:SPEC:258.9.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If a resource reference annotation is applied on a class, it is equivalent to defining a resource, however it is not equivalent to defining an injection-target. The rules above apply for injection-target element in this case.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.9.2"></a><font size="1PT">Servlet:SPEC:258.9.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If a resource reference annotation is used on a field it is equivalent to defining the injection-target element in the web.xml. However if there is no injection-target element in the descriptor then the injection-target from the fragments will still be merged into the web.xml as defined above. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.9.3"></a><font size="1PT">Servlet:SPEC:258.9.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If on the other hand there is an injection-target in the main web.xml and there is a resource reference annotation with the same resource name, then it is considered an override for the resource reference annotation. In this case since there is an injection-target specified in the descriptor, the rules defined above would apply in addition to overriding the value for the resource reference annotation. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.10"></a><font size="1PT">Servlet:SPEC:258.10</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> If a data-source element is specified in two fragments, while absent from the main web.xml, and all the attributes and child elements of the data-source element are identical, the data-source will be merged into the main web.xml. It is considered an error if a data-source element has the same name specified in two fragments, while absent from the main web.xml and the attributes and child elements are not identical in the two fragments. In such a case an error must be reported and the application MUST fail to deploy. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.11"></a><font size="1PT">Servlet:SPEC:258.11</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If the main web.xml does not have any <post-construct> element specified and web-fragments have specified <post-construct> then the <post-construct> elements from the fragments will be merged into the main web.xml. However if in the main web.xml at least one <post-construct> element is specified then the <post-construct> elements from the fragment will not be merged. It is the responsibility of the author of the web.xml to make sure that the <post-construct> list is complete.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.12"></a><font size="1PT">Servlet:SPEC:258.12</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">If the main web.xml does not have any <pre-destroy> element specified and web-fragments have specified <pre-destroy> then the <pre-destroy> elements from the fragments will be merged into the main web.xml. However if in the main web.xml at least one <pre-destroy> element is specified then the <pre-destroy> elements from the fragment will not be merged. It is the responsibility of the author of the web.xml to make sure that the <pre-destroy> list is complete.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.13"></a><font size="1PT">Servlet:SPEC:258.13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">After processing the web-fragment.xml, annotations from the corresponding fragment are processed to complete the effective metadata for the fragment before processing the next fragment. The following rules are used for processing annotations:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.14"></a><font size="1PT">Servlet:SPEC:258.14</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">Any metadata specified via an annotation that isn't already present in the descriptor will be used to augment the effective descriptor. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.14.1"></a><font size="1PT">Servlet:SPEC:258.14.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Configuration specified in the main web.xml or a web fragment takes precedence over the configuration specified via annotations. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.14.2"></a><font size="1PT">Servlet:SPEC:258.14.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">For a servlet defined via the @WebServlet annotation, to override values via the descriptor, the name of the servlet in the descriptor MUST match the name of the servlet specified via the annotation (explicitly specified or the default name, if one is not specified via the annotation). </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.14.3"></a><font size="1PT">Servlet:SPEC:258.14.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Init params for servlets and filters defined via annotations, will be overridden in the descriptor if the name of the init param exactly matches the name specified via the annotation. Init params are additive between the annotations and descriptors. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.14.4"></a><font size="1PT">Servlet:SPEC:258.14.4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> url-patterns, when specified in a descriptor for a given servlet name overrides the url patterns specified via the annotation.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.14.5"></a><font size="1PT">Servlet:SPEC:258.14.5</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> For a filter defined via the @WebFilter annotation, to override values via the descriptor, the name of the filter in the descriptor MUST match the name of the filter specified via the annotation (explicitly specified or the default name, if one is not specified via the annotation). </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.14.6"></a><font size="1PT">Servlet:SPEC:258.14.6</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT"> url-patterns to which a filter is applied, when specified in a descriptor for a given filter name overrides the url patterns specified via the annotation. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:258.14.7"></a><font size="1PT">Servlet:SPEC:258.14.7</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.3</font></TD><TD align="left" valign="center"><font size="1PT">DispatcherTypes to which a filter applies, when specified in a descriptor for a given filter name overrides the DispatcherTypes specified via the annotation. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:259"></a><font size="1PT">Servlet:SPEC:259</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">In addition to supporting fragments and use of annotations one of the requirements is
that not only we be able to plug-in things that are bundled in the WEB-INF/lib
but also plugin shared copies of frameworks - including being able to plug-in
to the web container things like JAX-WS, JAX-RS and JSF that build on top of the web container.
The ServletContainerInitializer allows handling such a use case as described below.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:259.1"></a><font size="1PT">Servlet:SPEC:259.1</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">The ServletContainerInitializer class is looked up via the jar services API.
For each application, an instance of the ServletContainerInitializer is created
by the container at application startup time.
The framework providing an implementation of the ServletContainerInitializer MUST bundle
in the META-INF/services directory of the jar file a file called
jakarta.servlet.ServletContainerInitializer, as per the jar services API,
that points to the implementation class of the ServletContainerInitializer.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:259.2"></a><font size="1PT">Servlet:SPEC:259.2</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">In addition to the ServletContainerInitializer we also have an annotation - HandlesTypes.
The HandlesTypes annotation on the implementation of the ServletContainerInitializer is used
to express interest in classes that may have anotations (type, method or field level annotations)
specified in the value of the HandlesTypes or if it extends / implements one those classes
anywhere in the class' super types.
The HandlesTypes annotation is applied irrespective of the setting of metadata-complete.
The container uses the HandlesTypes annotation to determine when to invoke the initializer's
onStartup method.
When examining the classes of an application to see if they match any of the criteria
specified by the HandlesTypes annotation of a ServletContainerInitializer,
the container may run into class loading problems if one or more of the application's
optional JAR files are missing.
Since the container is not in a position to decide whether these types of class
loading failures will prevent the application from working correctly,
it must ignore them, while at the same time providing a configuration option that would log them.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:259.3"></a><font size="1PT">Servlet:SPEC:259.3</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">If an implementation of ServletContainerInitializer does not have the @HandlesTypes annotation,
or if there are no matches to any of the HandlesType specified,
then it will get invoked once for every application with null as the value of the Set.
This will allow for the initializer to determine based on the resources available
in the application whether it needs to initialize a servet / filter or not.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:259.4"></a><font size="1PT">Servlet:SPEC:259.4</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">The onStartup method of the ServletContainerInitializer will be invoked when the application is coming up before any of the listener's events are fired. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:259.5"></a><font size="1PT">Servlet:SPEC:259.5</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">The ServletContainerInitializer's onStartup method get's a Set of Classes that either extend / implement the classes that the initializer expressed interest in or if it is annotated with any of the classes specified via the @HandlesTypes annotation. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:259.6"></a><font size="1PT">Servlet:SPEC:259.6</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">The framework jar file can also be bundled in WEB-INF/lib directory of the war file.
If the ServletContainerInitializer is bundled in a JAR file inside the WEB-INF/lib
directory of an application, it's onStartup method will be invoked only once
during the startup of the bundling application. If, on the other hand, the ServletContainerInitialzer is bundled
in a JAR file outside of the WEB-INF/lib directory, but still discoverable
by the runtime's service provider lookup mechanism,
it's onStartup method will be invoked every time an application is started.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:259.7"></a><font size="1PT">Servlet:SPEC:259.7</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">Implementations of the ServletContainerInitializer interface will be discovered by the runtime's service lookup mechanism or a container specific mechanism that is semantically equivalent to it. In either case, ServletContainerInitializer services from web fragment JAR files that are excluded from an absolute ordering MUST be ignored, and the order in which these services are discovered MUST follow the application's class loading delegation model.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:260"></a><font size="1PT">Servlet:SPEC:260</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">The ServletContainerInitializer and programmatic registration features make it possible to provide a clear separation of responsibilities between the Servlet and JSP containers, by making the Servlet container responsible for parsing only web.xml and web-fragment.xml resources, and delegating the parsing of Tag Library Descriptor (TLD) resources to the JSP container. `</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:261"></a><font size="1PT">Servlet:SPEC:261</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">Previously, a web container had to scan TLD resources for any listener declarations. With Servlet 3.0, this responsibility may be delegated to the JSP container. A JSP container that is embedded in a Servlet 3.0 compliant Servlet container may provide its own ServletContainerInitializer implementation, search the ServletContext passed to its onStartup method for any TLD resources, scan those resources for listener declarations, and register the corresponding listeners with the ServletContext. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:262"></a><font size="1PT">Servlet:SPEC:262</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">In addition, prior to Servlet 3.0, a JSP container used to have to scan an application's deployment descriptor for any jsp-config related configuration. With Servlet 3.0, the Servlet container must make available, via the ServletContext.getJspConfigDescriptor method, any jsp-config related configuration from the application's web.xml and web-fragment.xml deployment descriptors. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:263"></a><font size="1PT">Servlet:SPEC:263</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">Any ServletContextListeners that were discovered in a TLD and registered programmatically are limited in the functionality they provide. Any attempt to call a ServletContext API method on them that was added in Servlet 3.0 will result in an UnsupportedOperationException. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:264"></a><font size="1PT">Servlet:SPEC:264</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">In addition, a Servlet 3.0 compliant Servlet container must provide a ServletContext attribute with name jakarta.servlet.context.orderedLibs, whose value (of type java.util.List<java.lang.String>) contains the list of names of JAR files in the WEB-INF/lib directory of the application represented by the ServletContext, ordered by their web fragment names (with possible exclusions if fragment JAR files have been excluded from absolute-ordering), or null if the application does not specify any absolute or relative ordering. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:265"></a><font size="1PT">Servlet:SPEC:265</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">Web applications can include both annotations and the web.xml / web-fragment.xml deployment descriptors. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:266"></a><font size="1PT">Servlet:SPEC:266</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">. If there is no deployment descriptor, or there is one but does not have the metadata-complete set to true, web.xml, web-fragment.xml and annotations if used in the application must be processed.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:267"></a><font size="1PT">Servlet:SPEC:267</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">The following table (Table 8-1) describes whether or not to process annotations and web.xml fragments. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:75"></a><font size="1PT">Servlet:SPEC:75</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The Container provider must ensure that the dispatch of the request to a target servlet
occurs in the same thread of the same VM as the original request.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:192"></a><font size="1PT">Servlet:SPEC:192</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">The include method of the RequestDispatcher interface may be called at any time. The target servlet of the include method has access to all aspects of the request object, but its use of the response object is more limited.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:192.1"></a><font size="1PT">Servlet:SPEC:192.1</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">It can only write information to the ServletOutputStream or Writer of the response object</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:192.2"></a><font size="1PT">Servlet:SPEC:192.2</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">commit a response by writing content past the end of the response buffer</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:192.3"></a><font size="1PT">Servlet:SPEC:192.3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">commit a response by explicitly calling the flushBuffer method of the ServletResponse interface.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:192.4"></a><font size="1PT">Servlet:SPEC:192.4</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">It cannot set headers or call any method that affects the headers of the response, with the exception of the HttpServletRequest. getSession() and HttpServletRequest.getSession(boolean) methods. Any attempt to set the headers must be ignored, and any call to HttpServletRequest. getSession() or HttpServletRequest.getSession( boolean) that would require adding a Cookie response header must throw an IllegalStateException if the response has been committed.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:76"></a><font size="1PT">Servlet:SPEC:76</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">Except for servlets obtained by using the getNamedDispatcher method, a servlet being used from within an include has access to the path by which it was invoked. The following request attributes are set:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:76.1"></a><font size="1PT">Servlet:SPEC:76.1</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">'jakarta.servlet.include.request_uri' which is the URI by which it was invoked.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:76.2"></a><font size="1PT">Servlet:SPEC:76.2</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">'jakarta.servlet.include.context_path' which is the context path portion of the request URI by which it was invoked.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:76.3"></a><font size="1PT">Servlet:SPEC:76.3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">'jakarta.servlet.include.servlet_path' the servlet-path portion of the request URI by which it was invoked.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:76.4"></a><font size="1PT">Servlet:SPEC:76.4</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">'jakarta.servlet.include.path_info' the path-info portion of the request URI by which it was invoked.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:76.5"></a><font size="1PT">Servlet:SPEC:76.5</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">'jakarta.servlet.include.query_string' the query string portion of the request URI by which it was invoked.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:77"></a><font size="1PT">Servlet:SPEC:77</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">If output data exists in the response buffer that has not been committed, the content must be cleared before the target's service method is called.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:78"></a><font size="1PT">Servlet:SPEC:78</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">The path elements of the request object exposed to the target servlet must reflect the path used to obtain the RequestDispatcher.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:79"></a><font size="1PT">Servlet:SPEC:79</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">If the RequestDispatcher was obtained through getNamedDispatcher the path elements of the request object must reflect those of the original request.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:80"></a><font size="1PT">Servlet:SPEC:80</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">Before the forward method of the RequestDispatcher interface returns without exception,
the response content must be sent and committed, and closed by the servlet container,
unless the request was put into the asynchronous mode
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:81"></a><font size="1PT">Servlet:SPEC:81</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT">The request dispatching mechanism is responsible for aggregating query string parameters when forwarding or including requests.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">deprecated</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:180"></a><font size="1PT">Servlet:SPEC:180</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">Except for servlets obtained by using the getNamedDispatcher method, a servlet that has been invoked by another servlet using the forward method of RequestDispatcher has access to the path of the original request. The values of these attributes must be equal to the return values of the HttpServletRequest methods getRequestURI, getContextPath, getServletPath, getPathInfo, getQueryString respectively, invoked on the request object passed to the first servlet object in the call chain that received the request from the client. These attributes are accessible from the forwarded servlet via the getAttribute method on the request object. Note that these attributes must always reflect the information in the original request even under the situation that multiple forwards and subsequent includes are called. If the forwarded servlet was obtained by using the getNamedDispatcher method, these attributes must not be set.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:180.1"></a><font size="1PT">Servlet:SPEC:180.1</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.request_uri</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:180.2"></a><font size="1PT">Servlet:SPEC:180.2</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.context_path</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:180.3"></a><font size="1PT">Servlet:SPEC:180.3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.servlet_path</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:180.4"></a><font size="1PT">Servlet:SPEC:180.4</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.path_info</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:180.5"></a><font size="1PT">Servlet:SPEC:180.5</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.query_string</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:181"></a><font size="1PT">Servlet:SPEC:181</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">If the forwarded servlet was obtained by using the getNamedDispatcher method, these attributes must not be set.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:181.1"></a><font size="1PT">Servlet:SPEC:181.1</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.request_uri</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:181.2"></a><font size="1PT">Servlet:SPEC:181.2</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.context_path</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:181.3"></a><font size="1PT">Servlet:SPEC:181.3</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.servlet_path</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:181.4"></a><font size="1PT">Servlet:SPEC:181.4</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.path_info</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:181.5"></a><font size="1PT">Servlet:SPEC:181.5</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.forward.query_string</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:82"></a><font size="1PT">Servlet:SPEC:82</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">If the servlet that is the target of a request dispatcher throws a runtime exception or a checked exception of type ServletException or IOException, it may be propagated to the calling servlet.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:83"></a><font size="1PT">Servlet:SPEC:83</font></TD><TD align="center" valign="center"><font size="1PT">9</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">All other exceptions (not a runtime, ServletException, or IOException) should be wrapped as ServletExceptions with the root cause the original exception before propagation.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:84"></a><font size="1PT">Servlet:SPEC:84</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">An instance of a web application, by default, must run on one VM at any one time.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:85"></a><font size="1PT">Servlet:SPEC:85</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">An application marked as distributable must obey a more restrictive set of rules than is required of a normal web application (the rules are set through out this list.)</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:86"></a><font size="1PT">Servlet:SPEC:86</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The servlet container must enforce a one to one correspondence between a web application and a ServletContext. A ServletContext object provides a servlet with its view of the application.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:87"></a><font size="1PT">Servlet:SPEC:87</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">Since the context path of an application determines the URL namespace of the context of the web application, web containers must reject web application defining a context path could cause potential conflicts in this URL namespace.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:88"></a><font size="1PT">Servlet:SPEC:88</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">Since request are matched to resources case sensitively, this determination of potential context path namespace conflicts must be performed case sensitively as well.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:89"></a><font size="1PT">Servlet:SPEC:89</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The WEB-INF node (or directory) of a web application is not part of the public document tree of the application. Any requests to access the resources in /WEB-INF directory must be returned with a SC_NOT_FOUND(404) response.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:90"></a><font size="1PT">Servlet:SPEC:90</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The contents of /WEB-INF are visible to Servlets through the use of ServletContext.getResource or ServletContext.getSourceAsStream.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:91"></a><font size="1PT">Servlet:SPEC:91</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The web applcation classloader must load classes from the WEB-INF/ classes directory first, and then from the library JARs in the WEB-INF directory.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:92"></a><font size="1PT">Servlet:SPEC:92</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">When web applications are packaged in a WAR file (Web ARchive file), a META-INF directory will be present which contains information useful to Java Archive tools.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:92.1"></a><font size="1PT">Servlet:SPEC:92.1</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">Any requests to the META-INF directory of a packaged web application will be returned with a SC_NOT_FOUND(404) response.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:92.2"></a><font size="1PT">Servlet:SPEC:92.2</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The content of the META-INF directory of a packaged web application is accessible to servlets using the getResource and getResourceAsStream methods of the ServletContext.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:93"></a><font size="1PT">Servlet:SPEC:93</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.1</font></TD><TD align="left" valign="center"><font size="1PT">Jakarta EE technology-compliant containers are required to provide a mechanism by which a deployer can learn what JAR files containing resources and code are available for the Web application.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:97"></a><font size="1PT">Servlet:SPEC:97</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.1</font></TD><TD align="left" valign="center"><font size="1PT">Containers should provide a convenient procedure for editing and configuring library files or extensions.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:94"></a><font size="1PT">Servlet:SPEC:94</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.1</font></TD><TD align="left" valign="center"><font size="1PT">During deployment of the Web application, the Web container must make the correct versions of the extensions available to the application following the rules defined by the Optional Package Versioning mechanism (https://docs.oracle.com/javase/8/docs/technotes/guides/extensions/extensions.html).</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:95"></a><font size="1PT">Servlet:SPEC:95</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.1</font></TD><TD align="left" valign="center"><font size="1PT">Web containers must also be able to recognize declared dependencies expressed in the manifest entry of any of the library JARs under the WEB-INF/lib entry in a WAR.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:96"></a><font size="1PT">Servlet:SPEC:96</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.1</font></TD><TD align="left" valign="center"><font size="1PT">If a web container is not able to satisfy the dependencies declared via manifest files, it should reject the application with an informative error message.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:98"></a><font size="1PT">Servlet:SPEC:98</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">The classloader that a container uses to load a servlet in a WAR must allow the developer to load any resources contained in library JARs within the WAR following normal Java SE semantics using getResource.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:99"></a><font size="1PT">Servlet:SPEC:99</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">As described in the Jakarta EE license agreement, servlet containers that are not part of a Jakarta EE product should not allow the application to override Java SE platform classes, such as those in the java.* and javax.* namespaces, that Java SE does not allow to be modified.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:99.1"></a><font size="1PT">Servlet:SPEC:99.1</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">Also, servlet containers that are part of a Jakarta EE product should not allow the application to override Java SE or Jakarta EE platform classes, such as those in the java.* and javax.* namespaces, that either Java SE or Jakarta EE do not allow to be modified.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:99.2"></a><font size="1PT">Servlet:SPEC:99.2</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">The class loader that a container uses to load a servlet in a WAR must allow the developer to load any resources contained in library JARs within the WAR following normal Java SE semantics using getResource.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:99.3"></a><font size="1PT">Servlet:SPEC:99.3</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">It is recommended also that the application class loader be implemented so that classes and resources packaged within the WAR are loaded in preference to classes and resources residing in container-wide library JARs.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:100"></a><font size="1PT">Servlet:SPEC:100</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">It is recommended that the loader not allow servlets in the WAR access to the web container's implementation classes.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:101"></a><font size="1PT">Servlet:SPEC:101</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">7.2</font></TD><TD align="left" valign="center"><font size="1PT">It is recommended also that the application classloader be implemented so that classes and resources packaged within the WAR are loaded in preference to classes and resources residing in container-wide library JARs.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:102"></a><font size="1PT">Servlet:SPEC:102</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">A server should be able to replace an application with a new version without restarting the container. When an application is replaced, the container should provide a robust method for preserving session data within that application.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:103"></a><font size="1PT">Servlet:SPEC:103</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">A web application must be able to specify that when errors occur other resources in the application are used to provide the content body of the error response.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104"></a><font size="1PT">Servlet:SPEC:104</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">If the location of the error handler is a servlet or JSP page, then:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.1"></a><font size="1PT">Servlet:SPEC:104.1</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The original unwrapped request and response objects created by the container are passed to the servlet or JSP page.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.2"></a><font size="1PT">Servlet:SPEC:104.2</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The response setStatus method is disabled and ignored if called.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.3"></a><font size="1PT">Servlet:SPEC:104.3</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The request path and attributes are set as if a RequestDispatcher.forward to the error resource has been performed.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.3.1"></a><font size="1PT">Servlet:SPEC:104.3.1</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The request attribute 'jakarta.servlet.error.status_code' of type 'java.lang.Integer' will be set containing the HTTP status code of the error condition.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.3.2"></a><font size="1PT">Servlet:SPEC:104.3.2</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The request attribute 'jakarta.servlet.error.exception_type' of type 'java.lang.Class' will be set if the error page was invoked due to an uncaught exception.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.3.3"></a><font size="1PT">Servlet:SPEC:104.3.3</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The request attribute 'jakarta.servlet.error.message' of type 'java.lang.String' will be set if the error page was invoked due to an uncaught exception.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.3.4"></a><font size="1PT">Servlet:SPEC:104.3.4</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The 'jakarta.servlet.error.exception' attribute of type 'java.lang.Throwable' will be set if the error page was invoked due to an uncaught exception.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.3.5"></a><font size="1PT">Servlet:SPEC:104.3.5</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The 'jakarta.servlet.error.request_uri' attribute of type 'java.lang.String' will contain the URI of the offending resource.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:104.3.6"></a><font size="1PT">Servlet:SPEC:104.3.6</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.1</font></TD><TD align="left" valign="center"><font size="1PT">The 'jakarta.servlet.error.servlet_name' attribute of type 'java.lang.String' will contain the logical name of the servlet in which the error occurred.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:105"></a><font size="1PT">Servlet:SPEC:105</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">If the sendError method is called on the response, the container consults the list of error page declarations for the web application that use the status-code syntax and attempts a match. If there is a match, the container returns the resource as indicated by the location entry.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:106"></a><font size="1PT">Servlet:SPEC:106</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">In the case where the container is matching error pages based on the exception-type element, a match results in the container returning the resource indicated in the location entry. The closest match in the class hierarchy wins.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:107"></a><font size="1PT">Servlet:SPEC:107</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">If no error-page declaration containing an exception-type fits using the class-hierarchy match, and the exception throws is a ServletException or subclass thereof the container extraces the wrapped exception, as defined by the ServletException.getRootCause method and a second pass is made of the error page declarations, again attempting the match against the error page declearations, but using the wrapped exception.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:108"></a><font size="1PT">Servlet:SPEC:108</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">Error-page declarations using the exception-type element in the deployment descriptor must be unique up to the class name of the exception type.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:109"></a><font size="1PT">Servlet:SPEC:109</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">Error page declarations using the status-code elements must be unique in the deployment descriptor up to the status-code.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:110"></a><font size="1PT">Servlet:SPEC:110</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">The error page mechanism does not intervene when errors occur when invoked using the RequestDispatcher or Filter.doFilter method. In this way, a filter or servlet using the RequestDispatcher has the opportunity to handle errors generated.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:111"></a><font size="1PT">Servlet:SPEC:111</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">If a servlet generates an error that is not handled by the error page mechanism as described above, the container must ensure to send a response with status 500.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:112"></a><font size="1PT">Servlet:SPEC:112</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">The default servlet and container will use the sendError method to send 4xx and 5xx responses so that the error mechanism may be invoked.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:113"></a><font size="1PT">Servlet:SPEC:113</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">The default servlet and container will use the setStatus method to send 2xx and 3xx responses to bypass the error mechanism</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:114"></a><font size="1PT">Servlet:SPEC:114</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">If a web container receives a valid partial request, the web container must examine the welcome files list, which is an ordered list of partial URLs, with no leading or trailing slash, and append the each welcome file to the partial URI in the order it was defined to find a match. The web container must send the request to the first resource in the WAR that matches.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:115"></a><font size="1PT">Servlet:SPEC:115</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">If no welcome file match is found, the container may handle the request as it sees fit.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:116"></a><font size="1PT">Servlet:SPEC:116</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">Jakarta EE compliant servlet containers are required to support the following elements of the web deployment descriptor for specifying information allowing a servlet to obtain references to resources and enterprise beans. The deployment elements that contain this information are:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:116.1"></a><font size="1PT">Servlet:SPEC:116.1</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">env-entry</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:116.2"></a><font size="1PT">Servlet:SPEC:116.2</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">ejb-ref</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:116.3"></a><font size="1PT">Servlet:SPEC:116.3</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">ejb-local-ref</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:116.4"></a><font size="1PT">Servlet:SPEC:116.4</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">resource-env-ref</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:116.5"></a><font size="1PT">Servlet:SPEC:116.5</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">resource-ref</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:117"></a><font size="1PT">Servlet:SPEC:117</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">If the standalone container does not support these lookup facilities, the container should provide a warning upon deployment of an application that has dependencies on such resources.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:118"></a><font size="1PT">Servlet:SPEC:118</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">Servlet containers that are part of a Jakarta EE technology compliant implementation must support lookups of such objects and calls made to those objects when performed on a thread managed by the servlet container.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:119"></a><font size="1PT">Servlet:SPEC:119</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="left" valign="center"><font size="1PT">Such servlet containers should support this lookup behavior when performed on threads created by the developer, but are not required to do so.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:182"></a><font size="1PT">Servlet:SPEC:182</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="left" valign="center"><font size="1PT"><![CDATA[When a web application is deployed into a container, the following steps must be performed, in this order, before the web application begins processing client requests.
1. Instantiate an instance of each event listener identified by a <listener> element in the deployment descriptor.
2. For instantiated listener instances that implement ServletContextListener, call the contextInitialized() method.
3. Instantiate an instance of each filter identified by a <filter>> element in the deployment descriptor and call each filter instances init() method.
4. Instantiate an instance of each servlet identified by a <servlet> element that includes a <load-on-startup> element in the order defined by the load-onstartup element values, and call each servlet instances init() method.]]>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:201"></a><font size="1PT">Servlet:SPEC:201</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="left" valign="center"><font size="1PT">A web application is NOT required to contain a web.xml if it does NOT contain any Servlet,
Filter, or Listener components. In other words an application containing only static files
or JSP pages does not require a web.xml to be present.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:120"></a><font size="1PT">Servlet:SPEC:120</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">Each listener class specified in the deployment descriptor must have a public constructor taking no arguments.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:121"></a><font size="1PT">Servlet:SPEC:121</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">3.2</font></TD><TD align="left" valign="center"><font size="1PT">Listeners will be invoked in the order that they are defined in the deployment descriptor.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:122"></a><font size="1PT">Servlet:SPEC:122</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">3.3</font></TD><TD align="left" valign="center"><font size="1PT">The Web container creates an instance of each listener class and registers it
for event notifications prior to the processing of the first request by the application
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:123"></a><font size="1PT">Servlet:SPEC:123</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">3.3</font></TD><TD align="left" valign="center"><font size="1PT">The Web container registers the listener instances according to the interfaces
they implement and the order in which they appear in the deployment descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:124"></a><font size="1PT">Servlet:SPEC:124</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">3.3</font></TD><TD align="left" valign="center"><font size="1PT">During Web application execution, listeners corresponding to given events are
invoked in the order of their registration.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:125"></a><font size="1PT">Servlet:SPEC:125</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">3.4</font></TD><TD align="left" valign="center"><font size="1PT">On application shutdown, listeners are notified in reverse order to their declarations with notifications to session listeners preceeding notifications to context listeners. Session listeners must be notified of session invalidations prior to context listeners being notified of application shutdown.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:126"></a><font size="1PT">Servlet:SPEC:126</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The container is required to complete instantiation of the listener classes in a web application prior to the start of execution of the first request into the application.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:127"></a><font size="1PT">Servlet:SPEC:127</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The container must maintain a reference to each listener instance until the last request is serviced for the web application.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:128"></a><font size="1PT">Servlet:SPEC:128</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">The container must allow unhandled exceptions to be handled by the error page mechanism described in Section SRV.9.9, "Error Handling". If there is no error page specified for those exceptions, the container must ensure to send a response back with status 500. In this case no more listeners under that event are called.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:129"></a><font size="1PT">Servlet:SPEC:129</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">In cases where it is not possible to handle an Exception in application code (ex. an Exception occuring during initialization of a ContextListener), the container may response to all subsequent requests with an HTTP status code of 500 to indicate application error.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:130"></a><font size="1PT">Servlet:SPEC:130</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">In distributed web containers, HttpSession instances are scoped to the particular VM services session requests, and the ServletContext object is scoped to the web container's VM.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:131"></a><font size="1PT">Servlet:SPEC:131</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">Distributed containers are not required to propogate either servlet context events or HttpSession events to other VMs.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:132"></a><font size="1PT">Servlet:SPEC:132</font></TD><TD align="center" valign="center"><font size="1PT">11</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">Listener class instances are scoped to one per deployment descriptor declaration per Java virtual machine.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:133"></a><font size="1PT">Servlet:SPEC:133</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">Upon receipt of a client request, the Web container determines the Web application to which to forward it. The Web application selected must have the longest context path that matches the start of the request URL. The matched part of the URL is the context path when mapping to servlets.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:134"></a><font size="1PT">Servlet:SPEC:134</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">The Web container next must locate the servlet to process the request using the path mapping procedure described below. The path used for mapping to a servlet is the request URL from the request object minus the context path and the path parameters. The URL path mapping rules below are used in order. The first successful match is used with no further matches attempted</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:134.1"></a><font size="1PT">Servlet:SPEC:134.1</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">The container will try to find an exact match of the path of the request to the path of the servlet. A successful match selects the servlet.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:134.2"></a><font size="1PT">Servlet:SPEC:134.2</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">The container will recursively try to match the longest path-prefix: This is done by stepping down the path tree a directory at a time, using the '/' character as a path separator. The longest match determines the servlet selected.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:134.3"></a><font size="1PT">Servlet:SPEC:134.3</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">If the last segment in the URL path contains an extension (e.g. .jsp), the servlet container will try to match a servlet that handles requests for the extension. An extension is defined as the part of the last segment after the last '.' character.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:134.4"></a><font size="1PT">Servlet:SPEC:134.4</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">If neither the previous three rules result in a servlet match, the container will attempt to serve content appropriate for the resource requested. If a "default" servlet is defined for the applications, it will be used.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:134.5"></a><font size="1PT">Servlet:SPEC:134.5</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">The container must use case-sensitive string comparisons for matching.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:220"></a><font size="1PT">Servlet:SPEC:220</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">In the Web application deployment descriptor, the following syntax is used to define mappings</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:220.1"></a><font size="1PT">Servlet:SPEC:220.1</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">A string beginning with a / character and ending with a /* suffix is used for path mapping.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:220.2"></a><font size="1PT">Servlet:SPEC:220.2</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">A string beginning with a *. prefix is used as an extension mapping.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:220.3"></a><font size="1PT">Servlet:SPEC:220.3</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The empty string ("") is a special URL pattern that exactly maps to the application's context root, i.e., requests of the form http://host:port/<contextroot>/. In this case the path info is / and the servlet path and context path is empty string "".</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:220.4"></a><font size="1PT">Servlet:SPEC:220.4</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">A string containing only the character / indicates the "default" servlet of the application. In this case the servlet path is the request URI minus the context path and the path info is null.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:220.5"></a><font size="1PT">Servlet:SPEC:220.5</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">All other strings are used for exact matches only.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:135"></a><font size="1PT">Servlet:SPEC:135</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">If the container has an internal JSP container, the *.jsp extension is mapped to it, allowing JSP pages to be executed on demand.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:136"></a><font size="1PT">Servlet:SPEC:136</font></TD><TD align="center" valign="center"><font size="1PT">12</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">A servlet container is allowed to make other implicit mappings as long as explicit mappings take precedence.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:137"></a><font size="1PT">Servlet:SPEC:137</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Declarative security constraints are not applied when a servlet uses the RequestDispatcher to invoke a static resource or servlet using a forward or an include.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:138"></a><font size="1PT">Servlet:SPEC:138</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">The isUserInRole method uses the security-role-ref element when determining the return value of the call. If no security-role-ref element matching a security-role element has been declared, the container must default to checking the role-name element against the list of security-role elements for the web applications.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:290"></a><font size="1PT">Servlet:SPEC:290</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT"> Servlet containers MUST support the use of the @ServletSecurity
annotation on classes (and subclasses thereof) that implement
the jakarta.servlet.Servlet interface.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:291"></a><font size="1PT">Servlet:SPEC:291</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT"> The @HttpConstraint annotation is used within the @ServletSecurity
annotation to represent the security constraint to be applied to all
HTTP protocol methods for which a corresponding @HttpMethodConstraint
does NOT occur within the @ServletSecurity annotation.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:292"></a><font size="1PT">Servlet:SPEC:292</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT"> At most one instance of the @ServletSecurity annotation may occur
on a Servlet implementation class, and the @ServletSecurity annotation
MUST NOT be specified on (that is, targeted to) a Java method.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:293"></a><font size="1PT">Servlet:SPEC:293</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT"> When one or more @HttpMethodConstraint annotations are defined within
a @ServletSecurity annotation, each @HttpMethodConstraint defines the
security-constraint that applies to the HTTP protocol method identified
within the @HttpMethodConstraint. The encompassing @ServletSecurity
annotation defines the security-constraint that applies to all HTTP
protocol methods other than those for which a corresponding
@HttpMethodConstraint is defined within the @ServletSecurity annotation.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:294"></a><font size="1PT">Servlet:SPEC:294</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT"> When a security-constraint in the portable deployment descriptor
includes a url-pattern that is an exact match for a pattern mapped
to a class annotated with @ServletSecurity, the annotation must
have no effect on the constraints enforced by the Servlet container
on the pattern.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:295"></a><font size="1PT">Servlet:SPEC:295</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT"> When metadata-complete=true is defined for a portable deployment
descriptor, the @ServletSecurity annotation does not apply to any
of the url-patterns mapped to (any servlet mapped to) the annotated
class in the deployment descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:296"></a><font size="1PT">Servlet:SPEC:296</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1.2</font></TD><TD align="left" valign="center"><font size="1PT"> The enforcement by Servlet containers, of the @ServletSecurity
annotation must be equivalent in effect to enforcement, by the
container, of the security-constraint elements resulting from
the mapping defined in this section.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:297"></a><font size="1PT">Servlet:SPEC:297</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1.2</font></TD><TD align="left" valign="center"><font size="1PT"> The @ServletSecurity annotation is used to define one
method-independent @HttpConstraint followed by a list of zero
or more @HttpMethodConstraint specifications. The method-independent
constraint is applied to all HTTP methods for which no HTTP
method-specific constraint has been defined.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:298"></a><font size="1PT">Servlet:SPEC:298</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">4.1.2</font></TD><TD align="left" valign="center"><font size="1PT"> When no @HttpMethodConstraint elements are included, a
@ServletSecurity annotation corresponds to a single
security-constraint element containing a web-resource-collection
that contains no http-method elements, and thus pertains to all
HTTP methods.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:139"></a><font size="1PT">Servlet:SPEC:139</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">A servlet container enforces declarative or programmatic security for the principal associated with an incoming request based on the security attributes of the principal. This may happen in either of the following ways:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:139.1"></a><font size="1PT">Servlet:SPEC:139.1</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">A deployer has mapped a security role to a user group in the operational environment. The user group to which the calling principal belongs is retrieved from its security attributes. The principal is in the security role only if the principals user group matches the user group to which the security role has been mapped by the deployer.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:139.2"></a><font size="1PT">Servlet:SPEC:139.2</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">A deployer has mapped a security role to a principal name in a security policy domain. In this case, the principal name of the calling principal is retrieved from its security attributes. The principal is in the security role only if the principal name is the same as a principal name to which the security role was mapped.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:140"></a><font size="1PT">Servlet:SPEC:140</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.1</font></TD><TD align="left" valign="center"><font size="1PT">HTTP Basic Authentication is required to be supported by servlet containers.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:141"></a><font size="1PT">Servlet:SPEC:141</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.2</font></TD><TD align="left" valign="center"><font size="1PT">HTTP Digest Authentication is not a required authentication mechanism for servlet containers.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142"></a><font size="1PT">Servlet:SPEC:142</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">Form based authentication allows the customization of the login screen.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.1"></a><font size="1PT">Servlet:SPEC:142.1</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">The login form used for form based authentication must contain fields for entering a username and a password. These fields must be j_username and j_password, respectively.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.2"></a><font size="1PT">Servlet:SPEC:142.2</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">The login form used by the container can be specified within the deployment descriptor.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.3"></a><font size="1PT">Servlet:SPEC:142.3</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">An error page can be specified in the deployment descriptor which will be returned on failed form based authentication attempts.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.4"></a><font size="1PT">Servlet:SPEC:142.4</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">The authentication process for form based login:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.4.1"></a><font size="1PT">Servlet:SPEC:142.4.1</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">The login form associated with the security constraint is sent to the client and the URL path triggering the authentication is stored by the container.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.4.2"></a><font size="1PT">Servlet:SPEC:142.4.2</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">The container attempts to authenticate the user using the information from the form.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.4.3"></a><font size="1PT">Servlet:SPEC:142.4.3</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">If authentication fails, the error page is returned using either a forward or a redirect, and the status code of the response is set to 200.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.4.4"></a><font size="1PT">Servlet:SPEC:142.4.4</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">If authentication succeeds, the authenticated user's principal is check to see if it is in an authroized role for accessing the resource.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.4.5"></a><font size="1PT">Servlet:SPEC:142.4.5</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">If the user is authorized, the client is redirected to the resource using the stored URL path.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.5"></a><font size="1PT">Servlet:SPEC:142.5</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3.1</font></TD><TD align="left" valign="center"><font size="1PT">The action of the login form must always be j_security_check.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.6"></a><font size="1PT">Servlet:SPEC:142.6</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3.1</font></TD><TD align="left" valign="center"><font size="1PT">If the form based login is invoked because of an HTTP request, the original request parameters must be preserved by the container for use if on successful authentication, it redirects the call to the requested resource.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:142.7"></a><font size="1PT">Servlet:SPEC:142.7</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.3.1</font></TD><TD align="left" valign="center"><font size="1PT">If the user is authenticated using form login and has created an HTTP session, the timeout or invalidation of that session leads to the user being logged out in the sense that subsequent requests must cause the user to be re-authenticated.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:143"></a><font size="1PT">Servlet:SPEC:143</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">6.4</font></TD><TD align="left" valign="center"><font size="1PT">Servlet containers that are not Jakarta EE technology compliant are not required to support HTTPS protocol/authentication.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:144"></a><font size="1PT">Servlet:SPEC:144</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">7</font></TD><TD align="left" valign="center"><font size="1PT">Servlet containers are required to track authentication information at the container level rather than at the web application level.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:145"></a><font size="1PT">Servlet:SPEC:145</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">A security identity, or principal, must always be provided for use in a call to an enterprise bean.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:146"></a><font size="1PT">Servlet:SPEC:146</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">The default mode in calls to enterprise beans from web applications is for the security identity of a web user to be propagated to the Jakarta Enterprise Beans container.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:147"></a><font size="1PT">Servlet:SPEC:147</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">If a container supports calls to Jakarta Enterprise Beans' containers are required to support access to web resources by clients that have not authenticated themselves to the container through the use of the run-as element of the deployment descriptor. The container will use this identity when propagating the call from the web layer to the Jakarta Enterprise Beans layer.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:147.1"></a><font size="1PT">Servlet:SPEC:147.1</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">The security role propagated through the run-as element must be a security role defined in the deployment descriptor of the web application.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:148"></a><font size="1PT">Servlet:SPEC:148</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">Web containers running as part of a Jakarta EE platform, the use of run-as elements must be supported both for calls to Jakarta Enterprise Beans components within the same Jakarta EE application, and for calls to Jakarta Enterprise Beans components deployed in other Jakarta EE applications.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:149"></a><font size="1PT">Servlet:SPEC:149</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">If a request is issued against a set of protected resources the user who made the request must be a member of at least one of the named roles to be permitted to perform the contrained requests.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:150"></a><font size="1PT">Servlet:SPEC:150</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">The special role name "*" is a shorthand for all role names defined in the deployment descriptor.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:151"></a><font size="1PT">Servlet:SPEC:151</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">An auth constraint that names no roles indicates that access ot the contrained resources must not be permitted under any circumstances.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:152"></a><font size="1PT">Servlet:SPEC:152</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">A user data constraint establishes a requirement that the constrained requests be received over a protected transport layer connection.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:152.1"></a><font size="1PT">Servlet:SPEC:152.1</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">A transport guarantee of INTEGRAL is used to establish a requirement for content integrity.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:152.2"></a><font size="1PT">Servlet:SPEC:152.2</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">A transport guarantee of CONFIDENTIAL is used to establish a requirement for confidentiality.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:152.3"></a><font size="1PT">Servlet:SPEC:152.3</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">A transport guarantee of NONE indicates that the container must accept the constrained requests when received on any connection including unprotected ones.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:153"></a><font size="1PT">Servlet:SPEC:153</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8</font></TD><TD align="left" valign="center"><font size="1PT">If no auth-constraing applies to a request, the container must accept the request without requiring user authentication.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:154"></a><font size="1PT">Servlet:SPEC:154</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">When a url-pattern and http-method pair occurs in multiple security constraints, the applicable constraints (on the pattern and the method) are defined by combining the individual constraints.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:154.1"></a><font size="1PT">Servlet:SPEC:154.1</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">A security constraint that does not contain an auth constraint shall combine with auth constraints that name or imply roles to allow unauthenticated access.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:154.2"></a><font size="1PT">Servlet:SPEC:154.2</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">The special case of an auth constraint that names no roles shall combine with any other constraints to override their affects and cause access to be precluded.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:154.3"></a><font size="1PT">Servlet:SPEC:154.3</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">The combination of user-data constraints that apply to a common usr-pattern and http-method shall yield the union of connection types accepted by the individual constraints as acceptable connection types.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:154.4"></a><font size="1PT">Servlet:SPEC:154.4</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">A security constraint that does not contain a user-data constraint shall combine with other user-data constraints to cause the unprotected connection type to be an accepted connection type.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:155"></a><font size="1PT">Servlet:SPEC:155</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">When a Servlet container receives a request, it shall use the url pattern matching algorithm to select the constraints, if any, defined that is the best match to the request URI</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:156"></a><font size="1PT">Servlet:SPEC:156</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">If no security contraint can be matched between the defined contraints and the request URI, the container will accept the request.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:157"></a><font size="1PT">Servlet:SPEC:157</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">If a constraint match is found based on the request URI, the container shall determine if the HTTP method of the request is constrained, if it's not, then the constrained request will be accepted.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:158"></a><font size="1PT">Servlet:SPEC:158</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">If the HTTP method is contrained, then the method used for the request must match what is acceptable for the constraint in order for the request to be accepted.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:159"></a><font size="1PT">Servlet:SPEC:159</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">If the characteristics of the connection on which the request was received must satisfy at least one of the supported connection types defined by the constraints. If this rule is not satisfied, the container shall reject the request and redirect it to the HTTPS port.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:159.1"></a><font size="1PT">Servlet:SPEC:159.1</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">As an optimization, a container should reject the connection request if it doesn't match the constrained connection types and return a 403 (SC_FORBIDDEN) status code if it knows that access will ultimately be precluded (by an auth constraint naming with no roles).</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:160"></a><font size="1PT">Servlet:SPEC:160</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">If a constraint naming defined no roles, any attempted requests will result in a 403 (SC_FORBIDDEN).</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:161"></a><font size="1PT">Servlet:SPEC:161</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">If access is restricted to permitted roles and the request has not been authenticated, the request shall be rejected as unauthorized and a 401 (SC_UNAUTHORIZED) status code shall be returned to cause authentication.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:162"></a><font size="1PT">Servlet:SPEC:162</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">If access is restricted to permitted roles and the authentication identity of the request is not a member of any of these roles, the request shall be rejected as forbidden and a 403 (SC_FORBIDDEN) status code shall be returned to the user.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:309"></a><font size="1PT">Servlet:SPEC:309</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.4.2</font></TD><TD align="left" valign="center"><font size="1PT">
When the deny-uncovered-http-methods flag is set in the web.xml of an application, the container
must deny any HTTP protocol method when it is used with a request URL for which the HTTP method
is uncovered at the combined security constraint that applies to the url-pattern that is the best
match for the request URL. The denied request shall be rejected as forbidden and a 403 (SC_FORBIDDEN)
status code shall be returned.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:310"></a><font size="1PT">Servlet:SPEC:310</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">8.4.2</font></TD><TD align="left" valign="center"><font size="1PT">
When an applications security configuration contains no uncovered methods, the
deny-uncovered-http-methods flag must have no effect on the effective security
configuration of the application.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:163"></a><font size="1PT">Servlet:SPEC:163</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">If a developer creates a session while a user is not authenticated, and the container then authenticates the user, the session visible to developer code after login must be the same session object that was created prior to login occurring so that there is no loss of session information.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:164"></a><font size="1PT">Servlet:SPEC:164</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">For all authentication methods in both non-single signon and single signon containers, logout is caused by one of the following situations:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:164.1"></a><font size="1PT">Servlet:SPEC:164.1</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">Invalidation of the session. If this occurs, getUserPrincipal will return a null value.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:164.2"></a><font size="1PT">Servlet:SPEC:164.2</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">Session timeouts. If this occurs, getUserPrincipal will return a null value.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:164.3"></a><font size="1PT">Servlet:SPEC:164.3</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">An explicit call to HttpSession.invalidateAll. If this occurs, getUserPrincipal will return a null value.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:164.4"></a><font size="1PT">Servlet:SPEC:164.4</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">An explicit call to HttpSession.logout.If this occurs, getUserPrincipal will return a null value.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:165"></a><font size="1PT">Servlet:SPEC:165</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">For non-single signon containers, a session invalidating has no effect on login state or session state in other web applications.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:166"></a><font size="1PT">Servlet:SPEC:166</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">For single signon containers, logout causes all other active sessions associated with the current user to be invalidated.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:167"></a><font size="1PT">Servlet:SPEC:167</font></TD><TD align="center" valign="center"><font size="1PT">13</font></TD><TD align="center" valign="center"><font size="1PT">10</font></TD><TD align="left" valign="center"><font size="1PT">Invalidation or timeout of an individual session causes the termination of that session, but does not cause a logout unless it is the last session for this user, which means that a container is allowed to start a new session for one or more web applications without re-authenticating the user.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:168"></a><font size="1PT">Servlet:SPEC:168</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Servlet 2.5 web containers may use schema to validate the structure of a deployment descriptor.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:169"></a><font size="1PT">Servlet:SPEC:169</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">The deployment-extension element provides the ability to inject application or framework specific configuration information directly into the deployment descriptor.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:169.1"></a><font size="1PT">Servlet:SPEC:169.1</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">If a container uses schema to validate a deployment descriptor, any new content injected into deployment-extension elements as described below will not be validated by the web container.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:169.2"></a><font size="1PT">Servlet:SPEC:169.2</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">Deployment extensions are only valid within the top level web-app element or within servlet elements.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:169.3"></a><font size="1PT">Servlet:SPEC:169.3</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">Servlet 2.5 containers are required to raise an exception if they do not recognize an extension within a deployment descriptor where the mustUnderstand attribute is 'true'.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:169.4"></a><font size="1PT">Servlet:SPEC:169.4</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">1.1</font></TD><TD align="left" valign="center"><font size="1PT">Servlet 2.5 containers are not required to attempt to process extended deployment information where the nustUnderstand attribute is set to 'false'.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:170"></a><font size="1PT">Servlet:SPEC:170</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">1</font></TD><TD align="left" valign="center"><font size="1PT">Security information which may appear in the deployment descriptor is not required to be supported unless the servlet container is part of an implementation of the Jakarta EE specification.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:193"></a><font size="1PT">Servlet:SPEC:193</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT">The following additional elements exist in the Web application deployment descriptor to meet the requirements of Web containers that are JSP pages enabledor part of a Jakarta EE application server. They are not required to be supported by containers wishing to support only the servlet specification:</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:171"></a><font size="1PT">Servlet:SPEC:171</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT">jsp-config</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:172"></a><font size="1PT">Servlet:SPEC:172</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT">Syntax for looking up JNDI objects(env-entry, ejb-ref, ejb-local-ref, resource-ref, resource-env-ref)</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:193.1"></a><font size="1PT">Servlet:SPEC:193.1</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT">Syntax for specifying the message destination (message-destination, message-destination-ref)</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:193.2"></a><font size="1PT">Servlet:SPEC:193.2</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT">Reference to a Web service (service-ref)</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:174"></a><font size="1PT">Servlet:SPEC:174</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Web containers must remove all leading and trailing
whitespace, which is defined as "S(whitespace)" in XML 1.0 (http://www.w3.org/TR/2000/WD-xml-
2e-20000814), for the element content of the text nodes of a deployment descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:175"></a><font size="1PT">Servlet:SPEC:175</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The containers and tools that are
part of Jakarta EE technology-compliant implementation are required to validate
deployment descriptor against the XML schema for structural correctness.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:176"></a><font size="1PT">Servlet:SPEC:176</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">It is recommended that Web containers and tools that
manipulate Web applications provide a level of semantic checking. For example, it
should be checked that a role referenced in a security constraint has the same
name as one of the security roles defined in the deployment descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:10176"></a><font size="1PT">Servlet:SPEC:10176</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The sub elements under web-app can be in an arbitrary
order.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11276"></a><font size="1PT">Servlet:SPEC:11276</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The multiplicity
of the elements distributable, session-config, welcome-file-list, jspconfig,
login-config, and locale-encoding-mapping-list is "0 or more."
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11276.1"></a><font size="1PT">Servlet:SPEC:11276.1</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Containers must inform the developer
with a descriptive error message when the deployment descriptor contains
more than one element of session-config, jsp-config, and login-config.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11276.2"></a><font size="1PT">Servlet:SPEC:11276.2</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">The deployment descriptor instance
file must not contain multiple elements of session-config,
jsp-config, and login-config.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11276.3"></a><font size="1PT">Servlet:SPEC:11276.3</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The container must concatenate the items
in welcome-file-list and locale-encoding-mapping-list when there are multiple occurrences.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11276.4"></a><font size="1PT">Servlet:SPEC:11276.4</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The multiple
occurrence of distributable must be treated exactly in the same way as the
single occurrence of distributable.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11276"></a><font size="1PT">Servlet:SPEC:11276</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">URI paths specified in the deployment descriptor are
assumed to be in URLdecoded form.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11276.1"></a><font size="1PT">Servlet:SPEC:11276.1</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The containers must inform the developer
with a descriptive error message when URL contains CR(#xD) or LF(#xA).
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:11276.2"></a><font size="1PT">Servlet:SPEC:11276.2</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">The containers must
preserve all other characters including whitespace in URL.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:177"></a><font size="1PT">Servlet:SPEC:177</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Containers must attempt to canonicalize paths in present in the deployment descriptor.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:178"></a><font size="1PT">Servlet:SPEC:178</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">Paths beginning or resolving to paths that begin with ".." are not valid paths in the deployment descriptor.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:179"></a><font size="1PT">Servlet:SPEC:179</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="left" valign="center"><font size="1PT">Elements whose valus is an enumerated type must be treated in a case sensitive manner.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:214"></a><font size="1PT">Servlet:SPEC:214</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">
Servlet containers are required to support the use of these annotations
within classes that extend the jakarta.servlet.http.HttpServlet abstract
class.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:215"></a><font size="1PT">Servlet:SPEC:215</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">
When specified on a class target, these annotations apply to all requests
processed by the public service method of the HttpServlet implementation class.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:216"></a><font size="1PT">Servlet:SPEC:216</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">
When an annotation is specified at both the class and method level, the method
targeted annotation overrides that on the class (for the method).
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:217"></a><font size="1PT">Servlet:SPEC:217</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">
When the metadata-complete attribute is set in the portable deployment
descriptor, the annotations described in this section have no effect on
the access control policy enforced by the container on behalf of the
corresponding web module or web fragment.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:218"></a><font size="1PT">Servlet:SPEC:218</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">
When a security-constraint in the portable deployment descriptor
includes a url-pattern that matches a request URL, the security
annotations described in this section have no effect on the access
policy that applies to the request URL.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:219"></a><font size="1PT">Servlet:SPEC:219</font></TD><TD align="center" valign="center"><font size="1PT">14</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT">
When none of these annotations have been assigned to the class and method
targets corresponding to a request, the access policy that is applied to
the request is established by the applicable security constraints, if any,
in the corresponding portable deployment descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:184"></a><font size="1PT">Servlet:SPEC:184</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Jakarta EE technology-compliant containers are required to provide a mechanism by which a deployer can learn about what jar file containing resources and code are available for the Web application.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:185"></a><font size="1PT">Servlet:SPEC:185</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="left" valign="center"><font size="1PT">Containers should provide a convenient procedure for editing and configuring library files or extensions.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:186"></a><font size="1PT">Servlet:SPEC:186</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Servlet containers that are part of a Jakarta EE product should not
allow the application to override Java SE or Jakarta EE platform classes,
such as those in the java.* and javax.* namespaces,
that either Java SE or Jakarta EE do not allow to be modified.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:187"></a><font size="1PT">Servlet:SPEC:187</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">A security identity, or principal, must always be provided for use in a call to an enterprise bean.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:188"></a><font size="1PT">Servlet:SPEC:188</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">The default mode in calls to enterprise beans from web applications is
for the security identity of a web user to be propagated to the Jakarta Enterprise Beans container.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:189"></a><font size="1PT">Servlet:SPEC:189</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">web containers are required to allow web users that are not known to the web container
or to the Jakarta Enterprise Beans container to make calls:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:189.1"></a><font size="1PT">Servlet:SPEC:189.1</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">Web containers are required to support access to web resources by clients
that have not authenticated themselves to the container.
This is the common mode of access to web resources on the Internet.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:189.2"></a><font size="1PT">Servlet:SPEC:189.2</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">Application code may be the sole processor of signon and
customization of data based on caller identity.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:190"></a><font size="1PT">Servlet:SPEC:190</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">a web application deployment descriptor may specify a run-as element.
When a run-as role is specified for a Servlet, the Servlet container must
propagate a principal mapped to the role as the security identity in any call from the
Servlet to an Enterprise Beans, including calls originating from the Servlet's init and destroy
methods. The security role name must be one of the security role names defined for
the web application.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:191"></a><font size="1PT">Servlet:SPEC:191</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">For web containers running as part of a Jakarta EE platform,
the use of run-as elements must be supported both for calls to Jakarta Enterprise Beans components within the same Jakarta EE application,
and for calls to Jakarta Enterprise Beans components deployed in other Jakarta EE applications.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:194"></a><font size="1PT">Servlet:SPEC:194</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">Web containers may choose to support running components written to implement a Web service endpoint
as defined by the JAX-RPC and/or JAX-WS specifications.
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173"></a><font size="1PT">Servlet:SPEC:173</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">Web containers embedded in a JavaEE conformant implementation are required to support JAX-RPC and JAX-WS web service components.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.1"></a><font size="1PT">Servlet:SPEC:173.1</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">JSR-109 [http://jcp.org/jsr/detail/109.jsp] defines the model for packaging a Web service interface
with its associated WSDL description and associated classes.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.2"></a><font size="1PT">Servlet:SPEC:173.2</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">It(JSR-109) defines a mechanism for JAX-WS and JAX-RPC enabled Web containers to link to a component that implements this Web service.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.3"></a><font size="1PT">Servlet:SPEC:173.3</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">JAX-WS and JAX-RPC enabled Web containers must support the developer
in using the Web deployment descriptor
to define the following information for the endpoint implementation component,
using the same syntax as for HTTP Servlet components using the servlet element.
The child elements are are used to specify endpoint information in the following way:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.3.1"></a><font size="1PT">Servlet:SPEC:173.3.1</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">the servlet-name element defines a logical name which may be used
to locate this endpoint description among the other Web components in the WAR
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.3.2"></a><font size="1PT">Servlet:SPEC:173.3.2</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">the servlet-class element provides the fully qualified Java class name of this endpoint implementation</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.3.3"></a><font size="1PT">Servlet:SPEC:173.3.3</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">the description element(s) may be used to describe the component and may be displayed in a tool</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.3.4"></a><font size="1PT">Servlet:SPEC:173.3.4</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">the load-on-startup element specifies the order in which the component is initialized relative to other Web components in the Web container</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.3.5"></a><font size="1PT">Servlet:SPEC:173.3.5</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">the security-role-ref element may be used to test whether the authenticated user is in a logical security role</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.3.6"></a><font size="1PT">Servlet:SPEC:173.3.6</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">the run-as element may be used to override the identity propagated to Jakarta Enterprise Beans called by this component</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.4"></a><font size="1PT">Servlet:SPEC:173.4</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">Any servlet initialization parameters defined by the developer for this Web component may be ignored by the container.</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.5"></a><font size="1PT">Servlet:SPEC:173.5</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">JAX-WS and JAXRPC enabled Web component inherits the traditional Web component
mechanisms for defining the following information:
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.5.1"></a><font size="1PT">Servlet:SPEC:173.5.1</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">mapping of the component to the Web container's URL namespace using the servlet mapping technique</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.5.2"></a><font size="1PT">Servlet:SPEC:173.5.2</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">authorization constraints on Web components using security constraints</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.5.3"></a><font size="1PT">Servlet:SPEC:173.5.3</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">the ability to use servlet filters to provide low-level byte stream support for manipulating JAX-WS and/or JAX-RPC messages using the filter mapping technique</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.5.4"></a><font size="1PT">Servlet:SPEC:173.5.4</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">the timeout characteristics of any HTTP sessions that are associated with the component</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:173.5.5"></a><font size="1PT">Servlet:SPEC:173.5.5</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT">links to Jakarta EE objects stored in the JNDI namespace</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195"></a><font size="1PT">Servlet:SPEC:195</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">Annotations must be supported on the following container managed classes
that implement the following interfaces and are declared in the web application deployment descriptor
or using the annotations defined in Section8.1, ?Annotations
and pluggability? on page8-65 or added programmatically.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.1"></a><font size="1PT">Servlet:SPEC:195.1</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.Servlet</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.2"></a><font size="1PT">Servlet:SPEC:195.2</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.Filter</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.3"></a><font size="1PT">Servlet:SPEC:195.3</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.ServletContextListener</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.4"></a><font size="1PT">Servlet:SPEC:195.4</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.ServletContextAttributeListener</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.5"></a><font size="1PT">Servlet:SPEC:195.5</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.ServletRequestListener</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.6"></a><font size="1PT">Servlet:SPEC:195.6</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.ServletRequestAttributeListener</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.7"></a><font size="1PT">Servlet:SPEC:195.7</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.http.HttpSessionListener</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.8"></a><font size="1PT">Servlet:SPEC:195.8</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.http.HttpSessionAttributeListener</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.10"></a><font size="1PT">Servlet:SPEC:195.10</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.http.HttpSessionIdListener</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:195.9"></a><font size="1PT">Servlet:SPEC:195.9</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">jakarta.servlet.AsyncListener</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:196"></a><font size="1PT">Servlet:SPEC:196</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">References must be injected prior to any lifecycle methods being called and
the component instance being made available the the application.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:197"></a><font size="1PT">Servlet:SPEC:197</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">In a web application, classes using resource injection will have their annotations processed only
if they are located in the WEB-INF/classes directory, or if they are packaged in a jar file located in WEB-INF/lib.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:198"></a><font size="1PT">Servlet:SPEC:198</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The web application deployment descriptor contains a metadata-complete attribute on the web-app element.
The metadata-complete attribute defines whether the web descriptor is complete,
or whether other sources of metadata used by the deployment process should be considered.
Metadata may come from the web.xml file, web-fragment.xml files,
annotations on class files in WEB-INF/classes, and
annotations on classes in jar files in the WEB-INF/lib directory.
If metadata-complete is set to "true", the deployment tool only examines the web.xml file and
must ignore annotations such as @WebServlet, @WebFilter, and @WebListener
present in the class files of the application, and must also ignore any web-fragment.xml
descriptor packaged in a jar file in WEB-INF/lib.
If the metadata-complete attribute is not specified or is set to "false",
the deployment tool must examine the class files and web-fragment.xml files for metadata,
as previously specified.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:289"></a><font size="1PT">Servlet:SPEC:289</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">The web-fragment.xml also contains the metadata-complete attribute on the web-
fragment element. The attribute defines whether the web-fragment.xml descriptor
is complete for the given fragment, or whether it should scan for annotations in the
classes in the associated jar file. If metadata-complete is set to "true" the
deployment tool only examines the web-fragment.xml and must ignore annotations
such as @WebServlet, @WebFilter and @WebListener present in the class files of the
fragment. If metadata-complete is not specified or is set to "false" the deployment
tool must examine the class files for metadata.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199"></a><font size="1PT">Servlet:SPEC:199</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="left" valign="center"><font size="1PT">Following are the annotations that are required by a Jakarta EE technology compliant web container.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.1"></a><font size="1PT">Servlet:SPEC:199.1</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.4</font></TD><TD align="left" valign="center"><font size="1PT">The @Resource annotation is used to declare a reference to a resource such as
a data source, Java Messaging Service (JMS) destination, or environment entry.
This annotation is equivalent to declaring a resource-ref, message-destinationref
or env-ref, or resource-env-ref element in the deployment descriptor.
@Resource annotation is specified on a class, method or field.
The container is responsible injecting references to resources declared by
the @Resource annotation and mapping it to the proper JNDI resources.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.2"></a><font size="1PT">Servlet:SPEC:199.2</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.11</font></TD><TD align="left" valign="center"><font size="1PT">@Resources annotation acts as a container for multiple @Resource annotations
because the Java MetaData specification does not allow for multiple annotations
with the same name on the same annotation target.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.3"></a><font size="1PT">Servlet:SPEC:199.3</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.3</font></TD><TD align="left" valign="center"><font size="1PT">InjectionComplete annotation is declared on a method which will be called after the resources injections have been completed and before any lifecycle methods on a component are called. This allows application code to do post create processing if necessary.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">removed</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.4"></a><font size="1PT">Servlet:SPEC:199.4</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.2</font></TD><TD align="left" valign="center"><font size="1PT">Jakarta Enterprise Beans 4.0 components may be referenced from a web component using the @EJB annotation.
The @EJB annotation provides the equivalent functionality of declaring the ejb-ref
or ejb-local-ref elements in the deployment descriptor.
Fields that have a corresponding @EJB annotation are injected with the a reference to the corresponding Jakarta Enterprise Beans component.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.5"></a><font size="1PT">Servlet:SPEC:199.5</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.13</font></TD><TD align="left" valign="center"><font size="1PT">The @WebServiceRef annotation provides a reference to a web service in a web component
in same way as a resource-ref element would in the deployment descriptor.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.6"></a><font size="1PT">Servlet:SPEC:199.6</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.1</font></TD><TD align="left" valign="center"><font size="1PT">@DeclareRoles: This annotation is used to define the security roles that comprise the security model
of the application. This annotation is specified on a class, and if it is used to define
roles that could be tested (i.e., by calling isUserInRole) from within the methods of
the annotated class. Roles that are implicitly declared as a result of their use in a
@RolesAllowed need not be explicitly declared using the @DeclareRoles annotaion.
The @DeclareRoles annotation may only be defined in classes implementing the
jakarta.servlet.Servlet interface or a subclass thereof.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.7"></a><font size="1PT">Servlet:SPEC:199.7</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.12</font></TD><TD align="left" valign="center"><font size="1PT">The @RunAs annotation is equivalent to the run-as element in the deployment descriptor.
The @RunAs annotation may only be defined in classes implementing the jakarta.servlet.Servlet interface
or a subclass thereof.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.8"></a><font size="1PT">Servlet:SPEC:199.8</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.3</font></TD><TD align="left" valign="center"><font size="1PT">The @EJBs annotation allows more than one @EJB annotations to be declared on a single resource.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.9"></a><font size="1PT">Servlet:SPEC:199.9</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.5</font></TD><TD align="left" valign="center"><font size="1PT">This annotation(@PersistenceContext) specifies the container managed entity manager
for referenced persistence units.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.10"></a><font size="1PT">Servlet:SPEC:199.10</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.6</font></TD><TD align="left" valign="center"><font size="1PT">The PersistenceContexts annotation allows more than one @PersistenceContext
to be declared on a resource.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.11"></a><font size="1PT">Servlet:SPEC:199.11</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.7</font></TD><TD align="left" valign="center"><font size="1PT">The @PersistenceUnit annotation provides Jakarta Enterprise Beans components
declared in a servlet a reference to a entity manager factory. The entity manager
factory is bound to a separate persistence.xml configuration file as described in
section 5.10 of the Jakarta Enterprise Beans 4.0 specification.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.12"></a><font size="1PT">Servlet:SPEC:199.12</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.8</font></TD><TD align="left" valign="center"><font size="1PT">This annotation(@PersistenceUnits) allows for more than one @PersistentUnit annotations to be
declared on a resource.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.13"></a><font size="1PT">Servlet:SPEC:199.13</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.9</font></TD><TD align="left" valign="center"><font size="1PT">The @PostConstruct annotation is declared on a method that does not take any
arguments, and must not throw any checked exceptions. The return value must be
void. The method MUST be called after the resources injections have been completed
and before any lifecycle methods on the component are called.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:304"></a><font size="1PT">Servlet:SPEC:304</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.9</font></TD><TD align="left" valign="center"><font size="1PT">TThe @PostConstruct annnotation MUST be supported by all classes that support
dependency injection and called even if the class does not request any resources to be injected.
If the method throws an unchecked exception the class MUST not be put into service
and no method on that instance can be called.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:199.14"></a><font size="1PT">Servlet:SPEC:199.14</font></TD><TD align="center" valign="center"><font size="1PT">15</font></TD><TD align="center" valign="center"><font size="1PT">5.10</font></TD><TD align="left" valign="center"><font size="1PT">The @PreDestroy annotation is declared on a method of a container managed
component. The method is called prior to component being removed by the
container. The method annotated with @PreDestroy must return void and must not throw a
checked exception. The method may be public, protected, package private or private.
The method must not be static however it may be final.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:204"></a><font size="1PT">Servlet:SPEC:204</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">7.1</font></TD><TD align="left" valign="center"><font size="1PT">sessions of a context must be resumable by requests into
that context regardless of whether their associated context was being
accessed directly or as the target of a request dispatch at the time
the sessions were created.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:205"></a><font size="1PT">Servlet:SPEC:205</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.1</font></TD><TD align="left" valign="center"><font size="1PT">(The target servlet of the include method) cannot set
headers or call any method that affects the headers of the response,
with the exception of the HttpServletRequest.getSession() and
HttpServletRequest.getSession(boolean) methods.
Any attempt to set the headers must be ignored,
and any call to HttpServletRequest.getSession() or
HttpServletRequest.getSession(boolean) that would require adding a
Cookie response header must throw an IllegalStateException
if the response has been committed.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:206"></a><font size="1PT">Servlet:SPEC:206</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.2</font></TD><TD align="left" valign="center"><font size="1PT">clarify a way to map a filter to all servlet dispatches
... uses the special servlet name '*'.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:207"></a><font size="1PT">Servlet:SPEC:207</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.3</font></TD><TD align="left" valign="center"><font size="1PT">(Servlet 2.5) Previous versions of the servlet schema allows only a single url-pattern or servlet name per servlet mapping. For servlets mapped to multiple URLs this results in needless repetition of whole mapping clauses. The deployment descriptor servlet-mappingType was updated to...
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:208"></a><font size="1PT">Servlet:SPEC:208</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.4</font></TD><TD align="left" valign="center"><font size="1PT">(Servlet 2.5)Previous versions of the servlet schema allows only a single url-pattern in a filter mapping. For filters mapped to multiple URLs this results in needless repetition of whole mapping clauses. The deployment descriptor schema the filter-mappingType was updated to... This change allows multiple patterns and servlet names to be defined in a single mapping</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:209"></a><font size="1PT">Servlet:SPEC:209</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.5</font></TD><TD align="left" valign="center"><font size="1PT">The http-method elements now need to be a token
as described in HTTP 1.1 specification section 2.2.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:210"></a><font size="1PT">Servlet:SPEC:210</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.8</font></TD><TD align="left" valign="center"><font size="1PT">If the location of the error handler is a servlet or a JSP page: [...]
The response setStatus method is disabled and ignored if called.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:211"></a><font size="1PT">Servlet:SPEC:211</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.9</font></TD><TD align="left" valign="center"><font size="1PT">The API clarification better describes what happens
when a client did not specify a session id.
The API documentation in Section SRV.16.1.3, HttpServletRequest
was updated to specify when false is returned:
Returns false if the client did not specify any session ID.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:212"></a><font size="1PT">Servlet:SPEC:212</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.10</font></TD><TD align="left" valign="center"><font size="1PT">Section SRV.5.5, Closure of Response Object was updated
to the following: "The amount of content specified in the
setContentLength method of the response has been greater than zero
and has been written to the response".
the response's content length is set to 0 via
response.setHeader("Content-Length", "0")
and any subsequently setHeader() calls are ignored.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="Servlet:SPEC:213"></a><font size="1PT">Servlet:SPEC:213</font></TD><TD align="center" valign="center"><font size="1PT">A</font></TD><TD align="center" valign="center"><font size="1PT">8.11</font></TD><TD align="left" valign="center"><font size="1PT">The API in Section SRV.15.2.16, ServletRequest
was updated to described the behavior if the method is called
after the getReader() was called. If the getReader() is called
there will be no effect.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font size="1PT">
<br>
</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD><TD align="center" valign="center"><font size="1PT">technology</font></TD><TD align="center" valign="center"><font size="1PT">active</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
</TABLE>
</body>
</html>
|
