[
https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin...
]
José Freitas commented on JBIDE-8563:
-------------------------------------
You did the same thing I usually do, yet I had this problem in two enviroments, one at my
home, and one at my work.
As you suggested trying, cleaning the project made the error disappear, but at home I had
to clean it two times, and I had the impression that on second time it worked after
clearing the error log view(I wanted to see if it was throwing something new).
Another detail I noticed: when the error is there, the Ctrl+space don´t bring the class
too.
I tried again two more times from the beggining (delete everything and cloned the repo
again) and the error don´t appear anymore. Sorry for not being able to collect any more
data, maybe my eclipses just had an insanity moment.
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: Alexey Kazakov
Priority: Minor
Labels: alternative, cdi
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