Eiffel: the language
Extended static checking for Java
PLDI '02 Proceedings of the ACM SIGPLAN 2002 Conference on Programming language design and implementation
Component Software: Beyond Object-Oriented Programming
Component Software: Beyond Object-Oriented Programming
Essential COM
The Jndi API Tutorial and Reference: Building Directory-Enabled Java Applications
The Jndi API Tutorial and Reference: Building Directory-Enabled Java Applications
ArchJava: connecting software architecture to implementation
Proceedings of the 24th International Conference on Software Engineering
Specifying Distributed Software Architectures
Proceedings of the 5th European Software Engineering Conference
The Vienna Component Framework enabling composition across component models
Proceedings of the 25th International Conference on Software Engineering
Automated Support for Distributed Software Design
CASE '95 Proceedings of the Seventh International Workshop on Computer-Aided Software Engineering
Pattern-Oriented Software Architecture: Patterns for Resource Management
Pattern-Oriented Software Architecture: Patterns for Resource Management
Software Reuse in Product Populations
IEEE Transactions on Software Engineering
Static verification of component composition in contextual composition frameworks
International Journal on Software Tools for Technology Transfer (STTT)
The spec# programming system: an overview
CASSIS'04 Proceedings of the 2004 international conference on Construction and Analysis of Safe, Secure, and Interoperable Smart Devices
Hi-index | 0.00 |
"Composition Primitives" is a novel component model targeting .NET. The model facilitates composition across component programming frameworks via an adaptation mechanism external to the component. Constructing adapters is relatively inexpensive, because the model is minimal and focused on just one concern: offering enough information to support composition. Although small, the model supports static discovery of the services provided and consumed by a component-- in other words, it is reflective. To strengthen the value of its reflection capabilities, it purposely does not rely on the Service Locator pattern and it supports n-order composition scenarios. In this paper, we present our model and support our claims.