sdk-java
sdk-java copied to clipboard
Temporal Java SDK
We want to have an ability (extension point) to control default MDC keys. Now they are statically defined in workers. Why it's important: * we have multiple stacks: Java +...
## Describe what has changed in this PR Currently temporal-testing is using json path 2.8.0 which is causing the temporal-testing to have a CVE detected in maven. Temporal-testing mvn: https://mvnrepository.com/artifact/io.temporal/temporal-testing/1.23.2...
**Describe the solution you'd like** Go and Python and .NET and others use `temporalWorkflowID`, `temporalRunID`, `temporalActivityID`, etc but Java uses `workflowId` and `runId` Cannot change Java's defaults for compatibility reasons,...
We need a mechanism for concurrency control (mutex/semaphore) that fits with the language but is reentrant and deterministic within workflow coroutines. To be used within signal and update handlers and...
Test server only implements list open / closed, need support for this since all SDKs now have a high level API to list workflows that relies on this endpoint.
## Expected Behavior Workflow Failed Cloud Metrics and Java SDK Metrics should "closely" match each other ## Actual Behavior Workflow Failed metrics differ between Temporal Cloud and SDK metrics. ##...
## Expected Behavior `workflow_completed` metric counter is expected to count newly completed executions. ## Actual Behavior workflow_completed counter counts successful completion of workflow methods, including replays for example. ## Additional...
Bumps [org.eclipse.jetty:jetty-bom](https://github.com/jetty/jetty.project) from 9.4.51.v20230217 to 12.0.10. Release notes Sourced from org.eclipse.jetty:jetty-bom's releases. 12.0.10 Changelog #11851 - jetty-ee8-websocket-javax-server export not honoured #11811 - getHeaderNames should return header name once also when...
We have activity, that is using "Asynchronous Activity Completion" and we want to test it. In our case, we just want to test, that activity will send proper kafka message,...
So that users only have to catch one predictable exception