-
Tracker
-
Resolution: Obsolete
-
Major
-
1.0
-
None
Is it expected that the container validates these dependencies and fails deployment if they don't exist? I think it is, right? At least, I think some containers behave this way. Then we should say that this validation should not happen if the annotation appears in a class annotated @Alternative. I have no idea what the right language would be...
- relates to
-
CDI-53 Datasources and other resources defined on alternatives
-
- Closed
-
The CDI project is part ofJakarta and uses GitHub issues as it's issue tracking system.
Therefore, all issues in CDI JIRA project are being bulk-closed as described in this GitHub issue.
If you feel like this particular issue deserves ongoing discussion, investigation or fixes in CDI/CDI TCK, please create a new issue under GitHub repository and include a link to this JIRA.
For specification related question/issues, please use - https://github.com/eclipse-ee4j/cdi/issues
For CDI TCK related questions/issues, please use - https://github.com/eclipse-ee4j/cdi-tck/issues