Versions Compared

Old Version 1

changes.mady.by.user Robert Andelin

Saved on

compared with

New Version 2

changes.mady.by.user Robert Andelin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2025.2

...

  1. Add the com.parasoft.api.jar file located in the <INSTALL-DIR>/plugins/com.parasoft.ptest.libs.web_<VERSION>/root/ directory to your Java project classpath. You can also create a new Java project that already has the .jar file added to its classpath: 
    1. Go to File > New > Project.

    2. Choose SOAtest or Virtualize > Custom Development > SOAtest or Virtualize Java Project

      Info
      iconfalse
      titleBuilding 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

    3. Interfaces to Implement for Custom Message Formats in SOAtest

  3. Interfaces to Implement for Custom

    4. Tools in SOAtestInterfaces to Implement for Custom

  4. Listeners

    5. in Virtualize

  5. Interfaces to Implement for Custom Message Formats

    6. in Virtualize

  6. Interfaces to Implement for Custom Tools

    7. in Virtualize

  8. 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. 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 FormatTransport

      Defining parasoft-extension.xml for a Custom ListenerMessage Format

      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

      Listener

      Defining parasoft-extension.xml for a Custom Message FormatDefining 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 ListenerTransport

    Verifying the New Message Format

    For details, see the following Virtualize sections for details:

    Verifying the New Transport

    Listener

    Verifying the New Message Format

...