Debugger - Revision history

Anonymous at 17:00, 4 March 2013

2013-03-04T17:00:03Z

2013-03-04T16:50:37Z

‎Launch Configurations

2013-03-04T16:47:16Z

‎Breakpoint

2013-03-04T16:46:41Z

‎Breakpoint

2013-03-04T16:43:37Z

‎VulCon Debug Perspective

2013-03-04T16:43:00Z

‎VulCon Debug Perspective

2013-03-04T16:42:14Z

‎VulCon Debug Perspective

2013-02-21T17:22:17Z

2013-02-21T17:21:56Z

2013-02-21T17:08:35Z

@@ Line 1: / Line 1: @@
 ==VulCon Debugger==
 Starting from {{GVESB}} v3.3, {{VULCON}} Eclipse plugin has been enhanced with a new feature: the graphical debugger. Now it’s possible to deploy and follow running flows in a {{GVESB}} server, having control about stepping, execution and environment (variables).
@@ Line 92: / Line 93: @@
 ;Tab Commons:
 The Common Tab is a tab that is available to all PDE and Java launch configurations. It defines general aspects of the launch configuration including storage location, console encoding, etc.

@@ Line 77: / Line 77: @@
 *<code> GreenVulcanoESB debug password</code>: Password used to authenticate the user.
 ==Launch Configurations==
-[[File:DebugConfiguration.jpg|thumb|{{VULCON}} Debug Configuration]]
+[[File:debugConf.png|thumb|{{VULCON}} Debug Configuration]]
 Launch configurations are created by "Deploy & Debug" option from the service’s operation contextual menu, or using the New option right clicking the "{{VULCON}} Debugger" from Run->“Debug Configuration…” menu.
 Following is a snapshot of {{VULCON}}Debugger launch configuration:

@@ Line 44: / Line 44: @@
 </syntaxhighlight>
 ==Breakpoint==
-[[File:breakpoint|thumb|{{VULCON}} Debug Breakpoint]]
+[[File:breakpoint.png|thumb|{{VULCON}} Debug Breakpoint]]
 On the graphical view of an operation, is possible to toggle breakpoints from the contextual menu of a node using the voice ''Toggle Breakpoint''.
 Breakpoints shown on ''Breakpoint View'' have following structure:

@@ Line 44: / Line 44: @@
 </syntaxhighlight>
 ==Breakpoint==
-[[File:breakpointVulcon.jpg|thumb|{{VULCON}} Debug Breakpoint]]
+[[File:breakpoint|thumb|{{VULCON}} Debug Breakpoint]]
 On the graphical view of an operation, is possible to toggle breakpoints from the contextual menu of a node using the voice ''Toggle Breakpoint''.
 Breakpoints shown on ''Breakpoint View'' have following structure:
@@ Line 50: / Line 50: @@
 - Service [Service Name] Operation [Operation Name] Node [Node Name]
 </syntaxhighlight>
 ==VulCon Debug execution control==
 [[File:buttons.png|thumb|{{VULCON}} Debug buttons]]

@@ Line 10: / Line 10: @@
 Right-clicking the Operation to debug, the contextual menu is opened and you can choose "Deploy & Debug". When "Deploy & Debug" menu voice is selected, a new Debug launch configuration for the selected Operation is created and the {{GVESB}} server is contacted and made ready for service debugging. Afterward, within a minute, the user must start the service in the ESB.
 ==VulCon Debug Perspective==
-[[File:vulcondebug.jpg|thumb|{{VULCON}} Debug]]
+[[File:vulcondebug.png|thumb|{{VULCON}} Debug]]
 After the service to debug has been started, the {{GVESB}} server stops service execution on the first node of the flow, following the "Start" node.
 If not, a graphical view of the operation is opened, and the node, where the execution is currently hold, is sharpened with a green pattern.

@@ Line 10: / Line 10: @@
 Right-clicking the Operation to debug, the contextual menu is opened and you can choose "Deploy & Debug". When "Deploy & Debug" menu voice is selected, a new Debug launch configuration for the selected Operation is created and the {{GVESB}} server is contacted and made ready for service debugging. Afterward, within a minute, the user must start the service in the ESB.
 ==VulCon Debug Perspective==
-[[File:VulConDebugProspective.jpg|thumb|{{VULCON}} Debug]]
+[[File:vulcondebug|thumb|{{VULCON}} Debug]]
 After the service to debug has been started, the {{GVESB}} server stops service execution on the first node of the flow, following the "Start" node.
 If not, a graphical view of the operation is opened, and the node, where the execution is currently hold, is sharpened with a green pattern.
@@ Line 17: / Line 17: @@
 *<code>Full red</code>: used to signal a node where a breakpoint is set.
 *<code>Half red, half green</code>: used to signal the node where the execution is currently hold as well a breakpoint is set.
 ==Debug View==
 The ''Debug view'', normally placed on the top left side of the perspective, shows the parts of the {{GVESB}} operation flow call stack which are currently executed and how they relate to each other. Following is the {{VULCON}} Debugger call stack structure:

@@ Line 66: / Line 66: @@
 |-
 |}
-=={{VULCON}}Debug Preferences==
+=={{VULCON}} Debug Preferences==
 A new preference link has been added where it’s possible to set preferences for the {{VULCON}} Debugger.
 <syntaxhighlight lang="XML">

@@ Line 84: / Line 84: @@
 ;Tab Main:
 The Main Tab allows the user to customize settings for the launch configuration.
-*<code>{{GVESB}}Service</code>: Service’s name to debug.
+*<code>{{GVESB}} Service</code>: Service’s name to debug.
-*<code>{{GVESB}}Service Operation</code>: Service’s operation name.
+*<code>{{GVESB}} Service Operation</code>: Service’s operation name.
 ;Tab Source:
 The Source tab is a standard Eclipse option that allows you to control where Eclipse will look for your source files.
 ;Tab Commons:
 The Common Tab is a tab that is available to all PDE and Java launch configurations. It defines general aspects of the launch configuration including storage location, console encoding, etc