Third, if you want to use the Sandbox security feature in the Multiserver or J2EE conguration,
you’ll need to enable a Java security manager (java.lang.SecurityManager), which is also
done by dening the JVM arguments in the jvm.cong le. For JRun, this is the java.args line
in the jrun_root/jvm.cong le:
-Djava.security.manager -Djava.security.policy=”cf_root/WEB-INF/cfusion/lib/coldfusion.
policy” -Djava.security.auth.policy=”cf_root/WEB-INF/cfusion/lib/neo_jaas.policy”
Dierences Between the Debugger and FusionDebug
The focus in this article has been on the CF8 debugger, but along the way I’ve mentioned
a few ways in which the debugger is the same as or dierent from FusionDebug. Let’s do a
quick recap here. First, the CF8 debugger runs only on ColdFusion 8, where FusionDebug
works with ColdFusion 6, 7, and 8. On the other hand, you can use the CF8 debugger with
the free Developer edition of ColdFusion, but then you can’t use it for multiple developers
(or rather, you can’t use it for any more than ColdFusion will support for making requests
against the Developer edition, which is localhost plus two IP addresses.)
Some of the advantages of the CF8 debugger are related to use by multiple developers.
I’ve mentioned that the debugger does permit multiple developers to debug a single
ColdFusion server, and that it uses RDS to control such access. An administrator can control
debugger access using a single RDS password shared by all, or separate RDS accounts per
user in the Enterprise or Developer editions. For some, the fact that the debugger requires
RDS access may be a disadvantage. They’ve been conditioned to regard RDS as something
that should be disabled. Since the debugger is primarily a developer tool, though, as is RDS,
this shouldn’t be as much of a concern (though certainly for public production or central test
environments, it may be something to consider carefully due to the security implications of
enabling RDS on such public servers.)
Related to the multiple developer feature, the CF8 debugger only stops the rst user making
a certain request, while FusionDebug lets you intercept all requests for a page, from all users.
That could be an advantage or a disadvantage. You may wish (with the CF8 debugger) that
you could see the requests of more than the rst user hitting a page, or you may be annoyed
(by FusionDebug) that it lets you intercept the requests of any user hitting a page.
But the debugger adds something that FusionDebug lacks, which I haven’t mentioned
previously; the debugger adds another tab next to Variables and Breakpoints called Debug
Output Buer, which shows the HTML or other content generated to that point in the ow
of execution. Very handy. Also, as I mentioned, the debugger lets you stop on an error.
Conclusion
That’s a lengthy review of features, benets, and challenges in using the ColdFusion
8 debugger. I do hope that the introduction to step debugging and the debugger
interface and features will help you get started. For more on step debugging in CFML,
you may want to review the series of blog entries I’ve done previously on FusionDebug, at
http://carehart.org/blog/client/index.cfm/fusiondebug,
or my previous article in Fusion
Authority Quarterly Update Volume 1 Issue 2.
You can also read more about the CF8 debugger in the CFML manual, ColdFusion Developer’s
Guide, in the chapter, “Using the ColdFusion Debugger”, as well as in the DevCenter article,
“Using the ColdFusion 8 step-through debugger for Eclipse”, both of whose URLs I oered
in the Getting Started section above.
96 Tools The Fusion Authority Quarterly Update
(24 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji