Versions Compared

Old Version 1

changes.mady.by.user user-50d80

Saved on

compared with

New Version Current

changes.mady.by.user Chieko Sugizaki

Saved on

Key

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

...

Use the following process to add support for all of the various message formats and transports your team is working with. All extension work is done using Java.

  1. Add  [install dir]the com.parasoft.api.jar file located in the <INSTALL>/plugins/com.parasoft.xtestptest.libs.web_[version]<VERSION>/root/ com.parasoft.api.jar 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. Choose File> New> Project

    2. Choose SOAtest> Custom Development> SOAtestJava 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:

...

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

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