Hi Jim:

Thank you for your note. Your workshop about component management 
infrastructure poses an interesting question:
http://www.sei.cmu.edu/technology/dynamic_systems/cbs/icsewkshp.html

Are component-based systems different from object-
based systems? How are these differences (if any) 
reflected in component management infrastructures? 

In our experience from the Demeter project, the really useful components
are not only the classes but quite frequently
artifacts which cross-cut the application classes.
We notice three forms of useful cross-cutting components:

1. Adjusters (Mezini) or Mixin-Layers (Batory) which enhance a group of classes.
2. Adaptive Visitors (from the Demeter project) 
   which are task-based enhancements of
   a group of classes.
3. Aspect-descriptions (Kiczales, Lopes) which are syntactic sugar for 
   certain combinations of adjusters and visitors.

In addition, we use classes, UML class diagrams and strategies (in combination
with adjusters and visitors)  as useful reusable components.

Have you also noted cross-cutting reusable components?

-- Karl