...
- One parasoft-extension.xml file is expected for each Java project.
If you want to add multiple extensions at once, you create one parasoft-extension.xml file that covers all of the extensions you’re adding and you use the top-level
<extensions>element; see Adding Multiple Extensions at Once for details. Parasoft looks for parasoft-extension.xml files in its classpath under the default package, so each of your parasoft-extension.xml files need to be included on the classpath by putting the directories each live in (or the jar files each are contained in) on the classpath in the System Properties preferences.For details on how to configure this file for a specific type of extension, see:
Defining parasoft-extension.xml for a Custom Message Format
Defining parasoft-extension.xml for a Custom Listener
Defining parasoft-extension.xml for a Custom Tool
- Build your Java project and add it to your system properties classpath area, either as a jar file, a Java project within your SOAtest or Virtualize workspace, or a class folder.
Restart SOAtest/Virtualize and verify that the extension appears in the appropriate area.
For details, see the following sections:
| Anchor | ||||
|---|---|---|---|---|
|
...
Custom extensions can depend on Java libraries other than com.parasoft.api.jar. For For more information, see see Configuring External Dependencies.
You can externalize any string displayed in the GUI to support different languages. For For more information, see see Localizing GUI Text.
If you are using an existing extension and later create a new version of that extension that has a different set of GUI options, you can use a version updater to update your saved .tst (SOAtest) or .pva, .pvn (Virtualize) files to adapt them to the new set of options. For more information, see Updating GUI Fields for a New Version.