Versions Compared

Key

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

...

Requirements

Build the protobuf-extension.jar

You will need to build a Protobuf extension jar to use the Protobuf extension. To do so:

  1. Download the Protocol Buffer Compiler (protoc) mentioned in Requirements.
  2. Run the following command with the appropriate arguments:
    Code Block
    java -jar com.parasoft.soavirt.messages.protobuf.jar <ARGUMENTS>

The example below (for Windows) shows the command with all arguments. This will generate the jar (protobuf-extension.jar) which can then be added to SOAtest:

Code Block
java -jar com.parasoft.soavirt.messages.protobuf-<VERSION>.jar -protoc C:\protoc-<VERSION>-win64\bin\protoc.exe -includes -protoDir C:\<PATH_TO_PROTO_FILES> -logLevel 4

For more information about the Protobuf jar, run:

...

  • .

...

Installation

This artifact can be installed from the UI or the command line.

...

  1. Go to Parasoft > Preferences and click System Properties.
  2. Click Add JARs and choose thecom.parasoft.soavirt.messages.protobuf-extension<version>.jar.
  3. Click Apply.
  4. Restart SOAtest/Virtualize.

Command Line Installation

Add  com.parasoft.soavirt.messages.protobuf-extension<version>.jar to the system.properties.classpath property in your settings properties file. For example:

system.properties.classpath=<path to jar>/com.parasoft.soavirt.messages.protobuf-extension1.3.0.jar

Configuring Protobuf Files Location

The location of your Protobuf files is configured through a Java system property that specifies the path to a local directory that contains your .proto files.

Code Block
-J-Dcom.parasoft.soavirt.messages.protobuf.files=<PATH_TO_PROTO_FILES>

Usage

Anchor
AddingClients
AddingClients
Adding the Protobuf Clients

...

One of the benefits of using the Protobuf extension is the ability to use it in conjunction with the gRPC Transport in order to send messages in one format and receive messages in another format.

Change Log

1.3

  • Decode grpc-status-details-bin header to JSON when both Protobuf and gRPC extensions are loaded

1.2

  • Resolved issue sometimes detecting the wrong message type
  • Resolved various issues in schema generation
  • Automatically detect and consume ProtoJSON

1.0

  • Initial release