Adding Javadoc or Source links to WTK components

Beginning with release 0.9.0 of EclipseME, you can add Javadoc or source links to components of a Wireless Toolkit (WTK). This allows you to do source-level debugging (assuming the WTK has been compiled with debug information) and to use Eclipse's context-sensitive API help features.

  1. Attaching Javadoc to a WTK
  2. Attaching Source to a WTK

Attaching Javadoc to a WTK

In order to attach Javadoc to a WTK component, perform the following steps:

  1. Open the Platform Components window by selecting Preferences from the Window menu, expanding the J2ME item in the left column, and click on the Platform Components item.
  2. Expand one of the Wireless Toolkits, Platform Definitions, or Profiles items, and find the particular JAR file to which you want to attach Javadoc.
  3. Expand the JAR file itself to expose the Javadoc Attachment item underneath the JAR file.
    screenshot
  4. Right-click on the Javadoc Attachment item and select Add Javadoc Attachment. The following dialog will be displayed:
    screenshot
  5. Fill in the appropriate information in the dialog and press the OK button. You can use the Validate button to check that the expected files are present in the location you specify. Once you do this, the Javadoc attachment will be shown in the Platform Compoents dialog:
    screenshot

Note that if you add the Javadoc attachment to a JAR file in one part of this dialog box, such as under "Profiles", all the other areas pick up the attachment as well. If you have more than one Wireless Toolkit installed, however, you need to attach the Javadoc separately to each of the separate toolkits.

Attaching Source to a WTK

Attaching source to a WTK component works exactly the same as attaching Javadoc, except that you use the "Source Attachment" item instead of the "Javadoc Attachment" item.

Note that not all Wireless Toolkits are distributed with the classes in the JAR file compiled with debug information. Thus, even though you may have attached the source to the JAR file, you may still not be able to step into the WTK source.