[jbosstools-issues] [JBoss JIRA] (JBIDE-15620) Wrong CDI warnings

[Viacheslav Kabanovich (JIRA)]

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

Viacheslav Kabanovich commented on JBIDE-15620:
-----------------------------------------------

This is new in CDI 1.1. The section '3.8 Additional built-in beans' in CDI 1.1 spec differs from '3.6. Additional built-in beans' in CDI 1.1 spec in the following
1. javax.security.Principal instead of java.security.Principal (can it be a typo?)
2. Added built-in beans to be provided by servlet container:
javax.servlet.http.HttpServletRequest
javax.servlet.http.HttpSession
javax.servlet.ServletContext
3. Omitted built-in beans (replaced by 1.2.7 Relationship to Bean Validation)
javax.validation.ValidationFactory
javax.validation.Validator
I suggest changing this issue from Bug to Task linked to JBIDE-13228.
                
> Wrong CDI warnings
> ------------------
>
>                 Key: JBIDE-15620
>                 URL: https://issues.jboss.org/browse/JBIDE-15620
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi
>    Affects Versions: 4.1.1.Alpha1
>            Reporter: Juergen Zimmermann
>            Assignee: Viacheslav Kabanovich
>             Fix For: 4.2.x
>
>         Attachments: wrong-cdi-warnings.png
>
>
> I moved to WildFly (and therefore to Weld 2.0.CR1 resp CDI 1.1). I'm getting warnings about wrong dependency injection of these classes:
> * HttpSession
> * HttpServletRequest
> But the CDI 1.1 spec allows them to be injected (and my web app works fine).
> I'll attach a stacktrace to illustrate the wrong warnings

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira