This means that to test your code, you need to configure the code lookup in your runtime workbench – a pain if you have multiple runtime workbenches, or frequently clear your runtime workbench metadata.

An alternative approach, which I use, is to disconnect the debugger from the runtime workbench and connect it in your base workbench. This post details how.

The first step is to find out what port your server’s debug process is listening on. The default for WebSphere Application Server is 7777, but this might change if you’ve either customised it or configured multiple server instances. An easy way to check is to select the “debug” view in your Eclipse runtime workbench.

Debug View

In this picture, you can see that my WAS instance is running on port 7778. Make a note of this number, then select (in this view) the server (either of the top 2 lines), and click the disconnect icon (the red ‘N’ with 2 blobs icon). This disconnects the runtime workbench’s debugger from the server, freeing up the server’s debug port for another application i.e. your base workbench.

New config

Next, we need to create a runtime configuration in the base workbench to connect to the server. Open the debug configurations dialog (Run->Debug Configurations), and select “Remote Java Application”, then click the new button. All you really need to change from the default settings are the name (if you want to be able to remember it) and the port (to the port you wrote down earlier). Here’s mine:

Settings

Finally, hit debug and away you go.

By default, Eclipse wont let you have projects with circular dependencies, which can be quite frustrating. To get around this problem, you can (on either a project or workspace level) configure circular dependencies to only trigger a warning, instead of an error.

In Eclipse 3.4, this can be configured in Java Compiler -> Building -> Build path problems -> Circular dependencies

Enabling circular dependencies in Eclipse

Useful links

Internal

• How to debug servers across multiple Eclipse workbenches