Author: pete.muir(a)jboss.org
Date: 2009-07-21 14:05:26 -0400 (Tue, 21 Jul 2009)
New Revision: 3119
Modified:
tck/trunk/impl/src/main/resources/tck-audit.xml
Log:
Mark some assertions untestable
Modified: tck/trunk/impl/src/main/resources/tck-audit.xml
===================================================================
--- tck/trunk/impl/src/main/resources/tck-audit.xml 2009-07-21 16:27:31 UTC (rev 3118)
+++ tck/trunk/impl/src/main/resources/tck-audit.xml 2009-07-21 18:05:26 UTC (rev 3119)
@@ -4160,12 +4160,15 @@
</section>
<section id="11.4" title="Alternative metadata sources">
- <assertion id="a">
+ <assertion id="a" testable="false">
<text>The interfaces |AnnotatedType|, |AnnotatedField|, |AnnotatedMethod|,
|AnnotatedConstructor| and |AnnotatedParameter| in the package
|javax.enterprise.inject.spi| allow a portable extension to specify metadata that
overrides the annotations that exist on a bean class. The portable extension is
responsible for implementing the interfaces, thereby exposing the metadata to the
container.</text>
+ <note>Statement of intent</note>
</assertion>
- <assertion id="b">
+ <assertion id="b" testable="false">
<text>The interface |javax.enterprise.inject.spi.Annotated| exposes the
overriding annotations and type declarations.</text>
+ <note>Statement of intent</note>
+
</assertion>
<assertion id="c">
@@ -4194,8 +4197,9 @@
</section>
<section id="11.5" title="Container lifecycle events">
- <assertion id="a">
+ <assertion id="a" testable="false">
<text>During the application initialization process, the container fires a
series of events, allowing portable extensions to integrate with the container
initialization process defined in Section 12.2, "Application initialization
lifecycle".</text>
+ <note>Generic statement</note>
</assertion>
<assertion id="b">
@@ -4512,14 +4516,16 @@
<text>If a bean is deployed in an archive or directory that does not contain
a file named |beans.xml| in the metadata directory, it will not be discovered by the
container.</text>
</assertion>
- <assertion id="d">
+ <assertion id="d" testable="false">
<text>If a bean class is deployed in two different bean deployment archives,
non-portable behaviour results. Portable applications must deploy each bean class in
exactly one bean deployment archive.</text>
+ <note>Describes undefined behavior</note>
</assertion>
</section>
<section id="12.2" title="Application initialization
lifecycle">
- <assertion id="a">
+ <assertion id="a" testable="false">
<text>When an application is started, the container performs the following
steps.</text>
+ <note>Description</note>
</assertion>
<assertion id="b">
@@ -4619,16 +4625,19 @@
<text>Deployment problems are detected by the container at initialization
time. If a deployment problem exists in a deployment, initialization will be aborted by
the container.</text>
</assertion>
- <assertion id="d">
+ <assertion id="d" testable="false">
<text>The container is permitted to define a non-portable mode, for use at
development time, in which some definition errors and deployment problems do not cause
application initialization to abort.</text>
+ <note>Specifies undefined behavior</note>
</assertion>
- <assertion id="e">
+ <assertion id="e" testable="false">
<text>Exceptions represent problems that may not be detected until they
actually occur at runtime. All exceptions defined by this specification are unchecked
exceptions.</text>
+ <note>Explanatory note</note>
</assertion>
- <assertion id="f">
+ <assertion id="f" testable="false">
<text>All exceptions defined by this specification may be safely caught and
handled by the application.</text>
+ <note>Explanatory note</note>
</assertion>
</section>