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 Debugging two business object maps that have the same name in different folders
3.0 Known problems and workarounds
   3.1 Refresh problem when debugging JMS custom data binding

1.0 Description

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

2.0 Limitations

2.1 Debugging two business object maps that have the same name in different folders

When you debug an application that contains two business object maps of the same name in different folders or projects, you must delete all the breakpoints in the first map before you set breakpoints in the second. For example, if you set breakpoints in Project1/MyMap.map, then you must delete them before you set breakpoints in Project2/MyMap.map.

Also, if you create a breakpoint in a business object map and then close the business object map editor, the editor will be reopened the next time you restart WebSphere Integration Developer.

3.0 Known problems and workarounds

3.1 Refresh problem when debugging JMS custom data binding

You might experience a refresh problem when you debug JMS custom data binding code. Although the debugger stops at a breakpoint in the custom binding code, the stack frames might not appear.

To work around this problem, follow these steps:

  1. Click the Window menu and select Preferences.
  2. Expand Workbench and select Capabilities.
  3. In the Capabilities list, select the Enterprise Java capability and click OK.
  4. Click the Window menu and select Preferences again.
  5. Expand Run/Debug.
  6. Expand Java and Mixed Language Debug.
  7. Select Thread Filters.
  8. Clear the Apply thread filters option.
  9. Click OK.