Author: dan.j.allen Date: 2009-07-21 00:22:07 -0400 (Tue, 21 Jul 2009) New Revision: 3099 Modified: tck/trunk/impl/src/main/resources/tck-audit.xml Log: split 6.6.4.c into two assertions Modified: tck/trunk/impl/src/main/resources/tck-audit.xml =================================================================== --- tck/trunk/impl/src/main/resources/tck-audit.xml 2009-07-21 00:56:12 UTC (rev 3098) +++ tck/trunk/impl/src/main/resources/tck-audit.xml 2009-07-21 04:22:07 UTC (rev 3099) @@ -2583,10 +2583,14 @@ <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="c"> - <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>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>