Page History

...

1. Add [install dir]/plugins/com.parasoft.xtest.libs.web_[version]/root/com.parasoft.api.jar to your Java project classpath. You can also create a new project by going toFile> New> SOAtest>Custom Development> SOAtest Java Project orFile> New>Virtualize> Custom Development> Virtualize Java Project; this will create a new Java project that already has that .jar file added to the classpath.

   
   

   Info
   icon false title Building with Maven?
   If you’re building your Java project with Apache Maven, you can add the following to your project's pom.xml: Code Block <project> ... <dependencies> <dependency> <groupId>com.parasoft.soavirt</groupId> <artifactId>com.parasoft.api</artifactId> <version>9.9.0</version> <!-- should match product version --> <scope>provided</scope> </dependency> </dependencies> ... <repositories> <repository> <id>ParasoftMavenPublic</id> <name>Parasoft Public Repository</name> <url>http://build.parasoft.com/maven/</url> </repository> </repositories> ... </project>

2. Implement the appropriate interfaces. See the following sections for details on implementing the appropriate interfaces:
   
   

   Interfaces to Implement for Custom Transports in SOAtest

   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

   
   

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

...

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

• You can externalize any string displayed in the GUI to support different languages.  For details in SOAtest, see Localizing GUI Text.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..