Page History

...

1. 1. Interfaces to Implement for Custom Transports

      Interfaces to Implement for Custom Message Formats in SOAtest

      Interfaces to Implement for Custom Tools in SOAtest

      Interfaces to Implement for Custom Listeners in Virtualize

      Interfaces to Implement for Custom Message Formats in Virtualize

      Interfaces to Implement for Custom Tools in Virtualize

      
      

2. Create a parasoft-extension.xml file in the default package of your Java project and configure it as appropriate for the item (or items) you’re adding.

1. 1. One parasoft-extension.xml file is expected for each Java project.

   2. 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 in Virtualize, 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

      For details on how to configure this file for a specific type of extension in Virtualize, see:

      Defining parasoft-extension.xml for a Custom Transport

      Defining parasoft-extension.xml for a Custom Message Format

      Defining parasoft-extension.xml for a Custom Tool

2. 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.

3. Restart SOAtest/Virtualize and verify that the extension appears in the appropriate area. 

   For details, see the following Virtualize sections for details:

   Verifying the New Listener

   Verifying the New Message Format

   For details, see the following Virtualize sections for details:

   Verifying the New Transport

   Verifying the New Message Format

...

• Custom extensions can depend on Java libraries other than com.parasoft.api.jar. For details in SOAtest, see Configuring External Dependencies_soa.For details in Virtualize, see Configuring External Dependencies 1.

• You can externalize any string displayed in the GUI to support different languages.  For details in SOAtest, see Localizing GUI Text_soa.For details in Virtualize, see Localizing GUI Text 1.
  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 details on updating SOAtest artifacts, see Updating GUI Fields for a New Version 1.For details on updating Virtualize artifacts, see Updating GUI Fields for a New Version Virt..