sdk-java
sdk-java copied to clipboard
temporalio
Temporal Java SDK
## Expected Behavior ActivityStubs should be created for each workflow instance / execution separately. But if somebody uses Dependency Injection frameworks with Temporal it's very easy to misconfigure the wiring...
When testing an activity that constantly fails (cannot recover from the failure) and has a large scheduleToClose timeout set (like days/months), or does not have one set at all the...
Temporal strives to provide reasonable defaults for Retry options. Also, we try to not expose `RpcRetryOptions` because of how easy they are to misconfigure. But in some cases, our default...
**Is your feature request related to a problem? Please describe.** We don't report the completion of workflows during replays. This is a good default behavior for these main completion counters,...
Temporal JavaSDK has an untyped `WorkflowStub` that is bound to a specific method invocation (workflow method), while a currently existing ActivityStub is bound to the AcitivityInterface and not to the...
Some workflow state machines have self transitions and additional conditional logic which is not part of the modeled state machine. For example, ActivityStateMachine has these self transitions: ``` SCHEDULE_COMMAND_CREATED -->...
GrpcRetryer retry method by its nature is expected to throw InterruptedException because they 1. perform waiting on a timer 2. could get an Interrupted flag from GRPC calls with a...
**Describe the solution you'd like** Today `io.temporal.internal.testservice.CommandVerifier.verifyCommand` is called on each command to make sure valid or a task failure occurs. Since this is not a task failure caused by...
