[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-6575) CDI deployment problems validation.

[Alexey Kazakov (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564042#comment-12564042 ] 

Alexey Kazakov edited comment on JBIDE-6575 at 12/1/10 6:33 AM:
----------------------------------------------------------------

Here is a list of unimplemented rules:

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:
a)  Classes which don't have a non-private constructor with no parameters cannot be proxied by the container.
b)  Classes which are declared final or have final methods cannot be proxied by the container.
c)  Primitive types cannot be proxied by the container.
d)  Array types cannot be proxied by the container.

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.
-  If a decorator matches a managed bean with a non-static, non-private, final method, and the decorator also implements that method, the container automatically detects the problem and treats it as a deployment problem.

      was (Author: akazakov):
    Here is a list of unimplemented rules:

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.
-  If a decorator matches a managed bean with a non-static, non-private, final method, and the decorator also implements that method, the container automatically detects the problem and treats it as a deployment problem.
  
> CDI deployment problems validation.
> -----------------------------------
>
>                 Key: JBIDE-6575
>                 URL: https://jira.jboss.org/browse/JBIDE-6575
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: cdi (jsr-299)
>            Reporter: Alexey Kazakov
>            Assignee: Alexey Kazakov
>              Labels: new_and_noteworthy
>             Fix For: 3.2.0.CR1, 3.3.x
>
>         Attachments: editor.png
>
>
> Such as:
> 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.
> 5.2.4. Primitive types and null values
> - if an injection point of primitive type resolves to a bean that may have null values, such as a producer method
>   with a non-primitive return type or a producer field with a non-primitive type, the container automatically detects the problem
>   and treats it as a deployment problem.
> ...

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira