[
https://issues.jboss.org/browse/CDI-280?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-280:
------------------------------------------
[~struberg], as I said before I'm not fan of the "contextual" name and I
prefer "bean" (Bean instance, Bean Reference) since it's the usage in
technical post and books on CDI and other IoC frameworks. My goal here is to have the spec
read by end users as well as implementors. IMO, There's enough complex concepts to
catch in the spec (remember the discussion on Observer Resolution) to add new hermetic
terms were convention brought ones. There are 100% chance that usage keep the simpler one
and that the spec would be a bit harder to be read.
I'm afraid we won't come on an agreement on time to reprocess all these terms in
the Maintenance Release time frame
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, Ready_to_fix
Fix For: 1.2 Proposed
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 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