[webbeans-commits] Webbeans SVN: r3128 - in tck/trunk/impl/src/main: java/org/jboss/jsr299/tck/tests/decorators/definition/broken and 3 other directories.

[webbeans-commits at lists.jboss.org]

Author: pete.muir at jboss.org
Date: 2009-07-22 08:49:54 -0400 (Wed, 22 Jul 2009)
New Revision: 3128

Removed:
   tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/context/passivating/broken1/
   tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/context/passivating/broken3/
   tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/context/passivating/broken4/
   tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/context/passivating/broken5/
   tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/decorators/definition/broken/tooManyDecoratorsElements/
Modified:
   tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/decorators/definition/broken/enabledDecoratorIsNotDecorator/EnabledDecoratorNotADecoratorTest.java
   tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/deployment/lifecycle/broken/addDefinitionError/AddDefinitionErrorTest.java
   tck/trunk/impl/src/main/resources/tck-audit.xml
Log:
Remove stub tests

Modified: tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/decorators/definition/broken/enabledDecoratorIsNotDecorator/EnabledDecoratorNotADecoratorTest.java
===================================================================
--- tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/decorators/definition/broken/enabledDecoratorIsNotDecorator/EnabledDecoratorNotADecoratorTest.java	2009-07-22 12:47:59 UTC (rev 3127)
+++ tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/decorators/definition/broken/enabledDecoratorIsNotDecorator/EnabledDecoratorNotADecoratorTest.java	2009-07-22 12:49:54 UTC (rev 3128)
@@ -36,7 +36,7 @@
 {
 
    @Test
-   @SpecAssertion(section="8.2", id="review") // This assertion doesn't seem to be in the latest version of the spec
+   @SpecAssertion(section="8.2", id="bb")
    public void testEnabledDecoratorNotADecoratorTest()
    {
 

Modified: tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/deployment/lifecycle/broken/addDefinitionError/AddDefinitionErrorTest.java
===================================================================
--- tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/deployment/lifecycle/broken/addDefinitionError/AddDefinitionErrorTest.java	2009-07-22 12:47:59 UTC (rev 3127)
+++ tck/trunk/impl/src/main/java/org/jboss/jsr299/tck/tests/deployment/lifecycle/broken/addDefinitionError/AddDefinitionErrorTest.java	2009-07-22 12:49:54 UTC (rev 3128)
@@ -5,7 +5,6 @@
 import org.jboss.jsr299.tck.DefinitionError;
 import org.jboss.testharness.impl.packaging.Artifact;
 import org.jboss.testharness.impl.packaging.ExpectedDeploymentException;
-import org.jboss.testharness.impl.packaging.IntegrationTest;
 import org.jboss.testharness.impl.packaging.Resource;
 import org.jboss.testharness.impl.packaging.Resources;
 import org.testng.annotations.Test;

Modified: tck/trunk/impl/src/main/resources/tck-audit.xml
===================================================================
--- tck/trunk/impl/src/main/resources/tck-audit.xml	2009-07-22 12:47:59 UTC (rev 3127)
+++ tck/trunk/impl/src/main/resources/tck-audit.xml	2009-07-22 12:49:54 UTC (rev 3128)
@@ -2568,8 +2568,28 @@
     </assertion>
     
     <assertion id="aac">
-      <text>If a managed bean which declares a passivating scope 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>
+      <text>If a managed bean which declares a passivating scope 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="aad">
+      <text>If a managed bean which declares a passivating scope 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="aae">
+      <text>If a managed bean which declares a passivating scope 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="aaf">
+      <text>If a managed bean which declares a passivating scope 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="aag">
+      <text>If a managed bean which declares a passivating scope 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="aah">
+      <text>If a managed bean which declares a passivating scope 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="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>
@@ -3192,8 +3212,12 @@
       <text>The order of the decorator declarations determines the decorator ordering. Decorators which occur earlier in the list are called first.</text>
     </assertion>
     
+    <assertion id="ba">
+      <text>Each child |&lt;class&gt;| element must specify the name of a decorator bean class.  If there is no class with the specified name~, or if the class with the specified name is not a decorator bean class,~ 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>Each child |&lt;class&gt;| element must specify the name of a decorator bean class.  If there is no class with the specified name, or if the class with the specified name is not a decorator bean class, 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>
+      <text>Each child |&lt;class&gt;| element must specify the name of a decorator bean class.  If ~there is no class with the specified name, or if~ the class with the specified name is not a decorator bean class~,~ 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">