I have an activity interface that defines three different (but related) activities, and each requires different options to be specified (e.g., timeouts). From the Java documentation:
Activity options are needed only if some of the required timeouts are not specified through the
This seems to suggest that
@ActivityMethod annotations could be used to specify different options for each activity in a common interface. At the moment, it looks like ActivityMethod.java only supports overriding of the activity’s name.
So, is the only option for achieving different timeouts for different activities to instantiate multiple activity stubs within a workflow (each with its own
ActivityOptions instance? And in this case, would distinct task queues be required for each stub?