Stephan Herrmann | 0166441 | 2010-04-01 20:28:43 +0000 | [diff] [blame] | 1 | <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 http://www.eclipse.org/legal/epl-v10.html" /> |
| 4 | <link rel=stylesheet type="text/css" href="../css/book.css"> |
| 5 | <link rel=stylesheet type="text/css" href="otguide.css"> |
| 6 | <title>Debugging OT/J programs - Team Monitor View</title> |
| 7 | <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> |
| 8 | </head> |
| 9 | <body> |
| 10 | <h1>Team Monitor View</h1> |
| 11 | <p> |
| 12 | A special view exists for monitoring which team instances have been created and whether each |
| 13 | of them is currently active or not. When debugging callin bindings which do not trigger while |
| 14 | they are intended to do so, the team monitor should provide first help to find out whether |
| 15 | there is any active instance of the team being considered. If no active instance exists, |
| 16 | callins can not trigger. |
| 17 | </p> |
| 18 | <img src="images/screenshots/team_monitor_marked.png" /> |
| 19 | <p> |
| 20 | The team monitor view is a variant of the variables view with the following features: |
| 21 | <ul> |
| 22 | <li>Display all instances of all teams in the system. |
| 23 | <li>Display the activation state of each team instance as one of |
| 24 | <br /><img src="images/team_inact.gif"> a team instance in not active (for the current thread, if one is selected) |
| 25 | <br /><img src="images/team_act.gif"> a team instance is active, either globally or for the |
| 26 | thread selected in the debug view |
| 27 | <br /><img src="images/team_act_implicit.gif"> a team instance is implicitly active due to executing a team or role method. |
| 28 | <li>Change the activation state of a team using the context menu (<span class="ui">Activate Team</span> or <span class="ui">Deactivate Team</span>).<br /> |
| 29 | This operation affects the currently selected thread. If global (de)activation should be |
| 30 | achieved, select the debug target (<img src="images/debugt_obj.gif"/>) instead of any individual thread. |
| 31 | <li>Inspect fields of a team instance or perform any operation inherited from the <a href="debugging.html#variables">variables view</a>.<br/> |
| 32 | Note, that filtering of OT/J Internal Variables is also supported (and enabled by default). |
| 33 | </ul> |
| 34 | <i>Note that teams may only appear if a thread is currently suspended. If teams are visible while |
| 35 | all threads are running, the <span class="ui">Activate Team</span> or <span class="ui">Deactivate Team</span> options |
| 36 | cannot be performed. |
| 37 | </p> |
| 38 | <p><u>Technical note:</u> When debugging an Eclipse application or OSGi fragment with OT/Equinox enabled, |
| 39 | the team monitor can only work if an open Object Teams Plug-in Project can be found in the workspace. |
| 40 | If this requirement is not met a corresponding warning will be logged.</p> |
| 41 | </body> |
| 42 | </html> |