[JBoss JIRA] (CDI-318) @WithAnnotations types can appear on any supertype
by Martin Kouba (JIRA)
Martin Kouba created CDI-318:
--------------------------------
Summary: @WithAnnotations types can appear on any supertype
Key: CDI-318
URL: https://issues.jboss.org/browse/CDI-318
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Martin Kouba
Is this intentional? Supertypes also include interfaces which are not very useful here as beans may inherit type-level metadata and members from superclasses only.
Is there any special use-case for this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (CDI-293) Reconsider enum support
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/CDI-293?page=com.atlassian.jira.plugin.sy... ]
Pete Muir resolved CDI-293.
---------------------------
Resolution: Done
Merged
> Reconsider enum support
> -----------------------
>
> Key: CDI-293
> URL: https://issues.jboss.org/browse/CDI-293
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Affects Versions: 1.1.PRD
> Reporter: Jozef Hartinger
> Assignee: Pete Muir
> Fix For: 1.1.PFD
>
>
> The current version of the spec introduces support for scanning of enums and injection into enums.
> I discussed this with Pete and Stuart this week and the conclusion was that it is probably a mistake.
> There is a problem with the injection part if the enum is shared across multiple CDI applications. If we dropped the injection part, the scanning and processing part themselves does not make much sense as the result of scanning would not be processed by CDI anyhow. However, it is convenient for some extensions to have enums scanned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (CDI-292) Drop ProcessModule.getAnnotatedTypes()
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/CDI-292?page=com.atlassian.jira.plugin.sy... ]
Pete Muir resolved CDI-292.
---------------------------
Resolution: Done
Merged
> Drop ProcessModule.getAnnotatedTypes()
> --------------------------------------
>
> Key: CDI-292
> URL: https://issues.jboss.org/browse/CDI-292
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Portable Extensions
> Affects Versions: 1.1.PRD
> Reporter: Jozef Hartinger
> Assignee: Pete Muir
> Fix For: 1.1.PFD
>
>
> With @WithAnnotations in place it is now possible for extensions to indicate with fine granularity which container lifecycle events it is interested in and thus not to harm performance that much if the CDI implementation is efficient.
> Therefore, I don't like the ProcessModule.getAnnotatedTypes() method because:
> 1.) There is no granularity. If extensions start to use it inefficiently it will always harm performance heavily.
> 2.) I am not convinced this method is needed. It was not present in CDI 1.0. The only benefit of the method is that it allows for an extension to get an idea where a given AnnotatedType is comming from. There are other more efficient ways of exposing the same information. If we really need to do this we should probably introduce an abstraction over a bean archive (e.g. a Module object) and add a getModule() method to ProcessAnnotatedType.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months