New CFML Debugger Available for Railo 3.1

September 4, 2009 · By webrat · 5 Comments

New in Railo 3.1 is an interface to interact with the CFML debugger, FusionDebug. Now Railo developers have the opportunity to benefit from using an interactive step debugger.

  • Increase your productively
  • Improve code quality
  • Debug your CFML code faster
  • Better understand your code
  • Accelerate the learning of CFML and existing CFML applications

What is an interactive step debugger?

Interactive step debuggers let you see what is happening in your application as each line of code is being executed. You can use the FusionDebug CFML debugger to set breakpoints, step over, into, or out of code, inspect variables (across different scopes), and watch expressions. Modify the values of variables as your code is executing, so that you can force specific execution paths. You can even stop on certain runtime exceptions to see what is happening, and add conditions to your breakpoints so they only fire when the expression evaluates to true. FusionDebug is particularly helpful when testing code that does not produce HTML output, such as components (CFCs), SOAP web services, Ajax applications, and Adobe Flex™ or Flash® applications that use Flash Remoting.

Why would I need a CFML debugger?

Debugging CFML pages usually requires using lots of <cfoutput> statements, <cfdump> or writing to log files. As applications grow more sophisticated with the addition of object oriented components, and the integration of Flex, it's becoming increasingly difficult to solve complex problems. FusionDebug solves these problems by allowing you to suspend any page or component during its execution and see all the variables used by that page. You can add specific watch expressions as well as set variable values while the page is suspended. Pages can then be single-stepped or resumed.

Do I have to edit my code in Eclipse?

If you use Dreamweaver, CFStudio, HomeSite+, CFEclipse or even a text editor, don't worry. You don't have to use Eclipse to edit pages, or change your development platform. You can still develop with Dreamweaver or whatever your favorite editor happens to be, and jump into FusionDebug whenever you need to work out a problem. FusionDebug is able to use your files from the software you used to create them.

Try out using a step debugger when developing CFML.

A complimentary 20 day trial is available for FusionDebug CFML debugger. You can download the trial from the FusionDebug website.

Download trial: http://www.fusion-reactor.com/fd/downloads.cfm

Tags: Railo 3.1 · Testing

5 responses so far ↓

  • 1 George Webster // Sep 4, 2009 at 7:38 AM

    This is great! I will have to try this out. Also while it is not a step debugger ColdFire will provide the full debug info in firebug. It appears they have support for 3.1 beta, not sure if they have worked out any kinks for the full release yet.


    http://coldfire.riaforge.org/blog/index.cfm/2009/5/29/Initial-Railo-Support
  • 2 Sebastiaan // Jan 7, 2010 at 10:51 AM

    Dear Franz and Railo,

    Is there a way to get proper debuggin in Railo Barry (Railo 3.1.2.001 final)? I can only see the templates being run and the queries, but no CGI/URL/FORM/etc name/value pairs. This is essential to be able to debug properly. In CF it's just click and go - is there anything I'm missing here?
  • 3 Todd Rafferty // Jan 14, 2010 at 8:36 PM

    @Sebastiaan: Use the &quot;neo&quot; templates?
  • 4 Sebastiaan // Jan 14, 2010 at 11:23 PM

    I do, it doesn't matter which template I apply, they all only give me the Pages and Queries debug info...

    Currently using the Railo Express version with Jetty.

    There seems to be a lot less options compared to ACF - but it works the same and is lightning fast ;-)
  • 5 Sebastiaan // Jan 14, 2010 at 11:30 PM

    Still having to get use to two Administrators :-)

    Now I've set the neo-debug template in the Web Admin as well and now I get all debug info I expect. I assumed that as I set that debug template in the Server Admin it would automagically transfer to the Web Admin. But alas, only partially, it doesn't automagically inherit the debug template from the Server Admin, only the &quot;Enable debugging&quot; setting...

    Got any other handy Railo-tips?

Leave a Comment

Leave this field empty: