blob: 273fc99fec3027cbd8b7c51fba50bb64506785ae [file] [log] [blame]
Stephan Herrmann01664412010-04-01 20:28:43 +00001<html>
2 <head>
3 <meta name="copyright" content="Copyright Technical University Berlin and others 2004, 2010. This page is made available under the Eclipse Public License v1.0. For full details see" />
4 <link rel=stylesheet type="text/css" href="../css/book.css">
5 <link rel=stylesheet type="text/css" href="otjld/css/ot.css">
6 <style type="text/css">
7 body { margin:10px; }
8 .high { background-color:#a5b7bd;color:white; }
9 .low { background-color:#fff0c8; padding:2px; }
10 .caption { text-decoration:underline; vertical-align:top;position:relative;top:20px; margin-top:10px;}
11 </style>
12 <title>Call hierarchy extended for OT/J</title>
13 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
14 </head>
15 <body>
16 <h1 align="center">Call hierarchy extended for OT/J<a name="callhierarchy"></a></h1>
17 <p>
18 The purpose of the Java call hierarchy view is to statically display all potential
19 control flows originating from or leading to a specific program element.
20 Since callout and callin method bindings in OT/J introduce new kinds of control flows,
21 it is only appropriate to also visualize the control flows induced by such method bindings.
22 </p>
23 <p>
24 Whenever a given method can be invoked via a <b>callout method binding</b>,
25 the call hierarchy shows a <img src="../images/calloutbinding_obj.gif"> callout node.
26 Here all calls to the corresponding role method will be forwarded to the base method.
27 </p>
28 <p>
29 Whenever a <b>callin method binding</b> may intercept a given control flow,
30 a <img src="../images/callinbindingreplace_obj.gif"> callin node is shown.
31 Note, that a callin control flow is only taken at runtime,
32 if the enclosing team is active and no guard predicate evaluates to false.
33 </p>
34 <img src="images/screenshots/CallHierarchy.png"
35 alt="Call hierarchy showing Object Teams method bindings">
36 </body>