[webbeans-commits] Webbeans SVN: r3719 - tck/trunk/impl/src/main/resources.
webbeans-commits at lists.jboss.org
webbeans-commits at lists.jboss.org
Tue Sep 22 07:00:43 EDT 2009
Author: shane.bryzak at jboss.com
Date: 2009-09-22 07:00:43 -0400 (Tue, 22 Sep 2009)
New Revision: 3719
Modified:
tck/trunk/impl/src/main/resources/tck-audit-cdi.xml
Log:
section 7, 8 and 9 assertions
Modified: tck/trunk/impl/src/main/resources/tck-audit-cdi.xml
===================================================================
--- tck/trunk/impl/src/main/resources/tck-audit-cdi.xml 2009-09-22 11:00:26 UTC (rev 3718)
+++ tck/trunk/impl/src/main/resources/tck-audit-cdi.xml 2009-09-22 11:00:43 UTC (rev 3719)
@@ -2386,7 +2386,7 @@
<text>The |javax.enterprise.inject.spi.InjectionPoint.getMember()| method returns the |Constructor| object in the case of constructor parameter injection.</text>
</assertion>
- <assertion id="daa">
+ <assertion id="daa"> <text>When the container invokes a method of a bean, the invocation may or may not be treated as a business method invocation
<text>The |getAnnotated()| method returns an instance of |javax.enterprise.inject.spi.AnnotatedField| or |javax.enterprise.inject.spi.AnnotatedParameter|, depending upon whether the injection point is an injected field or a constructor/method parameter.</text>
</assertion>
@@ -3553,48 +3553,16 @@
</section>
- <section id="7.2" title="Container invocations and interception">
+ <section id="7.2" title="Container invocations and interception">
+ <assertion id="a0" testable="false">
+ <text>When the application invokes a method of a bean via a contextual reference to the bean, as defined in Section 6.5.3, "Contextual reference for a bean", or a business method of a session bean via an EJB remote or local reference, the invocation is treated as a business method invocation.</text>
+ </assertion>
+
+ <assertion id="a1">
+ <text>Invocations of initializer methods by the container are not business method invocations.</text>
+ </assertion>
+
<group>
- <text>When the container invokes a method of a bean, if, and only if, the invocation is a business method invocation it passes through the method interceptor and decorator stacks, and in the case of a session bean, it is subject to EJB services such a declarative transaction management, concurrency, security and asynchronicity, as defined by the EJB specification.</text>
-
- <assertion id="a">
- <text>Verify that a managed bean's business methods are intercepted</text>
- </assertion>
-
- <assertion id="b">
- <text>Verify that a managed bean's business methods are decorated</text>
- </assertion>
-
- <assertion id="c">
- <text>Verify that a session bean's business methods are intercepted</text>
- </assertion>
-
- <assertion id="d">
- <text>Verify that a session bean's business methods are decorated</text>
- </assertion>
-
- <assertion id="f" testable="false">
- <text>Verify that a session bean's business methods receive EJB services</text>
- <note>This is tested by the EJB TCK</note>
- </assertion>
- </group>
-
- <assertion id="g">
- <text>If the invocation is not a business method invocation, it is treated as a normal Java method call and is not intercepted by the container.</text>
- </assertion>
-
- <group>
- <text>Invocations of initializer methods by the container are not business method invocations.</text>
- <assertion id="ha">
- <text>Check initializer methods aren't decorated</text>
- </assertion>
- <assertion id="hb">
- <text>Check initializer methods aren't intercepted</text>
- </assertion>
- </group>
-
-
- <group>
<text>Invocations of producer, disposer and observer methods by the container are business method invocations are are intercepted by method interceptors and decorators.</text>
<assertion id="ia">
@@ -3620,13 +3588,12 @@
<assertion id="if">
<text>Verify observer methods are decorated</text>
</assertion>
- </group>
-
-
+ </group>
+
<assertion id="j">
<text>Invocation of lifecycle callbacks by the container are not business method invocations, but are intercepted by interceptors for lifecycle callbacks.</text>
- </assertion>
-
+ </assertion>
+
<group>
<text>Invocations of interceptors and decorator methods during method or lifecycle callback interception are not business method invocations, and therefore no recursive interception occurs.</text>
<assertion id="ka">
@@ -3644,7 +3611,40 @@
<assertion id="kd">
<text>Verify interceptor callbacks are not decorated</text>
</assertion>
+ </group>
+
+ <assertion id="a5">
+ <text>Invocations of message listener methods of message-driven beans during message delivery are business method invocations.</text>
+ </assertion>
+
+ <group>
+ <text>If, and only if, the invocation is a business method invocation it passes through the method interceptor and decorator stacks, and in the case of a session bean, it is subject to EJB services such a declarative transaction management, concurrency, security and asynchronicity, as defined by the EJB specification.</text>
+
+ <assertion id="a">
+ <text>Verify that a managed bean's business methods are intercepted</text>
+ </assertion>
+
+ <assertion id="b">
+ <text>Verify that a managed bean's business methods are decorated</text>
+ </assertion>
+
+ <assertion id="c">
+ <text>Verify that a session bean's business methods are intercepted</text>
+ </assertion>
+
+ <assertion id="d">
+ <text>Verify that a session bean's business methods are decorated</text>
+ </assertion>
+
+ <assertion id="f" testable="false">
+ <text>Verify that a session bean's business methods receive EJB services</text>
+ <note>This is tested by the EJB TCK</note>
+ </assertion>
</group>
+
+ <assertion id="g">
+ <text>If the invocation is not a business method invocation, it is treated as a normal Java method call and is not intercepted by the container.</text>
+ </assertion>
</section>
<section id="7.3" title="Lifecycle of contextual instances">
@@ -3795,7 +3795,7 @@
</group>
<group>
- <text>When the |destroy()| method is called, the container discards this internal reference. For certain kinds of resource, for example persistence contexts, the container eventually performs additional cleanup to destroy state associated with the client or transaction, as required by the Java EE platform specification.</text>
+ <text>When the |destroy()| method is called, the container discards this internal reference and performs any cleanup required of state associated with the client or transaction.</text>
<assertion id="na" testable="false">
<text>Check Java EE component environment resource</text>
@@ -3838,7 +3838,7 @@
<section id="8" title="Decorators">
<assertion id="a" testable="false">
- <text>Decorators may be bound to any managed bean that is not itself an interceptor or decorator or to any EJB session or message-driven bean.</text>
+ <text>Decorators may be associated with any managed bean that is not itself an interceptor or decorator or with any EJB session bean.</text>
<note>Doesn't specify an error</note>
</assertion>
</section>
@@ -3878,7 +3878,7 @@
<section id="8.1.2" title="Decorator delegate injection points">
<assertion id="a">
- <text>All decorators have a delegate injection point. A delegate injection point is an injection point of the bean class. The type and bindings of the injection point are called the delegate type and delegate bindings. The delegate injection point must be be declared by annotating the injection point with the annotation |@javax.decorator.Decorates|.</text>
+ <text>All decorators have a delegate injection point. A delegate injection point is an injection point of the bean class. The type and qualifiers of the injection point are called the delegate type and delegate qualifiers. The delegate injection point must be be declared by annotating the injection point with the annotation |@javax.decorator.Decorates|.</text>
</assertion>
<assertion id="b">
@@ -3986,7 +3986,7 @@
</assertion>
<assertion id="b">
- <text>For a custom implementation of the Decorator interface defined in Section 11.1.1, "The Decorator interface", the container calls |getDelegateType()|, |getDelegateBindings()| and |getDecoratedTypes()| to determine the delegate type and bindings and decorated types of the decorator.</text>
+ <text>For a custom implementation of the Decorator interface defined in Section 11.1.1, "The Decorator interface", the container calls |getDelegateType()|, |getDelegateQualifiers()| and |getDecoratedTypes()| to determine the delegate type and qualifiers and decorated types of the decorator.</text>
</assertion>
</section>
@@ -4034,7 +4034,7 @@
</assertion>
<assertion id="b">
- <text>An interceptor binding type may be declared by specifying the |@javax.interceptor.InterceptorBindingType| metaannotation.</text>
+ <text>An interceptor binding type may be declared by specifying the |@javax.interceptor.InterceptorBinding| meta-annotation.</text>
</assertion>
<assertion id="c">
@@ -4174,11 +4174,11 @@
</assertion>
<assertion id="b">
- <text>An annotation member may be excluded from consideration using the @NonBinding annotation.</text>
+ <text>An annotation member may be excluded from consideration using the @Nonbinding annotation.</text>
</assertion>
- <assertion id="c">
- <text>Array-valued or annotation-valued members of an interceptor binding type must be annotated |@NonBinding|. If an array-valued or annotation-valued member of an interceptor binding type is not annotated |@NonBinding|, the container automatically detects the problem and treats it as a definition error, as defined in Section 12.4, "Problems detected automatically by the container".</text>
+ <assertion id="ca">
+ <text>Array-valued or annotation-valued members of an interceptor binding type should be annotated |@Nonbinding| in a portable application. If an array-valued or annotation-valued member of an interceptor binding type is not annotated |@Nonbinding|, non-portable behavior results.</text>
</assertion>
<assertion id="d">
More information about the weld-commits
mailing list