]
Alexey Kazakov resolved JBIDE-6523.
-----------------------------------
Resolution: Done
beans.xml validation.
---------------------
Key: JBIDE-6523
URL:
https://jira.jboss.org/browse/JBIDE-6523
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdi (jsr-299)
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.2.0.Beta
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
name, or if the class with the specified name is not an alternative bean class, the
container automatically detects the problem
and treats it as a deployment problem.
- Each child <stereotype> element must specify the name of an @Alternative
stereotype annotation. If there is no annotation
with the specified name, or the annotation is not an @Alternative stereotype, the
container automatically detects the
problem and treats it as a deployment problem.
- If the same type is listed twice under the <alternatives> element, the container
automatically detects the problem and
treats it as a deployment problem.
8.2. Decorator enablement and ordering
- Each child <class> 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.
- If the same class is listed twice under the <decorators> element, the container
automatically detects the problem and
treats it as a deployment problem.
9.4. Interceptor enablement and ordering
- Each child <class> element must specify the name of an interceptor class. If
there is no class with the specified name, or if
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: