Version 3.3.2 Version 3.3.2
OTJLD v1.0
§§1-7.
Support for the join point sub-language ( OTJLD §) is not included in the stable release 1.1.x.
The compiler can be configured using global Preferences or project
specific Properties.
@SuppressWarnings annotation. OTJLD § A.0.1 can be disabled (default is enabled).
| Name | Software under Test | Kind | Number of tests |
|---|---|---|---|
| Jacks | compiler and runtime environment | black box | >1900 (test programs) |
| JUnit | all of the OTDT | white box | >37000 tests. |
Object Teams Project. A wizard will guide you through that process. It will also add the Object Teams class library (otre.jar) to your project's classpath.
team or 
role classes -- wizards will assist you in creating the classes properly.
), roles (), and method bindings (
, 
, 
, 
).team" the same way standard Java keywords are highlighted.team package declaration lets you navigate from a role file ( OTJLD § 1.2.5) to its enclosing team.
), that allows navigating to the binding declaration (or possibly multiple thereof).with{} and within (Expression){} -- are available.
playedBy
declarations and callin/callout method bindings.
playedBy) can be defined by choosing a provided role type and the desired base type with a type selection dialog.
Open Binding Editor).
OTJLD § 1.2.5).
for teams and for roles). (The same icons are used throughout the IDE, whenever a team or role is visible.)
OTJLD § 1.2.5):
) as (separate) files in the team package or
logically (
) as member types of the enclosing team.
extends") inheritance, there is an additional "implicit" role inheritance, established by role name equality in a team hierarchy. In conjunction with team nesting roles support a controlled
form of multiple inheritance.
org.objectteams.otequinox, a plugin ("aspect plugin")
may declare that it adapts classes from a specified other plugin ("base plugin").team class from an aspect plugin
can trigger byte-code aspect weaving into its base plugin at load-time.
As a result an aspect plugin can indeed adapt the behaviour of another plugin.
These bindings are declared using the extension point aspectBindings from
the mentioned plugin org.objectteams.otequinox.
Object Teams Plugin Project is provided, supporting the
development of plugins written in OT/J. This nature features two new launch types:
) for a self-hosted workbench using OT/Equinox.
) to start the Equinox framework with support for OT/J.
configuration/config.ini:
#{ObjectTeams: activate OT/Equinox:
osgi.hook.configurators.include=org.objectteams.eclipse.transformer.hook.HookConfigurator
osgi.framework.extensions=org.objectteams.eclipse.transformer.hook
osgi.classloader.singleThreadLoads=true
ot.equinox=1
# SH}
OTJLD § 1.2.5) OTJLD § 1.3.1) OTJLD § 3) (including callout override ( OTJLD § 3.1(e))) OTJLD § 4) OTJLD § 2.4) OTJLD § 2.3.2 — code for lifting is not filtered out yet)Toggle Breakpoint to set
breakpoints in OT/J-Code. Setting breakpoint in role files is supported, too.
)
view helps to debug issues related to team activation ( OTJLD § 5). For this purpose it displays all known team instances and shows their activation status as one of
,
(either globally or for the thread selected in the debug view), or
(temporarily active because the team or one of its roles is currently executing code).
Go to Language Definition). |