Class InteractiveSubmissionServiceGrpc.InteractiveSubmissionServiceFutureStub
java.lang.Object
io.grpc.stub.AbstractStub<S>
io.grpc.stub.AbstractFutureStub<InteractiveSubmissionServiceGrpc.InteractiveSubmissionServiceFutureStub>
com.daml.ledger.api.v2.interactive.InteractiveSubmissionServiceGrpc.InteractiveSubmissionServiceFutureStub
- Enclosing class:
- InteractiveSubmissionServiceGrpc
public static final class InteractiveSubmissionServiceGrpc.InteractiveSubmissionServiceFutureStub
extends io.grpc.stub.AbstractFutureStub<InteractiveSubmissionServiceGrpc.InteractiveSubmissionServiceFutureStub>
A stub to allow clients to do ListenableFuture-style rpc calls to service InteractiveSubmissionService.
Service allowing interactive construction of command submissions The prepare and execute endpoints allow to submit commands in 2-steps: 1. prepare transaction from commands, 2. submit the prepared transaction This gives callers the ability to sign the daml transaction with their own signing keys
-
Nested Class Summary
Nested classes/interfaces inherited from class io.grpc.stub.AbstractStub
io.grpc.stub.AbstractStub.StubFactory<T extends io.grpc.stub.AbstractStub<T>>
-
Method Summary
Modifier and TypeMethodDescriptionbuild
(io.grpc.Channel channel, io.grpc.CallOptions callOptions) com.google.common.util.concurrent.ListenableFuture<InteractiveSubmissionServiceOuterClass.ExecuteSubmissionResponse>
com.google.common.util.concurrent.ListenableFuture<InteractiveSubmissionServiceOuterClass.GetPreferredPackageVersionResponse>
getPreferredPackageVersion
(InteractiveSubmissionServiceOuterClass.GetPreferredPackageVersionRequest request) A preferred package is the highest-versioned package for a provided package-name that is vetted by all the participants hosting the provided parties.com.google.common.util.concurrent.ListenableFuture<InteractiveSubmissionServiceOuterClass.PrepareSubmissionResponse>
Requires `readAs` scope for the submitting party when LAPI User authorization is enabledMethods inherited from class io.grpc.stub.AbstractFutureStub
newStub, newStub
Methods inherited from class io.grpc.stub.AbstractStub
getCallOptions, getChannel, withCallCredentials, withChannel, withCompression, withDeadline, withDeadlineAfter, withExecutor, withInterceptors, withMaxInboundMessageSize, withMaxOutboundMessageSize, withOnReadyThreshold, withOption, withWaitForReady
-
Method Details
-
build
protected InteractiveSubmissionServiceGrpc.InteractiveSubmissionServiceFutureStub build(io.grpc.Channel channel, io.grpc.CallOptions callOptions) - Specified by:
build
in classio.grpc.stub.AbstractStub<InteractiveSubmissionServiceGrpc.InteractiveSubmissionServiceFutureStub>
-
prepareSubmission
public com.google.common.util.concurrent.ListenableFuture<InteractiveSubmissionServiceOuterClass.PrepareSubmissionResponse> prepareSubmission(InteractiveSubmissionServiceOuterClass.PrepareSubmissionRequest request) Requires `readAs` scope for the submitting party when LAPI User authorization is enabled
-
executeSubmission
public com.google.common.util.concurrent.ListenableFuture<InteractiveSubmissionServiceOuterClass.ExecuteSubmissionResponse> executeSubmission(InteractiveSubmissionServiceOuterClass.ExecuteSubmissionRequest request) -
getPreferredPackageVersion
public com.google.common.util.concurrent.ListenableFuture<InteractiveSubmissionServiceOuterClass.GetPreferredPackageVersionResponse> getPreferredPackageVersion(InteractiveSubmissionServiceOuterClass.GetPreferredPackageVersionRequest request) A preferred package is the highest-versioned package for a provided package-name that is vetted by all the participants hosting the provided parties. Ledger API clients should use this endpoint for constructing command submissions that are compatible with the provided preferred package, by making informed decisions on: - which are the compatible packages that can be used to create contracts - which contract or exercise choice argument version can be used in the command - which choices can be executed on a template or interface of a contract Can be accessed by any Ledger API client with a valid token when Ledger API authorization is enabled. Experimental API: this endpoint is not guaranteed to provide backwards compatibility in future releases
-