Skip to content

docs: fix broken links #1663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dapr-bot merged 1 commit into from
Feb 17, 2026
+7 −7
Merged

docs: fix broken links #1663

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions spring-boot-4-examples/workflows/multi-app/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ You can create new workflow instances of the `CustomerWorkflow` by calling the `
curl -X POST localhost:8080/customers -H 'Content-Type: application/json' -d '{ "customerName": "salaboy" }'
```

The workflow definition [`CustomerWorkflow`](orchstrator/src/main/java/io/dapr/springboot/examples/orchestrator/CustomerWorkflow.java) that you can find inside the `orchestrator` app,
The workflow definition [`CustomerWorkflow`](orchestrator/src/main/java/io/dapr/springboot4/examples/orchestrator/CustomerWorkflow.java) that you can find inside the `orchestrator` app,
performs the following orchestration when a new workflow instance is created:

- Call the `RegisterCustomerActivity` activity which can be found inside the `worker-one` application.
Expand Down Expand Up @@ -83,9 +83,9 @@ performs the following orchestration when a new workflow instance is created:
Testing becomes a complex task when you are dealing with multiple Spring Boot applications. For testing this workflow,
we rely on [Testcontainers](https://testcontainers.com) to create the entire setup which enable us to run the workflow end to end.

You can find the end-to-end test in the [`OrchestratorAppIT.java`](orchestrator/src/test/java/io/dapr/springboot/examples/orchestrator/OrchestratorAppIT.java) class inside the `orchestrator` application.
You can find the end-to-end test in the [`OrchestratorAppIT.java`](orchestrator/src/test/java/io/dapr/springboot4/examples/orchestrator/OrchestratorAppIT.java) class inside the `orchestrator` application.
This test interact with the application REST endpoints to validate their correct execution.

But the magic behind the test can be located in the [`DaprTestContainersConfig.class`](orchestrator/src/test/java/io/dapr/springboot/examples/orchestrator/DaprTestContainersConfig.java) which defines the configuration for
But the magic behind the test can be located in the [`DaprTestContainersConfig.class`](orchestrator/src/test/java/io/dapr/springboot4/examples/orchestrator/DaprTestContainersConfig.java) which defines the configuration for
all the Dapr containers and the `worker-one` and `worker-two` applications. Check this class to gain a deeper understand how to configure
multiple Dapr-enabled applications.
4 changes: 2 additions & 2 deletions spring-boot-4-examples/workflows/patterns/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ timeout_seconds: 180

<!-- END_STEP -->

By running the `spring-boot:test-run` goal, the application is loaded using the [test configurations](src/test/java/io/dapr/springboot/examples/wfp/DaprTestContainersConfig.java)
By running the `spring-boot:test-run` goal, the application is loaded using the [test configurations](src/test/java/io/dapr/springboot4/examples/wfp/DaprTestContainersConfig.java)
configured using [Testcontainers](https://testcontainers.com) to boostrap the [Dapr](https://dapr.io) sidecar and control plane.

Once the application is running you can trigger the different patterns by sending the following requests:
Expand Down Expand Up @@ -509,4 +509,4 @@ i.d.s.e.w.s.PerformTaskActivity : Completing activity...
## Testing workflow executions

Workflow execution can be tested using Testcontainers and you can find all the tests for the patterns covered in this
application [here](test/java/io/dapr/springboot/examples/wfp/TestWorkflowPatternsApplication.java).
application [here](src/test/java/io/dapr/springboot4/examples/wfp/TestWorkflowPatternsApplication.java).
2 changes: 1 addition & 1 deletion spring-boot-examples/workflows/multi-app/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ You can create new workflow instances of the `CustomerWorkflow` by calling the `
curl -X POST localhost:8080/customers -H 'Content-Type: application/json' -d '{ "customerName": "salaboy" }'
```

The workflow definition [`CustomerWorkflow`](orchstrator/src/main/java/io/dapr/springboot/examples/orchestrator/CustomerWorkflow.java) that you can find inside the `orchestrator` app,
The workflow definition [`CustomerWorkflow`](orchestrator/src/main/java/io/dapr/springboot/examples/orchestrator/CustomerWorkflow.java) that you can find inside the `orchestrator` app,
performs the following orchestration when a new workflow instance is created:

- Call the `RegisterCustomerActivity` activity which can be found inside the `worker-one` application.
Expand Down
2 changes: 1 addition & 1 deletion spring-boot-examples/workflows/patterns/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -509,4 +509,4 @@ i.d.s.e.w.s.PerformTaskActivity : Completing activity...
## Testing workflow executions

Workflow execution can be tested using Testcontainers and you can find all the tests for the patterns covered in this
application [here](test/java/io/dapr/springboot/examples/wfp/TestWorkflowPatternsApplication.java).
application [here](src/test/java/io/dapr/springboot/examples/wfp/TestWorkflowPatternsApplication.java).
Loading