[cdi-dev] [JBoss JIRA] (CDI-280) clarify usage of 'bean' term usage in the spec
[
https://issues.jboss.org/browse/CDI-280?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-280:
-----------------------------------
No, just calling it 'the proxy' would not be enough. Actually there are many
different kind of proxies involved besides the 'Contextual Reference'. And
depending on the implementation it could even be more.
1.) interceptor proxies
2.) decorator proxies
3.) subclassing proxies for abstract decorators
4.) EJB API proxies
5.) EJB NIV proxies
6.) JPA proxies
7.) customer specific proxies like custom InjectionTarget
8.) tenant proxies
etc
All those can be either used in parallel or some of them even stacked for the same bean!
clarify usage of 'bean' term usage in the spec
----------------------------------------------
Key: CDI-280
URL: https://issues.jboss.org/browse/CDI-280
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Mark Struberg
Assignee: Antoine Sabot-Durand
Labels: CDI_api_chge, CDI_spec_chge
Fix For: 2.0 (discussion)
We should go to the spec and look up all 'bean' words as they are 5 different
meaning the word 'bean' is used for
* The Bean<T> extends Contextual<T>. Should be referred as 'Bean' or
'CDI Bean'
* The class which gets scanned. Should be referred as 'Bean Class' to
* The instance stored in the context. Should be referred to as 'Contextual
Instance'
* The proxy for a Contextual Instance should be referred to as 'Contextual
Reference'
* The type of an injection point should be referred to as 'InjectionPoint Type'
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)