[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-8563) Alternative being not being recognized as so.
[
https://issues.jboss.org/browse/JBIDE-8563?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-8563:
----------------------------------
Fix Version/s: 3.3.0.M1
Priority: Major (was: Minor)
Assignee: Viacheslav Kabanovich (was: Alexey Kazakov)
People keep complaining that sometimes beans.xml validation requires a few cleanups to
make it pick up annotated types.
I guess it's because we have two models in CDI Tools. One is our pure CDI Model which
is built by CDI builder. This model is quite stable because it lives in Eclipse builder
ecosystem. But in parallel we have our old X-model which is used for XMLs (including
beans.xml). And probably sometimes XModel loads beans.xml earlier than JDT/CDI builders
finish building CDI model.
So, I'm afraid we should get rid of XModel in CDI tools at all to get rid of this
bug.
Slava, what do you think?
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