FusionDebug Rev. 3.0.0.Beta 1 for Railo

^{FDRAILO-TRUNK.19.13055}

RELEASE NOTES - KNOWN ISSUES - ADDITIONAL LICENSE AGREEMENTS

INTERGRAL INFORMATION SOLUTIONS GMBH
Schickardstr 32 - D-71034 Boeblingen - Germany

The FusionDebug software is Copyright (C) 2006-2008 Intergral Information Solutions GmbH.
All rights reserved. The FusionDebug software product is commercial software and may not be
redistributed except with the express written agreement of Intergral Information Solutions GmbH.
The software may only be used in accordance with the appropriate FusionDebug license agreement.

Status: Wed, 1 Apr 2009

RELEASE NOTES

• FusionDebug Rev. 3.0.0.Beta 1 for Railo

• BETA EXPIRY: FusionDebug 3.0.0 Beta 1 expires 23:59 May 31st 2009.

• FusionDebug Rev. 3.0.0 introduces a modular interface structure allowing different CFML engines
  to be used as debug targets. This beta has been built with support for Railo 3.1.0 when run in
  debug mode (see beta guide for instructions on starting Railo in debug mode).

We are very pleased to be working closely with Railo to provide this facility.

• No license is required to use this beta. After the beta period expires (at 23:59 on May 31st 2009),
  you will be unable to launch any debug sessions.

• We would appreciate your feedback on this beta product. Please do get in touch with us at fdbeta@intergral.com

• FusionDebug Rev. 3.0.0.0 Beta 1 has been tested using Eclipse Platform 3.2 to 3.4.2 (Ganymede) on
  Microsoft Windows XP SP2, Microsoft Windows Vista SP 1. FusionDebug is a pure Java
  application with no native dependencies, and so should run on all OS platforms for which Eclipse is
  available.

• We recommend installing the Eclipse Java SDK package. This can be obtained from http://www.eclipse.org/downloads/

• We recommend also installing the CFEclipse package, which provides a capable environment for
  working with CF scripts within Eclipse. This can be obtained from: http://www.cfeclipse.org/

• Please consult the Beta Guide for quick-start instructions on getting acquainted with FusionDebug. We will release
  an updated User Manual for 3.0.0 final.

KNOWN ISSUES

FusionDebug Rev. 3.0.0.Beta1

THIS IS A BETA RELEASE

The following issues are known at the time of publication.

• You should increase the length of the Railo page timeout in the Railo Administrator -> Settings -> Application.
  If you do not do this, there is a danger of Railo timing out pages paused by the debugger.

• FD-469 FusionDebug may become slow when stress-stepping (holding down Step-Into or Step-Over
  keyboard shortcuts) an application, while the "Variables" view is visible.

• FD-488 Exception breakpoint support. It is not currently possible to have a "Breakpoint on Exception"
  in FusionDebug

• FD-491/RAILO-196 Variables within scopes appear to be unordered.

• FD-492 Server memory creep. A small quantity of memory within the Railo server is consumed and not released
  when debugging. Disconnecting FusionDebug and restarting Railo corrects this issue.

• FD-493/RAILO-195 Stepping is innacurate within very long pages. You may find the line cursor skips
  to an incorrect line, or skips back and forth, when debugging very large CFC or CFM pages.

• FD-494/RAILO-194 When stepping through <CFScript> tags, the first script line immediately following the tag
  appears to be skipped.

• FD-496 When stepping through <CFLoop> tags, the line cursor appears to skip to the end of the tag before
  commencing to step.

GENERAL ISSUES

Some Numerical / Complex CF Types Decode to Java Types, Not CF Types

We're working hard on being able to decode all CFML complex types. Most types are already
implemented - structs, arrays, XML objects, CFCs, Functions etc. In some cases, you might see
an undecoded type in the Variables and Expressions view ("... instance of ...") or a plain
string representation of the object.

Step Over sometimes requires > 1 keypress to advance the cursor.

This is because some lines of CF code perform multiple actions and require you to press
step for each action that they perform.

Step Into CFC's is sometimes requires > 1 keypress to step into the CFC.

With the current instruction pointer located on the CFINVOKE tag, keep clicking Step Into until
the CFC is loaded. The parameters and other initialization actions are performed before the CFC
is called. You may have to push step into until this initialization is complete.

Step Requests sometimes jump around to lines of code that are not sensible.

This is a limitation of how CF processes and optimizes pages at compile time.

Calling CF functions which are reentrant to the currently halted thread may cause the VM to hang

You cannot set/clear breakpoints with CTRL-SHIFT-B when in the CFEclipse perspective

CFEclipse does not support the CTRL-SHIFT-B keystroke when in the CFEclipse perspective. You
can toggle the breakpoint by right mouse clicking on the line you wish to set the breakpoint
on and using the Toggle Line Breakpoint menu item.

Sometimes breakpoints don't fire.

In the Debug configuration, make sure the Target System Type is set correctly: checked for
Windows, unchecked for Unix.

Breakpoints set on blank lines may not always fire.

Since FD 2.0.1 breakpoints can be set on blank lines. FD cannot always get breakpoints to
fire on blank lines because they are sometimes optimized away by the CF compiler.

Wrong File Selected

When a breakpoint or step event fires, FusionDebug does its best to find the source file. If the
same file exists multiple times in different projects, the wrong one may be selected
Use the source code lookup tab on the Launch Control to correct the source code lookups.

If your system is monitored by FusionReactor with crash protection activated, FusionReactor may

terminate the page if it exceeds the Request Timeout limit that has been configured. Please
deactivate crash protection in FusionReactor.

ADDITIONAL LICENSE AGREEMENTS

This Software contains code derived from the Eclipse Foundation ("Eclipse Code").
Such Eclipse Source Code is made available under the terms of the Eclipse Public License v1.0 which
accompanies such code, and is also available at http://www.eclipse.org/legal/epl-v10.html

Eclipse Code. On behalf of Contributors to such Eclipse Code, Intergral hereby: (1) disclaims any and all
warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability
and fitness for a particular purpose with respect to such Eclipse Code and any and all derivative works thereof,
(2) disclaims any liability for damages, including direct, indirect, special, incidental and consequential
damages, such as lost profits, and (3) represents that any provisions in this License Agreement that differ
from the Eclipse Public License under which Intergral licensed the Eclipse Code, are offered by Intergral
alone and not by any other party. The source code for the Eclipse Code as contained in this Software may be
obtained by the Licensee as described in in this Readme to the Software. Intergral provides the Eclipse Code as
is, without warranty or support from Intergral.

By installing this product, in addition to the Intergral license terms, you also agree to be bound by the
third-party terms provided to you with the Intergral product documentation. Intergral recommends that you review
these third-party terms.