An architecture for extensible middleware platforms
This article presents a middleware platform architecture whose goals, motivated by the needs of a real‐world application, are the following: separation of functional and non‐functional code in applications, composition of non‐functional properties, and modularity and extensibility of the middleware...
Saved in:
Published in: | Software, practice & experience Vol. 31; no. 13; pp. 1237 - 1264 |
---|---|
Main Authors: | , |
Format: | Journal Article |
Language: | English |
Published: |
Chichester, UK
John Wiley & Sons, Ltd
10-11-2001
|
Subjects: | |
Online Access: | Get full text |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Summary: | This article presents a middleware platform architecture whose goals, motivated by the needs of a real‐world application, are the following: separation of functional and non‐functional code in applications, composition of non‐functional properties, and modularity and extensibility of the middleware platform itself. This architecture is inspired by the Enterprise Java Beans platform, and uses a new object composition model to separate and compose the non‐functional properties. In order to evaluate this architecture, we have implemented the JavaPod platform which we have used to implement a prototype of the application that motivated our goals. The results of these experiments show that our goals can indeed be achieved with our architecture. Copyright © 2001 John Wiley & Sons, Ltd. |
---|---|
Bibliography: | ArticleID:SPE412 istex:3CA53BF0EF0AEFD05112EBD3BF33A6E8CD80BC7C ark:/67375/WNG-39VX8JVP-9 In collaboration with France Telecom, 38–40 Rue Gal Leclerc, 92794 Issy Moulineaux, France. ObjectType-Article-2 SourceType-Scholarly Journals-1 ObjectType-Feature-1 content type line 23 |
ISSN: | 0038-0644 1097-024X |
DOI: | 10.1002/spe.412 |