le page request. For instance, consider the following code, which is an application built in
Fusebox 5:
Let’s see how the debug view (stack trace) appears at this point in this sample application.
This reects not only that we’re stopped on line 5 of dsp_productdetails.cfm, but also
that we got there from store.productdetails.cfm, which must have called or included dsp_
productdetails.cfm page on its own line 15, and so on. It’s great to be able to see, at any
point of execution in our request, how we got to where we are, based on which les were
called. Note that you can double-click on any of the lines shown in that stack trace to jump
to the indicated le and line of code.
Stepping into Other Files
Getting back to stepping through code, we can see in Figure 5 that the debugger is stopped
on line 5, which is about to call something called product.getDescription(). This looks like a
CFC (represented by product) calling a method called getDescription. But can the debugger
help us make sure that this is a CFC? Yes it can. Look at Figure 7, which shows that I’ve selected
Figure 5: Fusebox sample code
Figure 6: Debug (stack trace) view of Fusebox application
Figure 7: Variables view showing CFC metadata
The Fusion Authority Quarterly Update Tools 93
Kommentare zu diesen Handbüchern