[webbeans-commits] Webbeans SVN: r2267 - tck/trunk/impl/src/main/resources.
webbeans-commits at lists.jboss.org
webbeans-commits at lists.jboss.org
Mon Mar 30 03:19:11 EDT 2009
Author: shane.bryzak at jboss.com
Date: 2009-03-30 03:19:11 -0400 (Mon, 30 Mar 2009)
New Revision: 2267
Modified:
tck/trunk/impl/src/main/resources/tck-audit.xml
Log:
editing, minor
Modified: tck/trunk/impl/src/main/resources/tck-audit.xml
===================================================================
--- tck/trunk/impl/src/main/resources/tck-audit.xml 2009-03-30 07:11:48 UTC (rev 2266)
+++ tck/trunk/impl/src/main/resources/tck-audit.xml 2009-03-30 07:19:11 UTC (rev 2267)
@@ -6101,7 +6101,7 @@
<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>
- <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>
+ <note>Test that beans and observers are registered and definition exceptions occur before @Initialized, and that this causes the app deployment to fail</note>
</assertion>
<assertion id="b">
@@ -6239,15 +6239,15 @@
</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">
@@ -6283,43 +6283,43 @@
</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>
+ <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>
<assertion id="c">
- <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>
+ <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>
<assertion id="d">
- <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>
+ <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>
<assertion id="e">
- <text>every interceptor ~and decorator~ belonging to a parent activity also belongs to the child activity ~and may be applied to any bean belonging to the child activity~</text>
+ <text>Every interceptor ~and decorator~ belonging to a parent activity also belongs to the child activity ~and may be applied to any bean belonging to the child activity~</text>
</assertion>
<assertion id="f">
- <text>every interceptor ~and decorator~ belonging to a parent activity ~also belongs to the child activity and~ may be applied to any bean belonging to the child activity</text>
+ <text>Every interceptor ~and decorator~ belonging to a parent activity ~also belongs to the child activity and~ may be applied to any bean belonging to the child activity</text>
</assertion>
<assertion id="g">
- <text>every ~interceptor and~ decorator belonging to a parent activity also belongs to the child activity and~ may be applied to any bean belonging to the child activity~</text>
+ <text>Every ~interceptor and~ decorator belonging to a parent activity also belongs to the child activity and~ may be applied to any bean belonging to the child activity~</text>
</assertion>
<assertion id="h">
- <text>every ~interceptor and~ decorator belonging to a parent activity ~also belongs to the child activity and~ may be applied to any bean belonging to the child activity</text>
+ <text>Every ~interceptor and~ decorator belonging to a parent activity ~also belongs to the child activity and~ may be applied to any bean belonging to the child activity</text>
</assertion>
<assertion id="j">
- <text>every observer belonging to a parent activity also belongs to the child activity ~and receives events fired via the child activity~</text>
+ <text>Every observer belonging to a parent activity also belongs to the child activity ~and receives events fired via the child activity~</text>
</assertion>
<assertion id="k">
- <text>every observer belonging to a parent activity ~also belongs to the child activity and~ receives events fired via the child activity</text>
+ <text>Every observer belonging to a parent activity ~also belongs to the child activity and~ receives events fired via the child activity</text>
</assertion>
<assertion id="l">
- <text>every context object belonging to the parent activity also belongs to the child activity</text>
+ <text>Every context object belonging to the parent activity also belongs to the child activity</text>
</assertion>
<assertion id="m">
More information about the weld-commits
mailing list