[webbeans-commits] Webbeans SVN: r3374 - tck/trunk/impl/src/main/resources.

Author: shane.bryzak(a)jboss.com Date: 2009-07-30 20:27:07 -0400 (Thu, 30 Jul 2009) New Revision: 3374 Modified: tck/trunk/impl/src/main/resources/tck-audit.xml Log: fix all groupings for 6.6.4 Modified: tck/trunk/impl/src/main/resources/tck-audit.xml =================================================================== --- tck/trunk/impl/src/main/resources/tck-audit.xml 2009-07-30 17:11:12 UTC (rev 3373) +++ tck/trunk/impl/src/main/resources/tck-audit.xml 2009-07-31 00:27:07 UTC (rev 3374) @@ -2710,7 +2710,7 @@ </group> <group> - <text>A producer method is passivation capable if and only if it never returns a value which is not passivation capable at runtime. A producer method with a return type that implements or extends serializable is passivation capable. A producer method with a return type that is declared final and does not implement |Serializable| is not passivation capable.</text> + <text>A producer method is passivation capable if and only if it never returns a value which is not passivation capable at runtime. A producer method with a return type that implements or extends serializable is passivation capable. A producer method with a return type that is declared |final| and does not implement |Serializable| is not passivation capable.</text> <assertion id="ca"> <text>Test that a producer method with a serializable return type is passivation capable.</text> @@ -2836,87 +2836,123 @@ <text>Test decorator with initializer method parameter.</text> </assertion> </group> + + <group> + <text>If a stateful session bean has a non-transient injected field, bean constructor parameter or initializer method parameter that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> + + <assertion id="ba"> + <text>Test with an injected field.</text> + </assertion> - <assertion id="ba"> - <text>If a stateful session bean has a non-transient injected field~, bean constructor parameter or initializer method parameter~ that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> + <assertion id="bb"> + <text>Test with a bean constructor parameter.</text> + </assertion> - <assertion id="bb"> - <text>If a stateful session bean has a non-transient ~injected field,~ bean constructor parameter ~or initializer method parameter~ that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> + <assertion id="bc"> + <text>Test with an initializer method parameter.</text> + </assertion> + </group> + + <group> + <text>If a stateful session bean has an interceptor or decorator with a non-transient injected field, bean constructor parameter or initializer method parameter that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> + + <assertion id="bda"> + <text>Test an interceptor with an injected field.</text> + </assertion> + + <assertion id="bdb"> + <text>Test an interceptor with a bean constructor parameter.</text> + </assertion> + + <assertion id="bdc"> + <text>Test an interceptor with an initializer method parameter.</text> + </assertion> + + <assertion id="bdd"> + <text>Test a decorator with an injected field.</text> + </assertion> + + <assertion id="bde"> + <text>Test a decorator with a bean constructor parameter.</text> + </assertion> + + <assertion id="bdf"> + <text>Test a decorator with an initializer method parameter.</text> + </assertion> + </group> + + <group> + <text>If a producer method declares a passivating scope and the container is able to determine that it is not passivation capable by inspecting its return type, or has a parameter that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> + + <assertion id="ca"> + <text>Test a producer method with a non passivation-capable return type.</text> + </assertion> - <assertion id="bc"> - <text>If a stateful session bean has a non-transient~ injected field, bean constructor parameter or~ initializer method parameter that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - - <assertion id="bda"> - <text>If a stateful session bean has an interceptor ~or decorator~ with a non-transient injected field~, bean constructor parameter or initializer method parameter~ that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - - <assertion id="bdb"> - <text>If a stateful session bean has an interceptor ~or decorator~ with a non-transient ~injected field,~ bean constructor parameter ~or initializer method parameter~ that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - - <assertion id="bdc"> - <text>If a stateful session bean has an interceptor ~or decorator~ with a non-transient ~injected field, bean constructor parameter or~ initializer method parameter that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - - <assertion id="bdd"> - <text>If a stateful session bean has an ~interceptor or~ decorator with a non-transient injected field~, bean constructor parameter or initializer method parameter~ that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - - <assertion id="bde"> - <text>If a stateful session bean has an ~interceptor or~ decorator with a non-transient ~injected field,~ bean constructor parameter ~or initializer method parameter~ that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - - <assertion id="bdf"> - <text>If a stateful session bean has an ~interceptor or~ decorator with a non-transient ~injected field, bean constructor parameter or~ initializer method parameter that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> + <assertion id="cb"> + <text>Test a producer method with a parameter that does not resolve to a passivation capable dependency.</text> + </assertion> + </group> - <assertion id="ca"> - <text>If a producer method declares a passivating scope and the container is able to determine that it is not passivation capable by inspecting its return type~, or has a parameter that does not resolve to a passivation capable dependency,~ then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - - <assertion id="cb"> - <text>If a producer method declares a passivating scope and the container is able to determine that it~ is not passivation capable by inspecting its return type, or~ has a parameter that does not resolve to a passivation capable dependency, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - <assertion id="d"> <text>If a producer field declares a passivating scope and the container is able to determine that it is not passivation capable by inspecting its type, then the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> </assertion> - - <assertion id="ea"> - <text>If a producer method ~or field~ which declares a passivating scope returns an unserializable object at runtime, the container must throw an |IllegalProductException|.</text> - </assertion> + + <group> + <text>If a producer method or field which declares a passivating scope returns an unserializable object at runtime, the container must throw an |IllegalProductException|.</text> + + <assertion id="ea"> + <text>Test with a producer method.</text> + </assertion> + + <assertion id="eb"> + <text>Test with a producer field.</text> + </assertion> + </group> + + <group> + <text>If a producer method or field of scope |@Dependent| returns an unserializable object for injection into an injection point that requires a passivation capable dependency, the container must throw an |IllegalProductException|</text> + + <assertion id="fa"> + <text>Test for a deployment exception with a producer method.</text> + </assertion> + + <assertion id="fab"> + <text>Test for a runtime exception with a producer method.</text> + </assertion> + + <assertion id="fb"> + <text>Test for a deployment exception with a producer field.</text> + </assertion> + + <assertion id="fbb"> + <text>Test for a runtime exception with a producer field.</text> + </assertion> + </group> + + <group> + <text>For a custom implementation of |Bean|, the container calls |getInjectionPoints()| to determine the injection points, and |InjectionPoint.isTransient()| to determine whether the injected point is a transient field.</text> - <assertion id="eb"> - <text>If a producer ~method or~ field which declares a passivating scope returns an unserializable object at runtime, the container must throw an |IllegalProductException|.</text> - </assertion> - - <assertion id="fa"> - <text>If a producer method ~or field~ of scope |@Dependent| returns an unserializable object for injection into an injection point that requires a passivation capable dependency, the container must throw an |IllegalProductException|</text> - </assertion> - - <assertion id="fb"> - <text>If a producer ~method or~ field of scope |@Dependent| returns an unserializable object for injection into an injection point that requires a passivation capable dependency, the container must throw an |IllegalProductException|</text> - </assertion> - - <assertion id="ga"> - <text>For a custom implementation of |Bean|, the container calls |getInjectionPoints()| to determine the injection points~, and |InjectionPoint.isTransient()| to determine whether the injected point is a transient field~.</text> - </assertion> - - <assertion id="gb"> - <text>For a custom implementation of |Bean|, the container calls ~ |getInjectionPoints()| to determine the injection points, and~ |InjectionPoint.isTransient()| to determine whether the injected point is a transient field.</text> - </assertion> - - <assertion id="ha"> - <text>If a bean which declares a passivating scope type~, or any stateful session bean,~ has a decorator which is not a passivation capable dependency, the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> - - <assertion id="hb"> - <text>If ~a bean which declares a passivating scope type, or~ any stateful session bean, has a decorator which is not a passivation capable dependency, the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> - </assertion> + <assertion id="ga"> + <text>Test calling |getInjectionPoints()|.</text> + </assertion> + + <assertion id="gb"> + <text>Test calling |InjectionPoint.isTransient()|.</text> + </assertion> + </group> + + <group> + <text>If a bean which declares a passivating scope type, or any stateful session bean, has a decorator which is not a passivation capable dependency, the container automatically detects the problem and treats it as a deployment problem, as defined in Section 12.4, "Problems detected automatically by the container".</text> + + <assertion id="ha"> + <text>Test with a bean which declares a passivating scope type.</text> + </assertion> + + <assertion id="hb"> + <text>Test with a stateful session bean.</text> + </assertion> + </group> </section> <section id="6.7" title="Context management for built-in scopes">