Debugger Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Description
2.0 Limitations
   2.1 Changing variables on the entry breakpoint of a Receive activity in a business process is not supported
3.0 Known problems and workarounds
   3.1 Debugging menu items not displaying for business state machine programs
   3.2 Removing active icons from the editor

1.0 Description

This release notes file contains late-breaking information about limitations and known problems and workarounds for the WebSphereR Integration Developer debugger.

2.0 Limitations

2.1 Changing variables on the entry breakpoint of a Receive activity in a business process is not supported

If you stop on an entry breakpoint of a Receive activity in a business process, and then try to change variables, the change will not take effect. This action is not supported.

3.0 Known problems and workarounds

3.1 Debugging menu items not displaying for business state machine programs

If you cannot add a breakpoint to a WebSphereR Integration Developer component due to missing or disabled menu items, it might be necessary to restart the project with the -clean option. This option forces Eclipse to load the debugging plugins when the tool starts up.

For example, a project called "foo" might be started with the command line invocation:

    wid.exe -clean -data foo

3.2 Removing active icons from the editor

Usually, the active icons such as popped breakpoints, installed breakpoints, checkmark icons on the links, or exception icons, will be removed when the launcher is terminated. 

However, if the active icons are not removed from the editor,  this is the workaround to remove them: from the Debug view,  select  Terminated launch, and click Remove. The active icons will be removed.