[jbosstools-issues] [JBoss JIRA] (JBIDE-9800) Open CDI Named Bean dialog works incorrectly with beans declared in seam-config

[Jaroslav Jankovič (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaroslav Jankovič closed JBIDE-9800.
------------------------------------



Verified with jbosstools-3.3_stable_branch.aggregate-Update-2012-05-27_14-14-33-H161. Closing this JIRA.
                
> Open CDI Named Bean dialog works incorrectly with beans declared in seam-config
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-9800
>                 URL: https://issues.jboss.org/browse/JBIDE-9800
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: CDI extensions
>    Affects Versions: 3.3.0.M3
>            Reporter: Alexey Kazakov
>            Assignee: Viacheslav Kabanovich
>             Fix For: 3.3.0.M4
>
>         Attachments: openCDINamedBean.png
>
>
> EXECUTE: Download/clone and install http://seamframework.org/Seam3/SecurityModule as an existing maven project. Make sure CDI support is enabled for the projects.
> EXECUTE: Open /seam-security-example-openid-rp/src/main/resources/META-INF/seam-beans.xml
> EXECUTE: Remove org.jboss.seam.security.external.openid.OpenIdRpInApplicationScopeProducer (line 25) to fix this XML. Save the file.
> EXECUTE: Ctrl+Alt+Z
> EXECUTE: Type "identity" as a bean name
> ASSERT: There are a few beans with name "identity". If you see some beans from JARs it's ok. But there should be also two beans from source code. One of them should point to /seam-security-example-openid-rp/src/main/resources/META-INF/seam-beans.xml and the other one to /seam-security/src/main/java/org/jboss/seam/security/IdentityImpl.java
> FAILURE: But right now there are two beans with similar paths and both open IdentityImpl.java:
> !openCDINamedBean.png!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira