What about beans? ;-)
beans or components. Every JavaBean or EJB is a bean or component, no? or how bout module (which may consist of one or more components or beans)?
Modular programming is a software design technique that increases the extent to which software is composed from separate parts, called modules. Conceptually, modules represent a separation of concerns, and improve maintainability by enforcing logical boundaries between components. Modules are typically incorporated into the program through interfaces. A module interface expresses the elements that are provided and required by the module. The elements defined in the interface are visible to other modules. The implementation contains the working code that corresponds to the elements declared in the interface.
modules don't fit, a module's generally bigger than 1 class.
beans seem awkward; and over used, since there's lots of beans
in the various java editions. plus, it confused our WSA's when i said it.
i'm inclined to say an Injectable Bean (iBean) or Contextual Bean (CB) might describe them better.
My vote goes to COCO - Contextual Component. In JCDI4EE, every POJO is a COCO ;-)
Nicklas Karlsson wrote on Jun 08, 2009 14:18:
My vote goes to COCO - Contextual Component. In JCDI4EE, every POJO is a COCO ;-)
+1