-
Notifications
You must be signed in to change notification settings - Fork 132
/
DynamicWorkflow.java
48 lines (45 loc) · 2.02 KB
/
DynamicWorkflow.java
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
/*
* Copyright (C) 2022 Temporal Technologies, Inc. All Rights Reserved.
*
* Copyright (C) 2012-2016 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Modifications copyright (C) 2017 Uber Technologies, Inc.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this material except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package io.temporal.workflow;
import io.temporal.common.converter.EncodedValues;
/**
* Use DynamicWorkflow to implement any number of workflow types dynamically. When a workflow
* implementation type that extends DynamicWorkflow is registered, it is used to implement any
* workflow type that is not implicitly registered with the {@link io.temporal.worker.Worker}. Only
* one type that implements DynamicWorkflow per worker is allowed.
*
* <p>The main use case for DynamicWorkflow is an implementation of custom Domain Specific Languages
* (DSLs). A single implementation can implement a workflow type which definition is dynamically
* loaded from some external source.
*
* <p>Use {@link Workflow#getInfo()} to query information about the workflow type that should be
* implemented dynamically.
*
* <p>Use {@link Workflow#registerListener(Object)} to register signal and query listeners. Consider
* using {@link DynamicSignalHandler} and {@link DynamicQueryHandler} to implement handlers that can
* support any signal or query type dynamically.
*
* <p>All the determinism rules still apply to workflows that implement this interface.
*
* @see io.temporal.activity.DynamicActivity
*/
public interface DynamicWorkflow {
Object execute(EncodedValues args);
}