Supported by AITO. These pages are currently maintained by Alex Potanin |
|
Using Plans for Specifying Preconfigured Bean Sets
Altenbergerstr. 69 A-4040 Linz tel: +43 732 2468 7133 fax: birngruber@ssw.uni-linz.ac.at Keywords:knowledge representation software engineering component oriented programming
Abstract:Component composition is either done manually in a component assembly tool or with specific applications (wizards). However, from the view of the application programmer this situation is not satisfactory. Wizards are not flexible enough and their creation requires sub-stantial efforts. Doing everything manually is annoying, requires quite a good knowledge of the used components and increases the training period of the application programmer con-siderably. Ou work is a new approach for composing a set of JavaBeans using so-called bean plans . A bean plan is a partial description of a set of beans and their wiring. It describes a semi-finished bean suite with some JavaBeans being already preconfigured and preconnected and others being still isolated. The plan does not describe a fixed wiring of components, but can contain interactive decision spots , where the application programmer can interactively take some decisions about the composition. The application programmer can later complete the ensemble with any component assembly tool by defining missing connections and overriding preconfigured properties. The plan is shipped together with the bean suite and it relieves the application programmer from routine configuration tasks. BeanPlan is the scripting language for writing bean plans and will be described in this pa-per. Keywords: Components, Compositional Patterns, Composition Automation, JavaBeans
The participant will apply for the upcoming ECOOP PhD Workshop.
HTML3 JAVA
Last modified on Mon Aug 15 14:59:24 2005 |