[jbosstools-commits] JBoss Tools SVN: r26709 - trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/internal/core/validation.

Author: akazakov Date: 2010-11-18 09:32:05 -0500 (Thu, 18 Nov 2010) New Revision: 26709 Modified: trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/internal/core/validation/errorList.txt Log: https://jira.jboss.org/browse/JBIDE-6575 Modified: trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/internal/core/validation/errorList.txt =================================================================== --- trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/internal/core/validation/errorList.txt 2010-11-18 14:25:46 UTC (rev 26708) +++ trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/internal/core/validation/errorList.txt 2010-11-18 14:32:05 UTC (rev 26709) @@ -182,9 +182,9 @@ - bean class is deployed in two different bean archives (Non-Portable behavior) - (JBT: let's ignore this rule so far since we don't have any good tool to recognize such components) - Deployment problems + 5.2.1. Unsatisfied and ambiguous dependencies - If an unsatisfied or unresolvable ambiguous dependency exists, the container automatically detects the problem and treats it as a deployment problem. @@ -195,8 +195,8 @@ and treats it as a deployment problem. + Beans.xml (all of them are deployment problems) -Beans.xml 5.1.1. Declaring selected alternatives for a bean archive - Each child <class> element must specify the name of an alternative bean class. If there is no class with the specified @@ -220,4 +220,27 @@ the class with the specified name is not an interceptor class, the container automatically detects the problem and treats it as a deployment problem. - If the same class is listed twice under the <interceptors> element, the container automatically detects the problem and treats it as - a deployment problem. \ No newline at end of file + a deployment problem. + + + + Unimplemented: + +5.1.3. Inconsistent specialization +- Suppose an enabled bean X specializes a second bean Y. If there is another enabled bean that specializes Y we say that inconsistent + specialization exists. The container automatically detects inconsistent specialization and treats it as a deployment problem. + +5.3.1. Ambiguous EL names +- All unresolvable ambiguous EL names are detected by the container when the application is initialized. Suppose two beans are both available for injection in a certain war, and either: + • the two beans have the same EL name and the name is not resolvable, or + • the EL name of one bean is of the form x.y, where y is a valid bean EL name, and x is the EL name of the other bean, + the container automatically detects the problem and treats it as a deployment problem. + +5.4.1. Unproxyable bean types +- If an injection point whose declared type cannot be proxied by the container resolves to a bean with a normal scope, + the container automatically detects the problem and treats it as a deployment problem. + +8.3. Decorator resolution +- If a decorator matches a managed bean, and the managed bean class is declared final, the container automatically detects + the problem and treats it as a deployment problem. +