/
JavaEESpecAssertions.html
3399 lines (3369 loc) · 362 KB
/
JavaEESpecAssertions.html
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
<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, 2019 Oracle and/or its affiliates. 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 EE 8 Platform<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">344</font></TD><TD align="center" valign="center"><font size="2PT">340</font></TD><TD align="center" valign="center"><font size="2PT">4</font></TD><TD align="center" valign="center"><font size="2PT">0</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">316</font></TD><TD align="center" valign="center"><font size="2PT">312</font></TD><TD align="center" valign="center"><font size="2PT">4</font></TD><TD align="center" valign="center"><font size="2PT">0</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">28</font></TD><TD align="center" valign="center"><font size="2PT">28</font></TD><TD align="center" valign="center"><font size="2PT">0</font></TD><TD align="center" valign="center"><font size="2PT">0</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="JavaEE:SPEC:1"></a><font size="1PT">JavaEE:SPEC:1</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">6.4</font></TD><TD align="left" valign="center"><font size="1PT">
Java EE application clients are required to be able to define
their own CORBA services directly, using the RMI-IIOP APIs.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:2"></a><font size="1PT">JavaEE:SPEC:2</font></TD><TD align="center" valign="center"><font size="1PT">2</font></TD><TD align="center" valign="center"><font size="1PT">6.5</font></TD><TD align="left" valign="center"><font size="1PT">
Java EE application clients are required to be allowed to
use JavaIDL directly to present CORBA services themselves.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:16"></a><font size="1PT">JavaEE:SPEC:16</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">3.6.1</font></TD><TD align="left" valign="center"><font size="1PT">
The source of security attributes may vary across implementations of the
Java EE platform. Security attributes may be transmitted in the calling principal's
credential or in the security context. In other cases, security attributes may be
retrieved from a trusted third party, such as a directory service or a security
service.
</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="JavaEE:SPEC:19"></a><font size="1PT">JavaEE:SPEC:19</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="left" valign="center"><font size="1PT"> .The Java EE Product Provider must meet the following requirements concerning user
authentication.
All Java EE web servers must maintain a login session for each web user. It must be
possible for a login session to span more than one application, allowing a user to log
in once and access multiple applications. The required login session support is
described in the servlet specification. This requirement of a session for each web
user supports single signon.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:20"></a><font size="1PT">JavaEE:SPEC:20</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT"> Lazy authentication must be supported by web servers for protected web
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">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:21"></a><font size="1PT">JavaEE:SPEC:21</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.2</font></TD><TD align="left" valign="center"><font size="1PT"> All Java EE products are required to support three login mechanisms: HTTP basic
authentication, SSL mutual authentication, and form-based login. An application is
not required to use any of these mechanisms, but they are required to be available
for any application's 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">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="JavaEE:SPEC:22"></a><font size="1PT">JavaEE:SPEC:22</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.2.1</font></TD><TD align="left" valign="center"><font size="1PT">All Java EE products are required to support HTTP basic authentication (RFC2068).
Platform Providers are also required to support basic authentication over SSL.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:23"></a><font size="1PT">JavaEE:SPEC:23</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.2.2</font></TD><TD align="left" valign="center"><font size="1PT"> SSL Mutual Authentication
SSL 3.0 and the means to perform mutual (client and server) certificate based
authentication are required by this specification.
All Java EE products must support the following cipher suites to ensure
interoperable authentication with clients:
TLS_RSA_WITH_RC4_128_MD5
SSL_RSA_WITH_RC4_128_MD5
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
TLS_RSA_EXPORT_WITH_RC4_40_MD5
SSL_RSA_EXPORT_WITH_RC4_40_MD5
TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:24"></a><font size="1PT">JavaEE:SPEC:24</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.2.3</font></TD><TD align="left" valign="center"><font size="1PT"> Form Based Login
The web application deployment descriptor contains an element that causes a Java EE
product to associate an HTML form resource (perhaps dynamically generated) with
the web application. If the Deployer chooses this form of authentication (over HTTP
basic, or SSL certificate based authentication), this form must be used as the user
interface for login to the application.
The form based login mechanism and web application deployment descriptors
are described in 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="JavaEE:SPEC:25"></a><font size="1PT">JavaEE:SPEC:25</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.3</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.
A web container reports that no user has been authenticated by returning null
from the HttpServletRequest method getUserPrincipal. This is different than
the corresponding result for EJB containers. The EJB specification requires that
the EJBContext method getCallerPrincipal always return a valid Principal
object. The method can never return null.
Components running in a web container must be able to call enterprise beans
even when no user has been authenticated in the web container. When a call is
made in such a case from a component in a web container to an enterprise bean, a
Java EE product must provide a principal for use in the call.
A Java EE product may provide a principal for use by unauthenticated callers
using many approaches, including, but not limited to:
Always use a single distinguished principal.
Use a different distinguished principal per server, or per session, or per application.
Allow the deployer or system administrator to choose which principal to use
through the Run As capability of the web and enterprise bean 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="JavaEE:SPEC:26"></a><font size="1PT">JavaEE:SPEC:26</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.4</font></TD><TD align="left" valign="center"><font size="1PT"> The application client container must provide authentication of application users to
satisfy the authentication and authorization constraints enforced by the enterprise
bean containers and web containers.
The container will provide an appropriate user interface for interactions with
the user to gather authentication data. In addition, an application client may
provide a class that implements the
javax.security.auth.callback.CallbackHandler interface and specify the class
name in its deployment descriptor
The Deployer may override the callback
handler specified by the application and require use of the container's default
authentication user interface instead.
If use of a callback handler has been configured by the Deployer, the
application client container must instantiate an object of this class and use it for all
authentication interactions with the user. The application's callback handler must
support all the Callback objects specified in the javax.security.auth.callback
package.
Application clients execute in an environment controlled by a J2SE security
manager and are subject to the security permissions defined in EE.6.2, "Java 2
Platform, Standard Edition (J2SE) Requirements". Although this specification does not
define the relationship between the operating system identity associated with a
running application client and the authenticated user identity, support for single
signon requires that the Java EE product be able to relate these identities
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:27"></a><font size="1PT">JavaEE:SPEC:27</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.5</font></TD><TD align="left" valign="center"><font size="1PT"> A Product Provider must support both of the following:
1. Configured Identity.A Java EE container must be able to authenticate for access
to the resource using a principal and authentication data specified by a Deployer
at deployment time.The authentication must not depend in any way on data
provided by the application components. Providing for the confidential storage
of the authentication information is the responsibility of the Product Provider.
2. Programmatic Authentication. The Java EE product must provide for specification
of the principal and authentication data for a resource by the application
component at runtime using appropriate APIs. The application may obtain the
principal and authentication data through a variety of mechanisms, including
receiving them as parameters, obtaining them from the component's environment,
and so forth.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:28"></a><font size="1PT">JavaEE:SPEC:28</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">4.5</font></TD><TD align="left" valign="center"><font size="1PT"> the following techniques are recommended but not required by
this specification:
1. Principal Mapping. A resource can have a principal and attributes that are determined
by a mapping from the identity and security attributes of the requesting
principal. In this case, a resource principal is not based on inheritance of
the identity or security attributes from a requesting principal, but gets its identity
and security attributes based on the mapping.
2. Caller Impersonation. A resource principal acts on behalf of a requesting
principal. Acting on behalf of a caller principal requires delegation of the caller's
identity and credentials to the underlying resource manager. In some scenarios,
a requesting principal can be a delegate of an initiating principal and
the resource principal is transitively impersonating an initiating principal.
The support for principal delegation is typically specific to a security mechanism.
For example, Kerberos supports a mechanism for the delegation of
authentication. (Refer to the Kerberos v5 specification for more details.)
3. Credentials Mapping. This technique may be used when an application server
and an EIS support different authentication domains. For example:
a. The initiating principal may have been authenticated and have public key
certificate-based credentials.
b. The security environment for the resource manager may be configured
with the Kerberos authentication service.
The application server is configured to map the public key certificate-based
credentials associated with the initiating principal to the Kerberos credentials.
</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="JavaEE:SPEC:29"></a><font size="1PT">JavaEE:SPEC:29</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">5.1</font></TD><TD align="left" valign="center"><font size="1PT">Code Authorization
A Java EE product may restrict the use of certain J2SE classes and methods to secure
and insure proper operation of the system. The minimum set of permissions that a
Java EE product is required to grant to a Java EE application is defined in
Section Java EE.6.2, Java 2 Platform, Standard Edition (J2SE) Requirements. All
Java EE products must be capable of deploying application components with exactly
these permissions.
A Java EE Product Provider may choose to enable selective access to resources
using the Java 2 protection model. The mechanism used is Java EE product
dependent.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:30"></a><font size="1PT">JavaEE:SPEC:30</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">5.2</font></TD><TD align="left" valign="center"><font size="1PT"> Caller Authorization
A Java EE product must enforce the access control rules specified at deployment time
(see Section Java EE.3.6, Deployment Requirements) and more fully described in
the EJB and servlet specifications.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:31"></a><font size="1PT">JavaEE:SPEC:31</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">5.3</font></TD><TD align="left" valign="center"><font size="1PT"> Propagated Caller Identities.
It must be possible to configure a Java EE product so that a propagated caller identity is
used in all authorization decisions. With this configuration, for all calls to all
enterprise beans from a single application within a single Java EE product, the
principal name returned by the EJBContext method getCallerPrincipal must be
the same as that returned by the first enterprise bean in the call chain. If the first
enterprise bean in the call chain is called by a servlet or JSP page, the principal
name must be the same as that returned by the HttpServletRequest method
getUserPrincipal in the calling servlet or JSP page. (However, if the
HttpServletRequest method getUserPrincipal returns null, the principal used in
calls to enterprise beans is not specified by this specification, although it must still
be possible to configure enterprise beans to be callable by such components.)
Note that this does not require delegation of credentials, only identification of
the caller. A single principal must be the principal used in authorization decisions
for access to all enterprise beans in the call chain. The requirements in this section
apply only when a Java EE product has been configured to propagate 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">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="JavaEE:SPEC:32"></a><font size="1PT">JavaEE:SPEC:32</font></TD><TD align="center" valign="center"><font size="1PT">3</font></TD><TD align="center" valign="center"><font size="1PT">5.4</font></TD><TD align="left" valign="center"><font size="1PT"> Run As Identities
Java EE products must also support the Run As capability that allows the Application
Component Provider and the Deployer to specify an identity under which an
enterprise bean or web component must run. In this case it is the Run As identity
that is propagated to subsequent components, rather than the original 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">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="JavaEE:SPEC:33"></a><font size="1PT">JavaEE:SPEC:33</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"> All Java EE products must implement the access control semantics described in the
EJB, JSP, and servlet specifications, and provide a means of mapping the
deployment descriptor security roles to the actual roles exposed by a Java EE product
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:34"></a><font size="1PT">JavaEE:SPEC:34</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"> While most Java EE products will allow the Deployer to customize the role
mappings and change the assignment of roles to methods, all Java EE products must
support the ability to deploy applications and components using exactly the
mappings and assignments specified in their 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="JavaEE:SPEC:35"></a><font size="1PT">JavaEE:SPEC:35</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">As described in the EJB specification and the servlet specification, a Java EE
product must provide a deployment tool or tools capable of assigning the security
roles in deployment descriptors to the entities that are used to determine role
membership at authorization 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">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="JavaEE:SPEC:37"></a><font size="1PT">JavaEE:SPEC:37</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"> An application might define a role representing all authenticated
and unauthenticated users and configure some enterprise bean
methods to be accessible by this role.
To support such usage, this specification requires that it be possible to map an
application defined security role to the universal set of application principals
independent of 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">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:39"></a><font size="1PT">JavaEE:SPEC:39</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Servlets and JSP pages demarcate a transaction using the javax.transaction.UserTransaction interface which is defined in the JTA 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="JavaEE:SPEC:40"></a><font size="1PT">JavaEE:SPEC:40</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Servlets and JSP pages may access multiple resource managers and invoke multiple enterprise beans within a single transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:40.1"></a><font size="1PT">JavaEE:SPEC:40.1</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The specified transaction context is automatically propagated to the enterprise beans and transactional resource managers.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:40.2"></a><font size="1PT">JavaEE:SPEC:40.2</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">The result of the propagation may be subject to the enterprise bean transaction attributes. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:43"></a><font size="1PT">JavaEE:SPEC:43</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1</font></TD><TD align="left" valign="center"><font size="1PT">Servlet filters may use transactional resources in a local transaction mode within their doFilter 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="JavaEE:SPEC:45"></a><font size="1PT">JavaEE:SPEC:45</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.1</font></TD><TD align="left" valign="center"><font size="1PT">The Java EE platform must provide an object implementing the javax.transaction.UserTransaction interface to all web 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="JavaEE:SPEC:46"></a><font size="1PT">JavaEE:SPEC:46</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.1</font></TD><TD align="left" valign="center"><font size="1PT">The platform must publish the UserTransaction object in the Java" Naming and Directory Interface (JNDI) name space available to web components under the name java:comp/UserTransaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:47"></a><font size="1PT">JavaEE:SPEC:47</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.1</font></TD><TD align="left" valign="center"><font size="1PT">If a web component invokes an enterprise bean from a thread associated with a JTA transaction, the Java EE platform must propagate the transaction context with the enterprise bean invocation. Whether the target enterprise bean will be invoked in this transaction context or not is determined by the rules defined in the EJB 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="JavaEE:SPEC:47.1"></a><font size="1PT">JavaEE:SPEC:47.1</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.1</font></TD><TD align="left" valign="center"><font size="1PT">This transaction propagation requirement applies only to invocations of enterprise beans in the same Java EE product instance as the invoking 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">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:49"></a><font size="1PT">JavaEE:SPEC:49</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.1</font></TD><TD align="left" valign="center"><font size="1PT">If a web component accesses a transactional resource manager from a thread associated with a JTA transaction, the Java EE platform must ensure that the re-source access is included as part of the JTA transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:50"></a><font size="1PT">JavaEE:SPEC:50</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.1</font></TD><TD align="left" valign="center"><font size="1PT">If a web component creates a thread, the Java EE platform must ensure that the newly created thread is not associated with any JTA transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:51"></a><font size="1PT">JavaEE:SPEC:51</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.1</font></TD><TD align="left" valign="center"><font size="1PT">The Product Provider is not required to support the importing of a transaction context from a client to a web component.</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="JavaEE:SPEC:52"></a><font size="1PT">JavaEE:SPEC:52</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">The Product Provider is not required to support transaction context propagation via an HTTP request across web components.</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="JavaEE:SPEC:53"></a><font size="1PT">JavaEE:SPEC:53</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">When a web component is invoked through the RequestDispatcher interface, any active transaction context must be propagated to the called 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">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="JavaEE:SPEC:54"></a><font size="1PT">JavaEE:SPEC:54</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">Transactions may not span web requests from a 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">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="JavaEE:SPEC:54.1"></a><font size="1PT">JavaEE:SPEC:54.1</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.2</font></TD><TD align="left" valign="center"><font size="1PT">Returning from the service method with an active transaction context is an error. The web container is required to detect this error and abort the transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:65"></a><font size="1PT">JavaEE:SPEC:65</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">The Product Provider must provide support for transactions as defined in the EJB 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">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:66"></a><font size="1PT">JavaEE:SPEC:66</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.5</font></TD><TD align="left" valign="center"><font size="1PT">The Product Provider is not required to provide transaction management support for application clients.</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="JavaEE:SPEC:67"></a><font size="1PT">JavaEE:SPEC:67</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.6</font></TD><TD align="left" valign="center"><font size="1PT">The Product Provider is not required to provide transaction management support for applets.</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="JavaEE:SPEC:68"></a><font size="1PT">JavaEE:SPEC:68</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.7</font></TD><TD align="left" valign="center"><font size="1PT">A Java EE product must support a JDBC technology database as a transactional resource manager. The platform must enable transactional JDBC API acess from web components and enterprise beans.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:69"></a><font size="1PT">JavaEE:SPEC:69</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.7</font></TD><TD align="left" valign="center"><font size="1PT">It must be possible to access the JDBC technology database from multiple application components within a single transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:70"></a><font size="1PT">JavaEE:SPEC:70</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.7</font></TD><TD align="left" valign="center"><font size="1PT">A Java EE product must provide a transaction manager that is capable of coordinating two-phase commit operations across multiple XA-capable JDBC databases.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:71"></a><font size="1PT">JavaEE:SPEC:71</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.7</font></TD><TD align="left" valign="center"><font size="1PT"> If a JDBC driver supports the Java Transaction API's XA interfaces(in the javax.transaction.xa package), then the Java EE product must be capable of using the XA interfaces provided by the JDBC driver to accomplish two-phase commit 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">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="JavaEE:SPEC:72"></a><font size="1PT">JavaEE:SPEC:72</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.8</font></TD><TD align="left" valign="center"><font size="1PT">The platform must enable transactional JMS access from servlets, JSP pages, and enterprise beans. It must be possible to access the JMS provider from multiple application components within a single transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:73"></a><font size="1PT">JavaEE:SPEC:73</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.9</font></TD><TD align="left" valign="center"><font size="1PT">A Java EJava EE product must suport resource adapters that use XATransaction mode as transactional resource managers. The platform must enable transactional access to the resource adapter from servlets, JSP pages, and enterprise beans</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:74"></a><font size="1PT">JavaEE:SPEC:74</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">2.9</font></TD><TD align="left" valign="center"><font size="1PT">It must be possible to access the resource adapter from multiple application components within a single transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:75"></a><font size="1PT">JavaEE:SPEC:75</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">3.1</font></TD><TD align="left" valign="center"><font size="1PT">The Product Provider is not required to implement any particular protocol for transaction interportibility across multiple Java EE products. Java EE compatibility requires neither interportability among identical Java EE products from the same Product Provider, nor among heterogeneous Java EE products from multiple Product Providers.</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="JavaEE:SPEC:76"></a><font size="1PT">JavaEE:SPEC:76</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">3.2</font></TD><TD align="left" valign="center"><font size="1PT">All Java EE products are required to support the javax.transaction.xa.XAResource interface, as specified in the Connector 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="JavaEE:SPEC:77"></a><font size="1PT">JavaEE:SPEC:77</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">3.2</font></TD><TD align="left" valign="center"><font size="1PT">All Java EE products are required to support the javax.transaction.xa.XAResource interface, for performing two-phase commit operations on JDBC drivers that support the JTA XA APIs. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:78"></a><font size="1PT">JavaEE:SPEC:78</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">3.2</font></TD><TD align="left" valign="center"><font size="1PT">This specification does not require that JDBC drivers or JMS providers use the javax.transaction.xa.XAResource interface, although they may use this interface and in all cases they must meet the transactional resource manager requirements as described in the specification.</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="JavaEE:SPEC:79"></a><font size="1PT">JavaEE:SPEC:79</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">3.2</font></TD><TD align="left" valign="center"><font size="1PT">It must be possible to combine operations on one or more JDBC databases, one or more JMS sessions, one or more enterprise beans, and multiple resource adapters supporting the XATransaction mode in a single JTA transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:80"></a><font size="1PT">JavaEE:SPEC:80</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">4.1</font></TD><TD align="left" valign="center"><font size="1PT">Containers may choose to provide local transaction optimisation, but are not required to do so. Local Transaction optimization must be transparent to a Java EE 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="JavaEE:SPEC:82"></a><font size="1PT">JavaEE:SPEC:82</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">Containers must not attempt to share connections that are marked unshareable</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:83"></a><font size="1PT">JavaEE:SPEC:83</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">If a connection is not marked unshareable, it must be transaparent to the application whether the connection is actually shared or not.</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="JavaEE:SPEC:84"></a><font size="1PT">JavaEE:SPEC:84</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">Java EE application components may use the optional deployment descriptor element res-sharing-scope to indicate whether a connection to a resource manager is shareable or unshareable. Containers must assume connections to be shareable if no deployment hint is provided. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:85"></a><font size="1PT">JavaEE:SPEC:85</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">Java EE application components may cache connection objects and reuse them across multiple transaction. Containers that provide connection sharing must transaparently switch such cached connection objects (at dispatch time) to point to an appropriate shared connection with the correct transaction scope. Refer to the Connector specification for detailed description of connection sharing.</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="JavaEE:SPEC:86"></a><font size="1PT">JavaEE:SPEC:86</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">If the deployer configures a non-XA capable JDBC resource manager in a transaction, then a Java EE Product Provider may restrict all JDBC resource manager in a transaction to that non-XA-capable JDBC resource manager. Otherwise a Java EE Product Provider must support use of multiple XA-capable JDBC resource managers within a transaction.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:87"></a><font size="1PT">JavaEE:SPEC:87</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">A Java EE Product Provider may restrict the security configuration of all JDBC connections within a transaction to a single user identity. A Java EE Product Provider is not required to support transactions where more than one JDBC identity is used. Specifically, this means that transactions that require the use of more than one JDBC security identity (as can explicitly be done via component provided user name and password) may not be portable.</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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:88"></a><font size="1PT">JavaEE:SPEC:88</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">A Java EE Product Provider may make restrictions resulting in a transaction being restricted to a single JMS resource manager and user identity.</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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:89"></a><font size="1PT">JavaEE:SPEC:89</font></TD><TD align="center" valign="center"><font size="1PT">4</font></TD><TD align="center" valign="center"><font size="1PT">6</font></TD><TD align="left" valign="center"><font size="1PT">When both a JDBC resource manager and JMS resource manager are used in the same transaction, A Java EE Product Provider may restrict both to a pairing that allows their combination to deliver the full transactional semantics required by the application, and may restrict the security identity of both to a single identity. To fully support such usage, portable applications that wish to include JDCB and JMS access in a single global transaction must not mark the corresponding transactional resources as "un sharable" </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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:90"></a><font size="1PT">JavaEE:SPEC:90</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">A Java EE product must support the use of multiple XA-capable resource adapters in a single transaction. To support such a scenario, full two-phase commit support is required.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:91"></a><font size="1PT">JavaEE:SPEC:91</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">A JMS provider may be provided as an XA-capable resource adapter. In such a case, it must be possible to include JMS operations in the same global transactions as other resource adapters. </font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:92"></a><font size="1PT">JavaEE:SPEC:92</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">While JDBC drivers are not required to be XA-capable, a JDBC driver may be delivered as an XA-capable resource adapter. In such a case, it must be possible to include JDBC operations in the same global transaction as other XA-capable resource adapters.</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:93"></a><font size="1PT">JavaEE:SPEC:93</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT"></font></TD><TD align="left" valign="center"><font size="1PT"> In general, lookups of objects in the JNDI java: namespace are
required to return a new instance of the requested object on each
lookup.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:93.1"></a><font size="1PT">JavaEE:SPEC:93.1</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">
Lookups of objects in the JNDI java: namespace are NOT required
to return a new instance of the requested object every time if
the container knows the object is immutable (for example,
objects of type java.lang.String), or knows that the
application can t change the state of the 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">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="JavaEE:SPEC:93.2"></a><font size="1PT">JavaEE:SPEC:93.2</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">
Lookups of objects in the JNDI java: namespace are NOT required
to return a new instance of the requested object every time if
the object is defined to be a singleton, such that only one
instance of the object may exist in the 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">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="JavaEE:SPEC:93.3"></a><font size="1PT">JavaEE:SPEC:93.3</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">
Lookups of objects in the JNDI java: namespace are NOT required
to return a new instance of the requested object every time if
the name used for the lookup is defined to return an instance
of the object that might be shared. The name java:comp/ORB is
such a 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">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="JavaEE:SPEC:97"></a><font size="1PT">JavaEE:SPEC:97</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">1.2</font></TD><TD align="left" valign="center"><font size="1PT">
Java EE application clients, enterprise beans, and web components
are required to have access to a JNDI naming environment.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:98"></a><font size="1PT">JavaEE:SPEC:98</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 container also provides the tools that allow the Deployer to
create and manage the environment of each application 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">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:99"></a><font size="1PT">JavaEE:SPEC:99</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"> All instances of an application component within the same
container share the same environment entries.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:100"></a><font size="1PT">JavaEE:SPEC:100</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT"> A component can create a javax.naming.InitialContext object by
using the constructor with no arguments, and lookup directly
an environment entry from this InitialContext (e.g.
initCtx.lookup("java:comp/env/foo/name1")).
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:101"></a><font size="1PT">JavaEE:SPEC:101</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT"> A component can lookup the naming environment via the
InitialContext under the name "java:comp/env". The component can
then use the environment naming context to lookup an environment
entry (e.g. myEnv.lookup("foo/name1")).
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:102"></a><font size="1PT">JavaEE:SPEC:102</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
An environment entry is scoped to the application component whose
declaration contains the env-entry element. This means that the
environment entry is not accessible from other application
components at runtime, and that other application components may
define env-entry elements with the same enventry- name without
causing a name conflict.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:103"></a><font size="1PT">JavaEE:SPEC:103</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the following Java
types: String, Character, Byte, Short, Integer, Long, Boolean,
Double, and Float.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:103.1"></a><font size="1PT">JavaEE:SPEC:103.1</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the String Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:103.2"></a><font size="1PT">JavaEE:SPEC:103.2</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the Character Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:103.3"></a><font size="1PT">JavaEE:SPEC:103.3</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the Byte Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:103.4"></a><font size="1PT">JavaEE:SPEC:103.4</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the Short Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:103.5"></a><font size="1PT">JavaEE:SPEC:103.5</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the Integer Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:103.6"></a><font size="1PT">JavaEE:SPEC:103.6</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the Double Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:103.7"></a><font size="1PT">JavaEE:SPEC:103.7</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the Boolean Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:103.8"></a><font size="1PT">JavaEE:SPEC:103.8</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the Long Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:103.9"></a><font size="1PT">JavaEE:SPEC:103.9</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The environment entry values may be one of the Float Java 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">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:113"></a><font size="1PT">JavaEE:SPEC:113</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">
The Java EE Product Provider must provide a deployment tool that
allows the Deployer to set and modify the values of the
application component's environment entries.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:114"></a><font size="1PT">JavaEE:SPEC:114</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">
The Java EE Product Provider must implement the java:comp/env
environment naming context, and provide it to the application
component instances at runtime. The naming context must include
all the environment entries declared by the Application Component
Provider, with their values supplied in the deployment descriptor
or set 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="JavaEE:SPEC:115"></a><font size="1PT">JavaEE:SPEC:115</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">
The environment naming context implemented by the Java EE Product
Provider must allow the Deployer to create subcontexts if they
are needed by an application 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="JavaEE:SPEC:116"></a><font size="1PT">JavaEE:SPEC:116</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">2.4</font></TD><TD align="left" valign="center"><font size="1PT">
The container must ensure that the application component
instances have only read access to their environment
variables. The container must throw the
javax.naming.OperationNotSupportedException from all the methods
of the javax.naming.Context interface that modify the environment
naming context and its subcontexts.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:117"></a><font size="1PT">JavaEE:SPEC:117</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">3.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
An EJB reference is scoped to the application component whose
declaration contains the ejb-ref element. This means that the EJB
reference is not accessible from other application components at
runtime, and that other application components may define ejb-ref
elements with the same ejb-ref-name without causing a name
conflict.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:118"></a><font size="1PT">JavaEE:SPEC:118</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">3.2</font></TD><TD align="left" valign="center"><font size="1PT">
The Java EE Product Provider must support deployment of application
using ejb-link elements to reference target enterprise beans
that can be in any ejb-jar file in the same Java EE application as the
referencing application 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="JavaEE:SPEC:119"></a><font size="1PT">JavaEE:SPEC:119</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">3.2</font></TD><TD align="left" valign="center"><font size="1PT">
The Java EE Product Provider must support deployment of applications
packaging multiple beans with the same ejb-name (but packaged in
distinct ejb-jar's) and using ejb-link elements following the
ejb-jar-path#ejb-name syntax. In this manner, multiple beans with
the same ejb-name may be uniquely identified when the Application
Assembler cannot change ejb-names.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:120"></a><font size="1PT">JavaEE:SPEC:120</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">5.4</font></TD><TD align="left" valign="center"><font size="1PT">
At the minimum, the deployment tools provided by the Java EE Product
Provider must be able to preserve the application assembly
information in the ejb-link elements by binding an EJB reference
to the home interface of the specified target 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">false</font></TD><TD align="center" valign="center"><font size="1PT">platform</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="JavaEE:SPEC:121"></a><font size="1PT">JavaEE:SPEC:121</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">8.4</font></TD><TD align="left" valign="center"><font size="1PT">
At the minimum, the deployment tools provided by the Java EE Product
Provider must be able to inform the Deployer of any unresolved
EJB references, and allow him or her to resolve an EJB reference
by binding it to a specified compatible target 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">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="JavaEE:SPEC:122"></a><font size="1PT">JavaEE:SPEC:122</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
It is possible to obtain multiple connections from a Resource
Manager Connection Factory Reference by calling the factory
object multiple times.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:123"></a><font size="1PT">JavaEE:SPEC:123</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
By default, connections to a resource manager are shareable
across other application components in the application that use
the same resource in the same transaction 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">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="JavaEE:SPEC:124"></a><font size="1PT">JavaEE:SPEC:124</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.1.2</font></TD><TD align="left" valign="center"><font size="1PT">
The Application Component Provider can specify that connections
obtained from a resource manager connection factory reference are
not shareable by specifying the value of the res-sharing-scope
deployment descriptor element to be Unshareable.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:125"></a><font size="1PT">JavaEE:SPEC:125</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.1.3</font></TD><TD align="left" valign="center"><font size="1PT">
A resource manager connection factory reference is scoped to the
application component whose declaration contains the resource-ref
element. This means that the resource manager connection factory
reference is not accessible from other application components at
runtime, and that other application components may define
resource-ref elements with the same res-ref-name without causing
a name conflict.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:126"></a><font size="1PT">JavaEE:SPEC:126</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.1.4</font></TD><TD align="left" valign="center"><font size="1PT">
The Application Component Provider must use the
javax.jms.QueueConnectionFactory or the
javax.jms.TopicConnectionFactory for obtaining JMS connections.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:127"></a><font size="1PT">JavaEE:SPEC:127</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">
The Java EE Product Provider is responsible for providing the
implementation of the resource manager connection factory classes
that are required by this 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="JavaEE:SPEC:128"></a><font size="1PT">JavaEE:SPEC:128</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">
If the Application Component Provider set the res-auth of a
resource reference to Application, the container must allow the
application component to perform explicit programmatic sign on
using the resource manager's API.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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">deprecated</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:129"></a><font size="1PT">JavaEE:SPEC:129</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">
If the Application Component Provider sets the res-sharing-scope
of a resource manager connection factory reference to
Unshareable, the container must not attempt to share the
connections obtained from the resource manager connection factory
reference.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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">deprecated</font></TD><TD align="center" valign="center"><font size="1PT">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:130"></a><font size="1PT">JavaEE:SPEC:130</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">6.3</font></TD><TD align="left" valign="center"><font size="1PT">
The container must provide tools that allow the Deployer to set
up resource sign on information for the resource manager
references whose res-auth element is set to Container. The
minimum requirement is that the Deployer must be able to specify
the username/password information for each resource manager
connection factory reference declared by the application
component, and the container must be able to use the
username/password combination for user authentication when obtaining
a connection by invoking the resource manager connection factory.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:132"></a><font size="1PT">JavaEE:SPEC:132</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">7.1.3</font></TD><TD align="left" valign="center"><font size="1PT">
A resource environment reference is scoped to the application
component whose declaration contains the resource-env-ref
element. This means that the resource environment reference is
not accessible to other application components at runtime, and
that other application components may define resource-env-ref
elements with the same resource-env-ref-name without causing a
name conflict.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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">deprecated</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:133"></a><font size="1PT">JavaEE:SPEC:133</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">7.3</font></TD><TD align="left" valign="center"><font size="1PT">
At the minimum, the deployment tools must be able to inform the
Deployer of any unresolved resource environment references, and
allow him or her to resolve a resource environment reference by
binding it to a specified compatible target object in the
environment.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:134"></a><font size="1PT">JavaEE:SPEC:134</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">8.1.3</font></TD><TD align="left" valign="center"><font size="1PT">
A message destination reference is scoped to the application
component whose declaration contains the message-destination-ref
element. This means that the message destination reference is not
accessible to other application components at runtime, and that
other application components may define message-destination-ref
elements with the same message-destination-refname without
causing a name conflict.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:135"></a><font size="1PT">JavaEE:SPEC:135</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">8.2</font></TD><TD align="left" valign="center"><font size="1PT">
To avoid the need to rename message destinations to have unique
names within an entire Java EE application, the Application
Assembler may use the following syntax in the
message-destination-link element of the referencing application
component. The Application Assembler specifies the path name of
the ejb-jar file containing the referenced message destination
and appends the message-destination-name of the target
destination separated from the path name by #. The path name is
relative to the referencing application component jar file. In
this manner, multiple destinations with the same
message-destination-name may be uniquely identified.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:136"></a><font size="1PT">JavaEE:SPEC:136</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">8.4</font></TD><TD align="left" valign="center"><font size="1PT">
The Java EE Product Provider must provide the deployment tools that
allow the Deployer to perform the tasks described in subsection
5.8.3 of the Java EE platform spec.
The deployment tools provided by the Java EE Product
Provider must be able to process the information supplied in the
message-destination-ref elements 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">false</font></TD>
</TR>
<TR>
<TD align="center" valign="center"><a name="JavaEE:SPEC:137"></a><font size="1PT">JavaEE:SPEC:137</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">9.2</font></TD><TD align="left" valign="center"><font size="1PT">
The Java EE Product Provider is responsible for providing an
appropriate UserTransaction object as required by this
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="JavaEE:SPEC:138"></a><font size="1PT">JavaEE:SPEC:138</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">10.2</font></TD><TD align="left" valign="center"><font size="1PT">
The container is required to provide the java:comp/ORB name for
all components except applets. applications can find an
appropriate object implementing the ORB interface by looking up
the JNDI name java:comp/ORB.
</font></TD><TD align="center" valign="center"><font size="1PT">true</font></TD><TD align="center" valign="center"><font 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="JavaEE:SPEC:139"></a><font size="1PT">JavaEE:SPEC:139</font></TD><TD align="center" valign="center"><font size="1PT">5</font></TD><TD align="center" valign="center"><font size="1PT">10.2</font></TD><TD align="left" valign="center"><font size="1PT">
Any reference to a ORB object provided by the