English 
Español
한국어
print pageZoomFlex Remoting Debugger
If you generate a new ZoomFlex application, you'll notice that the application by default contains a "Debug" button. Clicking on this button loads up a window that shows the recent remoting calls made by the ZoomFlex application to the various server-side functions.
A typical scenario for using ZoomFlex Remoting debugging would be when you want to find out which server-side components (and which functions in the components) are being called, what arguments are being passed to the server-side functions, and what results are being returned. The ZoomFlex remoting debugger keeps track of all the calls made and the time taken to execute each server-side function.
The figure above provides is a sample of of remoting debugging. As you'll notice, the debugger provides information about:
- The remote object being invoked
- The method called
- What was the status of the call (false = error, true=success)
- How long did it take to execute
Clicking on any of the remoting calls, displays more information about that call.
If you have removed the "Debug" button from the application that you are working on, you can always put it back into your view using the following steps.
First, add the namespace for the where the component lives. Add the following code to the root tag of your view:
So, for example, in the default code the namespace is declared in the VBox tag:
width = "100%"
height = "100%"
xmlns:zoomComp = "com.straker.zoom.components.*"
xmlns:controllers = "com.zoom.controllers.*"
xmlns:mx = "http://www.adobe.com/2006/mxml">
Second, instantiate the debug button where you want the button to appear.
Recompile your application and you will see the Debug button in your view. Clicking on the button will display a popup that displays all remoting calls made by your application.
Next approach: Using the trace() method »
Comments
There are no comments for this page as yet.
Full RSS
