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

[Martin Kouba (JIRA)]

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

Martin Kouba commented on CDI-280:
----------------------------------

I don't think this clarification will help to understand "5.5.8 Bean metadata" better (this section is just complicated).

I wouldn't introduce *Bean Metadata* but rather continue with *Bean*. *Bean Metadata* might be more correct but also possible source of confusion.

We should definitely check whether we use *Bean instance* (aka contextual instance of a *Bean*) consistently.

*Bean Class* - OK
*Proxy* -  I'm not sure, to my understanding _client proxy_ and _contextual reference_ are synonyms with some formal differences
*InjectionPoint Type* - NOK, the spec uses _required type_ consistently (see 5.2 Typesafe resolution), also I don't see any confusion here
*Session bean* - OK
                
> 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_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