Java Layers.pptVIP

12/7/00 Java Layers/RC,CL Java Layers Language Support for Stepwise Refinement Problem Software development and maintenance is expensive Difficult Takes a long time Reuse is Key Separation of concerns One application feature per component Flexible composition Presentation Overview Part I – Motivation Mixins Stepwise Refinement Drawbacks of Mixins Part II – Java Layers Java Layers Overview Two Language Features An OO Problem An OO Solution Use same lockable code for all 3 classes Encapsulate lockable code in a class Subtype Car, Box, House with new class Mixed-In Classes Mixins Types with parameterized supertypes Depend on type parameters More precisely: Parametric Polymorphism An OO mechanism for code reuse Apply same code to unrelated classes Work with single inheritance Mixins Software Components Question Can we use mixins to build applications out of reusable components? Example: Music Server Variation can occur on many axes: Client interface {getSong, putSong, eraseCopyright, hideBritney, …} Server execution strategy {single threaded, thread-spawning, thread pool, …} Transport type Fault tolerance Server discovery … Music Application Instances Application Assembly is Easy Base Class class Base { } GetSong Mixin class GetSongT extends Base extends T { static public class Client extends T.Client { void getSong(…){…} } static public class Server extends T.Server { void dispatch(Req req){ if (req.name.equals(“getSong”)) processGetSong(req); else super.dispatch(req); } … } } Other Mixins class EraseCopyrightT extends Base extends T { static public class Client extends T.Client { void eraseCopyright(…){…} } … } Stepwise Program Refinement Drawbacks of Mixins Superclass initialization Runtime efficiency Leaf-type references Composition validation Semantic validity Syntactic correctness Recap Software components imply reuse Mixins reuse OO code Mixins build applications incrementally Stepwise program refinement