|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Klaus-Peter Löhr, "Automatic Mediation between Incompatible Component Interaction Styles," 2013 46th Hawaii International Conference on System Sciences, vol. 9, pp. 320b, 36th Annual Hawaii International Conference on System Sciences (HICSS'03) - Track 9, 2003. | |||
| BibTex | x | ||
| @article{ 10.1109/HICSS.2003.1174884, author = {Klaus-Peter Löhr}, title = {Automatic Mediation between Incompatible Component Interaction Styles}, journal ={2013 46th Hawaii International Conference on System Sciences}, volume = {9}, year = {2003}, isbn = {0-7695-1874-5}, pages = {320b}, doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2003.1174884}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - CONF JO - 2013 46th Hawaii International Conference on System Sciences TI - Automatic Mediation between Incompatible Component Interaction Styles SN - 0-7695-1874-5 SP EP A1 - Klaus-Peter Löhr, PY - 2003 KW - null VL - 9 JA - 2013 46th Hawaii International Conference on System Sciences ER - | |||
Incompatibility of component interaction styles is identified as a major obstacle to interoperability when using off-the-shelf components or dealing with legacy software in compositional development. It is argued that a language for defining abstract interfaces — AID — can serve as a basis for accommodating heterogeneous interaction styles. AID is independent of any concrete style, such as invocation, pipe-and-filter, event-based or others. An AID text just specifies elementary input and output events which happen at the boundary of a component. Code that mediates between different styles can then be generated automatically from an abstract interface description.
The focus of this paper is on mediating between dataflow and invocation interaction. The design of the mediation code for invocation-based interaction with mismatching push/pull modes is described in some detail. How to accommodate event-based interaction is shown in the context of the CORBA Notification Service. Enterprise Java Beans are taken as an example of a complex component model, and the problems of accommodating the message-driven beans of EJB 2.0 are analyzed.