[cdi-dev] [JBoss JIRA] (CDI-280) clarify usage of 'bean' term usage in the spec

Antoine Sabot-Durand (JIRA) issues at jboss.org
Tue Feb 25 10:17:47 EST 2014


    [ https://issues.jboss.org/browse/CDI-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12947937#comment-12947937 ] 

Antoine Sabot-Durand commented on CDI-280:
------------------------------------------

After having checked the majority of the 1904 Bean occurrences in the spec and to provide a consistent approach  I propose these names

 * The class that gets Scanned : *Bean Class* (_quite obvious_)
 * The Bean<T> : *Bean Metadata* (_because the previous defined *Bean Class* is not {{Bean.class}}_)
 * The instance : *Bean* or *Bean Instance* (_The most accepted usage in the spec and in other IoC framework_)
 * The proxy on the instance : *Bean client proxy* or *Client proxy* (_Already in the spec even if I don't like the term "proxy"_)
 * Type of injection type : *InjectionPoint Type* (_obvious_)
 * EJB Bean : *Session Bean* (_obvious_)

The idea is to start from the user point of view. The _Bean_ is the object instance that gets injected in the developer code. It has the required _Bean Class_ and the container stores its _Bean Metadata_. Some _Bean_ are not injected directly but are wrapped in _Client Proxy_ to provide CDI services. _Bean_ are provided by the container which use _Injection Point Type_ and Qualifiers to retrieve the corresponding _Bean Metadata_ to lookup for or create the _Bean_ which can be wrapped in a _Client Proxy_ if needed.

I also propose that these terms should be introduced at the beginng of the spec.
                
> 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
>              Labels: CDI_spec_chge
>             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


More information about the cdi-dev mailing list