Databases Reference
In-Depth Information
Figure 6-28.
The FireBug JavaScript console containing Dynamic Action debug messages
While this doesn't give you any detail about what the dynamic action code is doing, it does give you
a visual indicator that the dynamic action code is firing. For a bit more information you can use
FireBug's console menu to also capture any XMLHttpRequests, as shown in Figure 6-29.
Figure 6-29.
Choosing to show XMLHttpRequests in the console
After this is turned on, you'll not only see the dynamic actions that fire, but also the calls to
WWV_FLOW.SHOW that indicate XMLHttpRequests (or AJAX calls) as shown in Figure 6-30. You'll
notice that the AJAX calls being made actually show up before the debug message from the dynamic
action to which they belong. Don't be confused by this. It's merely a function of when APEX has chosen
to emit the debug message.
