[
https://jira.jboss.org/browse/JBIDE-6671?page=com.atlassian.jira.plugin.s...
]
Alexey Kazakov resolved JBIDE-6671.
-----------------------------------
Fix Version/s: 3.2.0.M2
Resolution: Duplicate Issue
This feature has been implemented in JBIDE-6574.
Pete, if it's still doesn't work then please reopen it as a bug with step to
reproduce the issue.
Add validation for 3.1.4 da - dd
--------------------------------
Key: JBIDE-6671
URL:
https://jira.jboss.org/browse/JBIDE-6671
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdi (jsr-299)
Reporter: Pete Muir
Assignee: Alexey Kazakov
Fix For: 3.2.0.M2
If the bean class of X does not directly extend the bean class of another managed bean,
the container automatically detects the problem and treats it as a definition error.
Possible ways this can happen:
* a specializing bean extending a non simple bean.
* a specializing bean extending nothing.
* a specializing bean directly extending an enterprise bean class.
* a specializing bean implementing an interface and extending nothing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira