ColdFusion Server Debugging
This approach to debugging ZoomFlex applications is valid only in a scenario when you are using ZoomFlex/ShadoCMS on your development server or you have full administrative access to the server on which ZoomFlex/ShadoCMS server is running. In most situations you would use this form of debugging only on your development server. That is the reason why this debugging is listed as a client-side debugging approach.
If you are using the hosted verison of ZoomFlex, then you can skip this approach.
Before you can use this approach, you need to follow through this excellent Adobe article on Using the ColdFusion8 step-through debugger for Eclipse. Once you are through with this article, you should have Eclipse-based ColdFusion8 debugging all setup.
ColdFusion8 debugging lets you setup breakpoints in the ColdFusion code. As that code is run on the server, the Eclipse-based debugger breaks at the breakpoint and you can examine the state of the ColdFusion script (cfm) or component (cfc) at that particular point.
This form of debugging is very useful when you extend/write server-side components and call them from a ZoomFlex application.
A typical scenario for using this kind of debugging would be when you add some server-side code and want to look at the various variables inside the ColdFusion code as the code is running on the server. This helps you ensure that the ColdFusion code is running as expected, before using the returned results in a ZoomFlex application.
Next approach: Monitoring HTTP traffic »
Comments
There are no comments for this page as yet.
print page
