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

Antoine Sabot-Durand (JIRA) issues at jboss.org
Wed Feb 26 15:42:47 EST 2014

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

Antoine Sabot-Durand 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).

Yes, I agree: more example sooner in this chapter would benefit understanding.

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

In fact Bean Metadata is already introduced : 5.5.8 use this term many times. And I really think we should have distinctive name between the bean instance and the bean metadata, it's the purpose of this ticket. 

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

In theory it's the best term, but everybody use the *Bean* abbreviation. So, IMO, we really should reserved the term *Bean* to shorten the *Bean Instance* and for nothing else. That said I agree we should try to use *Bean Instance* in the spec.

Proxy - I'm not sure, to my understanding client proxy and contextual reference are synonyms with some formal differences

Yes they're synonyms. I prefer *Bean Reference* but there are so much occurrence of *Proxy* or *Client proxy* in the spec that I hesitate to switch to *Bean Reference*.

InjectionPoint Type - NOK, the spec uses required type consistently (see 5.2 Typesafe resolution), also I don't see any confusion here


> 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

More information about the cdi-dev mailing list