[webbeans-commits] Webbeans SVN: r2265 - tck/trunk/impl/src/main/resources.
webbeans-commits at lists.jboss.org
webbeans-commits at lists.jboss.org
Sun Mar 29 22:45:18 EDT 2009
Author: shane.bryzak at jboss.com
Date: 2009-03-29 22:45:16 -0400 (Sun, 29 Mar 2009)
New Revision: 2265
Modified:
tck/trunk/impl/src/main/resources/tck-audit.xml
Log:
highlighting, minor editing
Modified: tck/trunk/impl/src/main/resources/tck-audit.xml
===================================================================
--- tck/trunk/impl/src/main/resources/tck-audit.xml 2009-03-30 01:41:00 UTC (rev 2264)
+++ tck/trunk/impl/src/main/resources/tck-audit.xml 2009-03-30 02:45:16 UTC (rev 2265)
@@ -6100,22 +6100,22 @@
<section id="11.1" title="Deployment lifecycle">
<assertion id="a">
- <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>
+ <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>
+ <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>
+ <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>
+ <text>Next, the container raises an event of type |@Deployed Manager|.</text>
<note>Test that the @Deployed event is called</note>
</assertion>
@@ -6129,56 +6129,56 @@
<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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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">
@@ -6224,53 +6224,53 @@
</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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
@@ -6278,7 +6278,7 @@
<section id="11.6" title="Activities">
<assertion id="a" testable="false">
- <text>The method createActivity() creates a new child activity of an activity:</text>
+ <text>The method |createActivity()| creates a new child activity of an activity:</text>
<note>A statement of intent</note>
</assertion>
@@ -6323,82 +6323,82 @@
</assertion>
<assertion id="m">
- <text>Beans ~and observers~ may be registered with an activity by calling addBean() ~or addObserver()~ on the Manager object that represents the activity.</text>
+ <text>|Beans| ~and observers~ may be registered with an activity by calling |addBean()| ~or |addObserver()|~ on the |Manager| object that represents the activity.</text>
</assertion>
<assertion id="n">
- <text>~Beans and~ observers may be registered with an activity by calling ~addBean() or~ addObserver() on the Manager object that represents the activity.</text>
+ <text>~|Beans| and~ observers may be registered with an activity by calling ~|addBean()| or~ |addObserver()| on the |Manager| object that represents the activity.</text>
</assertion>
<assertion id="o">
- <text>a bean registered with the child activity is not available for injection into any bean registered with a parent activity</text>
+ <text>A bean registered with the child activity is not available for injection into any bean registered with a parent activity</text>
</assertion>
<assertion id="p">
- <text>a bean registered with a child activity is not available for injection into a ~servlet or~ EJB</text>
+ <text>A bean registered with a child activity is not available for injection into a ~servlet or~ EJB</text>
</assertion>
<assertion id="q">
- <text>a bean registered with a child activity is not available for injection into a servlet ~or EJB~</text>
+ <text>A bean registered with a child activity is not available for injection into a servlet ~or EJB~</text>
</assertion>
<assertion id="r">
- <text>a bean registered with a child activity may not be obtained by dynamic lookup via the parent activity</text>
+ <text>A bean registered with a child activity may not be obtained by dynamic lookup via the parent activity</text>
</assertion>
<assertion id="s">
- <text>an observer registered with the child activity does not receive events fired via a parent activity</text>
+ <text>An observer registered with the child activity does not receive events fired via a parent activity</text>
</assertion>
<assertion id="t">
- <text>If a bean registered with a child activity has the bean type and all bindings of some injection point of some bean registered with a direct ~or indirect~ parent activity, a DeploymentException is throw by the container at deployment time.</text>
+ <text>If a bean registered with a child activity has the bean type and all bindings of some injection point of some bean registered with a direct ~or indirect~ parent activity, a |DeploymentException| is throw by the container at deployment time.</text>
</assertion>
<assertion id="u">
- <text>If a bean registered with a child activity has the bean type and all bindings of some injection point of some bean registered with a~ direct or~ indirect parent activity, a DeploymentException is throw by the container at deployment time.</text>
+ <text>If a bean registered with a child activity has the bean type and all bindings of some injection point of some bean registered with a~ direct or~ indirect parent activity, a |DeploymentException| is throw by the container at deployment time.</text>
</assertion>
<assertion id="v">
- <text>The addInterceptor() ~and addDecorator()~ methods throw UnsupportedOperationException when called on a Manager object that represents a child activity.</text>
+ <text>The |addInterceptor()| ~and |addDecorator()|~ methods throw |UnsupportedOperationException| when called on a |Manager| object that represents a child activity.</text>
</assertion>
<assertion id="w">
- <text>The ~addInterceptor() and~ addDecorator() methods throw UnsupportedOperationException when called on a Manager object that represents a child activity.</text>
+ <text>The ~|addInterceptor()| and~ |addDecorator()| methods throw |UnsupportedOperationException| when called on a |Manager| object that represents a child activity.</text>
</assertion>
</section>
<section id="11.6.1" title="Current Activity">
<assertion id="a">
- <text>An activity may be associated with the current context for a normal scope by calling setCurrent(), passing the normal scope type</text>
+ <text>An activity may be associated with the current context for a normal scope by calling |setCurrent()|, passing the normal scope type</text>
</assertion>
<assertion id="b">
- <text>If the given scope is inactive when setCurrent() is called, a ContextNotActiveException is thrown.</text>
+ <text>If the given scope is inactive when |setCurrent()| is called, a |ContextNotActiveException| is thrown.</text>
</assertion>
<assertion id="c">
- <text>If the given scope type is not a normal scope, an IllegalArgumentException is thrown.</text>
+ <text>If the given scope type is not a normal scope, an |IllegalArgumentException| is thrown.</text>
</assertion>
<assertion id="d">
- <text>All EL evaluations (as defined Section 5.10, "EL name resolution")~, all calls to any injected Manager object or Manager object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected Event object (as defined in Section 7.6, "The Event interface") and all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text>
+ <text>All EL evaluations (as defined Section 5.10, "EL name resolution")~, all calls to any injected |Manager| object or |Manager| object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected |Event| object (as defined in Section 7.6, "The Event interface") and all calls to any injected |Instance| object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text>
</assertion>
<assertion id="e">
- <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"),~ all calls to any injected Manager object ~or Manager object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected Event object (as defined in Section 7.6, "The Event interface") and all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text>
+ <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"),~ all calls to any injected |Manager| object ~or |Manager| object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected |Event| object (as defined in Section 7.6, "The Event interface") and all calls to any injected |Instance| object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text>
</assertion>
<assertion id="f">
- <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"),~ all calls to any ~injected Manager object or~ Manager object obtained via JNDI lookup~ (as defined by Section 5.7, "The Manager object"), all calls to any injected Event object (as defined in Section 7.6, "The Event interface") and all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text>
+ <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"),~ all calls to any ~injected |Manager| object or~ |Manager| object obtained via JNDI lookup~ (as defined by Section 5.7, "The Manager object"), all calls to any injected |Event| object (as defined in Section 7.6, "The Event interface") and all calls to any injected |Instance| object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text>
</assertion>
<assertion id="g">
- <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"), all calls to any injected Manager object or Manager object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"),~ all calls to any injected Event object (as defined in Section 7.6, "The Event interface") ~and all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text>
+ <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"), all calls to any injected |Manager| object or |Manager| object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"),~ all calls to any injected |Event| object (as defined in Section 7.6, "The Event interface") ~and all calls to any injected |Instance| object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text>
</assertion>
<assertion id="h">
- <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"), all calls to any injected Manager object or Manager object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected Event object (as defined in Section 7.6, "The Event interface") and ~all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup") are processed by the current activity</text>
+ <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"), all calls to any injected |Manager| object or |Manager| object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected |Event| object (as defined in Section 7.6, "The Event interface") and ~all calls to any injected |Instance| object (as defined by Section 5.8, "Dynamic lookup") are processed by the current activity</text>
</assertion>
<assertion id="j">
More information about the weld-commits
mailing list