Separating Dapr Workflows documentation on Spring Boot to it's separate page #4975
+91
−49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
salaboy
force-pushed
the
sb-workflows
branch
from
d2de566 to
e28ede4
Compare
Signed-off-by: salaboy <Salaboy@gmail.com>
Removed duplicate information and streamlined the scenarios for configuring secrets access. Signed-off-by: rohit <50377477+caretak3r@users.noreply.github.com> Signed-off-by: salaboy <Salaboy@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
salaboy
force-pushed
the
sb-workflows
branch
from
dd7dd60 to
51d0e5f
Compare
msfussell
reviewed
Dec 14, 2025
Member
msfussell
left a comment
msfussell
left a comment
There was a problem hiding this comment.
Some light editing. Please read the Dapr doc style recommendations. No "we" (instead use you or none) and minimize "will" to use the present tense as in this is how it works now.
|
|
||
| Following the same approach that we used for Spring Data and Spring Messaging, the [`dapr-spring-boot-starter`](_index.md) brings Dapr Workflow integration for Spring Boot users. | ||
|
|
||
| With Dapr Workflows you define complex orchestrations (workflows) in (Java) code. The Dapr Spring Boot Starter makes your life easier by managing `Workflow`s and `WorkflowActivity`s as Spring beans. |
Member
There was a problem hiding this comment.
Suggested change
| With Dapr Workflows you define complex orchestrations (workflows) in (Java) code. The Dapr Spring Boot Starter makes your life easier by managing `Workflow`s and `WorkflowActivity`s as Spring beans. | |
| With Dapr Workflows you define complex orchestrations (workflows) in Java code. The Dapr Spring Boot Starter makes your development easier by managing `Workflow`s and `WorkflowActivity`s as Spring Beans. |
|
|
||
| With Dapr Workflows you define complex orchestrations (workflows) in (Java) code. The Dapr Spring Boot Starter makes your life easier by managing `Workflow`s and `WorkflowActivity`s as Spring beans. | ||
|
|
||
| In order to enable the automatic bean discovery you can annotate your `@SpringBootApplication` with the `@EnableDaprWorkflows` annotation: |
Member
There was a problem hiding this comment.
Suggested change
| In order to enable the automatic bean discovery you can annotate your `@SpringBootApplication` with the `@EnableDaprWorkflows` annotation: | |
| In order to enable the automatic bean discovery you annotate your `@SpringBootApplication` with the `@EnableDaprWorkflows` annotation: |
| } | ||
| ``` | ||
|
|
||
| By adding this annotation, all the `Workflow`s and `WorkflowActivity`s beans will be automatically discovered by Spring and registered to the workflow engine. |
Member
There was a problem hiding this comment.
Suggested change
| By adding this annotation, all the `Workflow`s and `WorkflowActivity`s beans will be automatically discovered by Spring and registered to the workflow engine. | |
| By adding this annotation, all the `Workflow`s and `WorkflowActivity`s beans are automatically discovered by Spring and registered to the workflow engine. |
|
|
||
| From inside your workflow definitions, you can perform service to service interactions, schedule timers or receive external events. | ||
|
|
||
| By having all `WorkflowActivity`s as managed beans we can use Spring `@Autowired` mechanism to inject any bean that our workflow activity might need to implement its functionality, for example the `@RestTemplate`: |
Member
There was a problem hiding this comment.
Suggested change
| By having all `WorkflowActivity`s as managed beans we can use Spring `@Autowired` mechanism to inject any bean that our workflow activity might need to implement its functionality, for example the `@RestTemplate`: | |
| By having all `WorkflowActivity`s as managed beans you can use the Spring `@Autowired` mechanism to inject any bean that the workflow activity might need to implement its functionality. For example the `@RestTemplate`: |
| ## Creating and interacting with Workflows | ||
|
|
||
|
|
||
| To create and interact with Workflow instances you need to use the `DaprWorkflowClient` that you can also `@Autowired`. |
Member
There was a problem hiding this comment.
Suggested change
| To create and interact with Workflow instances you need to use the `DaprWorkflowClient` that you can also `@Autowired`. | |
| To create and interact with Workflow instances you use the `DaprWorkflowClient` that you can also `@Autowired`. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing some old details and separating workflows with spring boot to it's own page.
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Issue reference