Author: pete.muir(a)jboss.org
Date: 2009-03-29 18:30:35 -0400 (Sun, 29 Mar 2009)
New Revision: 2256
Modified:
tck/trunk/impl/src/main/resources/tck-audit.xml
Log:
assertions for chapter 11
Modified: tck/trunk/impl/src/main/resources/tck-audit.xml
===================================================================
--- tck/trunk/impl/src/main/resources/tck-audit.xml 2009-03-29 19:35:48 UTC (rev 2255)
+++ tck/trunk/impl/src/main/resources/tck-audit.xml 2009-03-29 22:30:35 UTC (rev 2256)
@@ -6094,15 +6094,195 @@
</section>
<section id="11" title="Packaging and Deployment">
+
</section>
- <section id="11.6" title="Activities">
+ <section id="11.1" title="Deployment lifecycle">
<assertion id="a">
- <text>The method createActivity() creates a new child activity of an
activity:</text>
+ <text>First, the container performs bean discovery and registers Bean and
Observer objects for the discovered beans. The container detects definition errors by
validating the bean classes and metadata, throwing a DeploymentException and aborting
deployment of the application if any definition errors exist, as defined in Section 10.1,
"Definition errors".</text>
+ <note>Test that beans and observers are registered and definition exceptions
occur before @Initialized, and that this puts causes the app deployment to
fail</note>
</assertion>
<assertion id="b">
+ <text>Next, the container raises an event of type @Initialized Manager,
allowing the application or third-party frameworks to register additional Bean and
Observer objects.</text>
+ <note>Test that the @Initialized event is called, and that beans are
registered</note>
+ </assertion>
+
+ <assertion id="c">
+ <text>Next, the container detects deployment problems by validating bean
dependencies and specialization, throwing a DeploymentException and aborting deployment of
the application if any deployment problems exist, as defined in Section 10.2,
"Deployment problems".</text>
+ <note>Test that validation happens after @Initialized and before @Deployed
and that deployment problems cause deployment to fail</note>
+ </assertion>
+
+ <assertion id="d">
+ <text>Next, the container raises an event of type @Deployed
Manager.</text>
+ <note>Test that the @Deployed event is called</note>
+ </assertion>
+
+ <assertion id="e">
+ <text>Finally, the container begins directing requests to the
application.</text>
+ <note>Test that the app is usable</note>
+ </assertion>
+
+ </section>
+
+ <section id="11.2" title="Bean discovery">
+
+ <assertion id="a" implied="true">
+ <text>When bean discovery occurs, the container considers any beans.xml file
in any metadata directory of the application classpath (standalone WAR)</text>
+ </assertion>
+
+ <assertion id="b" implied="true">
+ <text>When bean discovery occurs, the container considers any beans.xml file
in any metadata directory of the application classpath (jar in WEB-INF/lib of standalone
WAR)</text>
+ </assertion>
+
+ <assertion id="c" implied="true">
+ <text>When bean discovery occurs, the container considers any beans.xml file
in any metadata directory of the application classpath (WAR in EAR)</text>
+ </assertion>
+
+ <assertion id="d" implied="true">
+ <text>When bean discovery occurs, the container considers any beans.xml file
in any metadata directory of the application classpath (jar in WEB-INF/lib of WAR in
EAR)</text>
+ </assertion>
+
+ <assertion id="e" implied="true">
+ <text>When bean discovery occurs, the container considers any beans.xml file
in any metadata directory of the application classpath (ejb-jar)</text>
+ </assertion>
+
+ <assertion id="f" implied="true">
+ <text>When bean discovery occurs, the container considers any beans.xml file
in any metadata directory of the application classpath (jar in EAR lib
directory)</text>
+ </assertion>
+
+ <assertion id="g">
+ <text>When bean discovery occurs, the container considers any ejb-jar.xml
file in any metadata directory of the application classpath that also contains a beans.xml
file</text>
+ <note>What does this mean?</note>
+ </assertion>
+
+ <assertion id="h" implied="true">
+ <text>When bean discovery occurs, the container considers any Java class in
any archive or directory in the classpath that has a beans.xml file in the metadata
directory (standalone WAR)</text>
+ </assertion>
+
+ <assertion id="i" implied="true">
+ <text>When bean discovery occurs, the container considers any Java class in
any archive or directory in the classpath that has a beans.xml file in the metadata
directory (jar in WEB-INF/lib of standalone WAR)</text>
+ </assertion>
+
+ <assertion id="j" implied="true">
+ <text>When bean discovery occurs, the container considers any Java class in
any archive or directory in the classpath that has a beans.xml file in the metadata
directory (WAR in EAR)</text>
+ </assertion>
+
+ <assertion id="k" implied="true">
+ <text>When bean discovery occurs, the container considers any Java class in
any archive or directory in the classpath that has a beans.xml file in the metadata
directory (jar in WEB-INF/lib of WAR in EAR)</text>
+ </assertion>
+
+ <assertion id="l" implied="true">
+ <text>When bean discovery occurs, the container considers any Java class in
any archive or directory in the classpath that has a beans.xml file in the metadata
directory (ejb-jar)</text>
+ </assertion>
+
+ <assertion id="m" implied="true">
+ <text>When bean discovery occurs, the container considers any Java class in
any archive or directory in the classpath that has a beans.xml file in the metadata
directory (jar in EAR lib dir)</text>
+ </assertion>
+
+ <assertion id="n">
+ <text>First, the container discovers all binding types~, stereotypes and
interceptor binding types~ declared in XML, according to the rules of Section 9.4,
"Stereotype, binding type and interceptor binding type
declarations".</text>
+ </assertion>
+
+ <assertion id="o">
+ <text>First, the container discovers all ~binding types~, stereotypes ~and
interceptor binding types~ declared in XML, according to the rules of Section 9.4,
"Stereotype, binding type and interceptor binding type
declarations".</text>
+ </assertion>
+
+ <assertion id="p">
+ <text>First, the container discovers all ~binding types, stereotypes and~
interceptor binding types declared in XML, according to the rules of Section 9.4,
"Stereotype, binding type and interceptor binding type
declarations".</text>
+ </assertion>
+
+ <assertion id="q">
+ <text>The container automatically discovers simple beans (according to the
rules of Section 3.2.1, "Which Java classes are beans?") ~and session beans
(according to the rules of Section 3.3.2, "Which EJBs are beans?") deployed
and/or declared in these locations and searches the bean classes for producer methods,
producer fields, disposal methods and observer methods declared using
annotations.~</text>
+ <note>Check all archive types enumerated above</note>
+ </assertion>
+
+ <assertion id="r">
+ <text>The container automatically discovers ~simple beans (according to the
rules of Section 3.2.1, "Which Java classes are beans?") and~ session beans
(according to the rules of Section 3.3.2, "Which EJBs are beans?")~ deployed
and/or declared in these locations and searches the bean classes for producer methods,
producer fields, disposal methods and observer methods declared using
annotations.~</text>
+ <note>Check all archive types enumerated above</note>
+ </assertion>
+
+ <assertion id="s">
+ <text>The container automatically discovers ~simple beans (according to the
rules of Section 3.2.1, "Which Java classes are beans?") and session beans
(according to the rules of Section 3.3.2, "Which EJBs are beans?") deployed
and/or declared in these locations and searches the bean classes for~ producer methods,
~producer fields, disposal methods and observer methods~ declared using
annotations.</text>
+ <note>Check all archive types enumerated above, and session beans and simple
beans</note>
+ </assertion>
+
+ <assertion id="t">
+ <text>The container automatically discovers ~simple beans (according to the
rules of Section 3.2.1, "Which Java classes are beans?") and session beans
(according to the rules of Section 3.3.2, "Which EJBs are beans?") deployed
and/or declared in these locations and searches the bean classes for producer methods~,
producer fields~, disposal methods and observer methods~ declared using
annotations.</text>
+ <note>Check all archive types enumerated above, and session beans and simple
beans</note>
+ </assertion>
+
+ <assertion id="u">
+ <text>The container automatically discovers ~simple beans (according to the
rules of Section 3.2.1, "Which Java classes are beans?") and session beans
(according to the rules of Section 3.3.2, "Which EJBs are beans?") deployed
and/or declared in these locations and searches the bean classes for producer methods,
producer fields,~ disposal methods~ and observer methods~ declared using
annotations.</text>
+ <note>Check all archive types enumerated above, and session beans and simple
beans</note>
+ </assertion>
+
+ <assertion id="v">
+ <text>The container automatically discovers~ simple beans (according to the
rules of Section 3.2.1, "Which Java classes are beans?") and session beans
(according to the rules of Section 3.3.2, "Which EJBs are beans?") deployed
and/or declared in these locations and searches the bean classes for producer methods,
producer fields, disposal methods and~ observer methods declared using
annotations.</text>
+ <note>Check all archive types enumerated above, and session beans and simple
beans</note>
+ </assertion>
+
+ <assertion id="w">
+ <text>The container discovers beans~, disposal methods and observer methods~
defined using XML by parsing the beans.xml files according to the rules of Chapter 9, XML
based metadata.</text>
+ <note>Check all archive types enumerated above, simple beans, session beans,
producer methods and producer fields</note>
+ </assertion>
+
+ <assertion id="x">
+ <text>The container discovers ~beans, ~disposal methods ~and observer
methods~ defined using XML by parsing the beans.xml files according to the rules of
Chapter 9, XML based metadata.</text>
+ <note>Check all archive types enumerated above</note>
+ </assertion>
+
+ <assertion id="y">
+ <text>The container discovers ~beans, disposal methods and~ observer methods
defined using XML by parsing the beans.xml files according to the rules of Chapter 9, XML
based metadata.</text>
+ <note>Check all archive types enumerated above</note>
+ </assertion>
+
+ <assertion id="z">
+ <text>Next, the container determines which beans~, interceptors and
decorators are enabled,~ according to the rules defined in Section 2.5.6, "Enabled
deployment types", Section A.3.7, "Interceptor enablement and ordering" and
Section A.5.5, "Decorator enablement and ordering", taking into account any
<Deploy>, ~<Interceptors> and <Decorators>~
declarations in the beans.xml files.</text>
+ </assertion>
+
+ <assertion id="aa">
+ <text>Next, the container determines which ~beans,~ interceptors ~and
decorators~ are enabled, according to the rules defined in Section 2.5.6, "Enabled
deployment types", Section A.3.7, "Interceptor enablement and ordering" and
Section A.5.5, "Decorator enablement and ordering", taking into account any
~<Deploy>,~ <Interceptors> ~and <Decorators>~
declarations in the beans.xml files.</text>
+ </assertion>
+
+ <assertion id="ab">
+ <text>Next, the container determines which ~beans, interceptors and~
decorators are enabled, according to the rules defined in Section 2.5.6, "Enabled
deployment types", Section A.3.7, "Interceptor enablement and ordering" and
Section A.5.5, "Decorator enablement and ordering", taking into account any
~<Deploy>, <Interceptors> and~ <Decorators>
declarations in the beans.xml files.</text>
+ </assertion>
+
+ <assertion id="ac">
+ <text>For each enabled bean that is not an interceptor or decorator, the
container creates an instance of Bean, and registers it by calling
Manager.addBean()</text>
+ <note>Check that interceptors aren't registered as beans, decorators
aren't registered as beans, that disabled beans aren't registered and that simple
beans, session beans, producer methods and producer fields are registered</note>
+ </assertion>
+
+ <assertion id="ad">
+ <text>For each enabled interceptor, the container creates an instance of
Interceptor and registers it by calling Manager.addInterceptor()</text>
+ </assertion>
+
+ <assertion id="ae">
+ <text>For each enabled decorator, the container creates an instance of
Decorator and registers it by calling Manager.addDecorator().</text>
+ </assertion>
+
+ <assertion id="af">
+ <text>For each observer method of an enabled bean, the container creates an
instance of Observer that implements the rules of Section 7.5.8, "Observer object for
an observer method" and registers it by calling Manager.addObserver()</text>
+ </assertion>
+ </section>
+
+ <section id="11.4" title="Providing additional XML based
metadata">
+ <assertion id="a">
+ <text>The container parses the XML stream according to the rules of Chapter
9, XML based metadata.This method may be called at any time by the application or
third-party framework.</text>
+ <note>Check that the parse method adds beans etc.</note>
+ </assertion>
+ </section>
+
+ <section id="11.6" title="Activities">
+
+ <assertion id="a" testable="false">
+ <text>The method createActivity() creates a new child activity of an
activity:</text>
+ <note>A statement of intent</note>
+ </assertion>
+
+ <assertion id="b">
<text>every bean belonging to a parent activity also belongs to the child
activity~, is eligible for injection into other beans belonging to the child activity and
may be obtained by dynamic lookup via the child activity~</text>
</assertion>