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

Author: pete.muir(a)jboss.org Date: 2009-03-29 10:01:23 -0400 (Sun, 29 Mar 2009) New Revision: 2252 Modified: tck/trunk/impl/src/main/resources/tck-audit.xml Log: add 11.6 assertions Modified: tck/trunk/impl/src/main/resources/tck-audit.xml =================================================================== --- tck/trunk/impl/src/main/resources/tck-audit.xml 2009-03-28 18:27:43 UTC (rev 2251) +++ tck/trunk/impl/src/main/resources/tck-audit.xml 2009-03-29 14:01:23 UTC (rev 2252) @@ -6092,5 +6092,150 @@ <text>If the same decorator is declared more than once, a |DefinitionException| is thrown by the container at deployment time.</text> </assertion> </section> + + <section id="11" title="Packaging and Deployment"> + </section> + + <section id="11.6" title="Activities"> + + <assertion id="a"> + <text>The method createActivity() creates a new child activity of an activity:</text> + </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> + </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> + </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> + </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> + </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> + </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> + </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> + </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> + </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> + </assertion> + + <assertion id="l"> + <text>every context object belonging to the parent activity also belongs to the child activity</text> + </assertion> + + <assertion id="m"> + <text>Beans ~and observers~ may be registered with an activity by calling addBean() ~or addObserver()~ on the Manager object that represents the activity.</text> + </assertion> + + <assertion id="n"> + <text>~Beans and~ observers may be registered with an activity by calling ~addBean() or~ addObserver() on the Manager object that represents the activity.</text> + </assertion> + <assertion id="o"> + <text>a bean registered with the child activity is not available for injection into any bean registered with a parent activity</text> + </assertion> + + <assertion id="p"> + <text>a bean registered with a child activity is not available for injection into a ~servlet or~ EJB</text> + </assertion> + + <assertion id="q"> + <text>a bean registered with a child activity is not available for injection into a servlet ~or EJB~</text> + </assertion> + + <assertion id="r"> + <text>a bean registered with a child activity may not be obtained by dynamic lookup via the parent activity</text> + </assertion> + + <assertion id="s"> + <text>an observer registered with the child activity does not receive events fired via a parent activity</text> + </assertion> + + <assertion id="t"> + <text>If a bean registered with a child activity has the bean type and all bindings of some injection point of some bean registered with a direct ~or indirect~ parent activity, a DeploymentException is throw by the container at deployment time.</text> + </assertion> + + <assertion id="u"> + <text>If a bean registered with a child activity has the bean type and all bindings of some injection point of some bean registered with a~ direct or~ indirect parent activity, a DeploymentException is throw by the container at deployment time.</text> + </assertion> + + <assertion id="v"> + <text>The addInterceptor() ~and addDecorator()~ methods throw UnsupportedOperationException when called on a Manager object that represents a child activity.</text> + </assertion> + + <assertion id="w"> + <text>The ~addInterceptor() and~ addDecorator() methods throw UnsupportedOperationException when called on a Manager object that represents a child activity.</text> + </assertion> + + </section> + + <section id="11.6.1" title="Current Activity"> + <assertion id="a"> + <text>An activity may be associated with the current context for a normal scope by calling setCurrent(), passing the normal scope type</text> + </assertion> + + <assertion id="b"> + <text>If the given scope is inactive when setCurrent() is called, a ContextNotActiveException is thrown.</text> + </assertion> + + <assertion id="c"> + <text>If the given scope type is not a normal scope, an IllegalArgumentException is thrown.</text> + </assertion> + + <assertion id="d"> + <text>All EL evaluations (as defined Section 5.10, "EL name resolution")~, all calls to any injected Manager object or Manager object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected Event object (as defined in Section 7.6, "The Event interface") and all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text> + </assertion> + + <assertion id="e"> + <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"),~ all calls to any injected Manager object ~or Manager object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected Event object (as defined in Section 7.6, "The Event interface") and all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text> + </assertion> + + <assertion id="f"> + <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"),~ all calls to any ~injected Manager object or~ Manager object obtained via JNDI lookup~ (as defined by Section 5.7, "The Manager object"), all calls to any injected Event object (as defined in Section 7.6, "The Event interface") and all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text> + </assertion> + + <assertion id="g"> + <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"), all calls to any injected Manager object or Manager object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"),~ all calls to any injected Event object (as defined in Section 7.6, "The Event interface") ~and all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup")~ are processed by the current activity</text> + </assertion> + + <assertion id="h"> + <text>~All EL evaluations (as defined Section 5.10, "EL name resolution"), all calls to any injected Manager object or Manager object obtained via JNDI lookup (as defined by Section 5.7, "The Manager object"), all calls to any injected Event object (as defined in Section 7.6, "The Event interface") and ~all calls to any injected Instance object (as defined by Section 5.8, "Dynamic lookup") are processed by the current activity</text> + </assertion> + + <assertion id="j"> + <text>If the root activity has no active normal scope such that the current context for that scope has an associated activity, the root activity is the current activity.</text> + </assertion> + + <assertion id="k"> + <text>If the root activity has exactly one active normal scope such that the current context for that scope has an associated activity, that activity is the current activity.</text> + </assertion> + + <assertion id="l" testable="false"> + <text>Otherwise, there is no well-defined current activity, and the behavior is undefined. Portable frameworks and applications should not depend upon the behavior of the container when two different current contexts have an associated activity.</text> + </assertion> + + <assertion id="m"> + <text>A bean registered with an activity is only available to Unified EL expressions that are evaluated when that activity or one of its children is the current activity.</text> + </assertion> + </section> + </specification>