Resolving non-specific problems when using the workbench
Work through the advice provided
to help you to resolve some common problems that can occur when you
use the workbench that are not dealt
with in previous categories.

Editors do not update automatically when the same file is open
in multiple windows
- Scenario: You are working in the Broker Application Development perspective, and are using the associated
editor to work with one or more resources; for example, you are editing
a message flow in the message flow editor or an ESQL
module in the ESQL editor. You have clicked to create a second Eclipse view, and have opened the
same resource in the second window. Changes that you make to the resource
in the first editor window are not reflected in the second editor
window.
- Explanation: The workbench editors
do not automatically update multiple windows in which you have opened
the same resource.
- Solution: Save the contents of the resource file
in the first editor window, then close and reopen additional windows. The reopened windows reflect the updated content.

Deleting or closing a project takes a long time
- Scenario: Deleting or closing a project to save
memory takes a long time.
- Explanation: If a project is referenced by other
projects, removing that project requires all the other projects, and
the projects that refer to them recursively, to be built fully. This
process occurs to keep the content-assist and validation models current.
- Solution: To keep a project open in the workspace
requires very little memory, therefore you do not need to close or
delete projects.
You are experiencing poor performance when working with large
or complex projects
- Scenario: You are experiencing poor performance
in the workbench when working with
large or complex projects.
- Explanation: Frequent project changes, such as adding
and removing projects, or using , use large amounts of memory
due to the size and number of files and the connections between them.
- Solution: Increase your system memory.
You are considering moving database resources within the workbench
- Scenario: You are considering moving database resources
within the workbench, such as the
XMI files for connection, database, schema, and tables.
- Solution: You cannot move database resources after
they are imported. The only move that you can perform
without affecting the integrity of the files is between two projects
while keeping the project-relative path of the files unchanged. To
place the database resources in a different folder, import them again
from the database.
You do not know how to return to the welcome page
- Scenario: You do not know how to return to the welcome
page that was displayed in the workbench when
you first started using it.
- Solution: To open the welcome page:
- From the Help menu, select Welcome. If only one welcome page is available, it is displayed.
If more than one is available, a list is displayed.
- Select the welcome page that you want, for example, WebSphere® Message
Broker Message Brokers Toolkit.
- Click OK.