[webbeans-dev] Terminology

[Dan Allen]

On Wed, Jan 7, 2009 at 12:07 PM, Jim Knutson <knutson at us.ibm.com> wrote:
> I guess I still have a worry about this.  If I were to take "contextual
> bean" as a term without the context of this discussion, I would initially
> assume that this is a different kind of bean.  As I understand it so far,
> that is not the case.

For the record, I have advocated the term "contextual bean" from
start, except that I like contextual JavaBean because technically
"bean" is just casual for the TM term. Now, when I read "contextual
JavaBean", I don't think of a separate component model. Web Beans has
always been about connecting JSF and EJB, which I think can be
generalized as "helping existing components, whether they be Java EE
components or simple Java objects, find each other in a highly
specialized, type-safe, and contextual way". In a sense, we are
wrapping the components like EJBs in a binding type, but only to help
them work with one another, to glue them together or let them interact
with each other through the manager (events). So if you are asking how
will it be perceived, I am a developer and I am perceiving that
contextual JavaBean means to get JavaBeans (i.e. any components I
already have) working together and to have more well-defined life
cycle callbacks that take into account the scope in which they are
stored.

-Dan

p.s. This e-mail represents my own perception.

-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction