[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8563) Alternative being not being recognized as so.
[
https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-8563:
--------------------------------------------
I just want to confirm I've bumped into similar problems - if things happens as you
say Slava my question isn't there a way things can be revalidated (efficiently) or at
least invalidate marks that are wrong now that CDI model is in place?
Alternative being not being recognized as so.
---------------------------------------------
Key: JBIDE-8563
URL: https://issues.jboss.org/browse/JBIDE-8563
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Final
Reporter: José Freitas
Assignee: Viacheslav Kabanovich
Labels: alternative, cdi
Fix For: 3.3.0.M1
the problem occurs on
booking example:
https://github.com/seam/examples/
declaring on WEB-INF/beans.xml
{code}
<alternatives>
<class>org.jboss.seam.examples.booking.bootstrap.ApplicationInitializer</class>
</alternatives>
{code}
gives me the error check:
{code}
<class> element must specify the name of an alternative bean class [JSR-299
§5.1.1]
{code}
but the class is declared as an Alternative
{code}
@Alternative
public class ApplicationInitializer{
...
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira