temporalio / temporalio/sdk-java
Inheritance of workflow interfaces is not supported
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
@WorkflowInterface
public interface CustomerWorkflow {
@WorkflowMethod
void execute(Customer customer);
}
@WorkflowInterface
public interface CustomerWorkflowWithSignal extends CustomerWorkflow {
@SignalMethod(name = "setCustomer")
void setCustomer(Customer customer);
}
Registering two classes that implement the interfaces above should be possible, the second implementation should have a CustomerWorkflowWithSignal name.
Instead, it causes "java.lang.IllegalStateException: CustomerWorkflow workflow type is already registered with the worker".
Special consideration should be put into maintaining compatibility during the fix as it may change the workflow names for some users.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Java interface-registration example from the issue and trace how workflow names are derived and registered. The fix is complete when both implementations can register under the intended names, including CustomerWorkflowWithSignal, while preserving existing workflow names for compatible users; add regression coverage for the inheritance and compatibility cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100