Group items tagged

" Why Object Teams? Team spirit for your objects Building complex systems from isolated objects often yields poor structure which readily decays during system evolution. Objects should team-up in order to co-operate and jointly deliver complex behaviors. Objects play specific roles within a given Team. Context based dispatch Role instances are attached as specializers to existing objects. Object behavior is controlled by the currently active context that determines which roles are active at a given point in time. Contexts are reified into team instances, which may further be used to mediate between roles and maintain state of the collaboration. Modules larger than classes On the road to re-use of modules larger than classes two approaches compete: frameworks and components. For many applications white box frameworks are too fragile and black box components to rigid. Object Teams provide a middle road which balances encapsulation and adaptability. "

" Everthing Object Teams - adding team spirit to your objects. Object Teams with Null Annotations without comments The recent release of Juno M4 brought an interesting combination: The Object Teams Development Tooling now natively supports annotation-based null analysis for Object Teams (OT/J). How about that? :)"

" Should you need to compile an OT/J program outside the OTDT, the following steps should enable you to use ANT for this task: download ecotj.jar you'll always find the latest version here in the column "Command Line Compiler" add it to your ANT runtime classpath (either place it in your ant_lib directory or provide the path by a -lib command line option to ant). in your build.xml set the property build.compiler to use the OTDT compiler in tasks, like that: "