a3cc1384b5
* properly add the dapr runtime returned error details to the Java DaprException Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * add error handling to sdk docs Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * add tests for the dapr exception changes Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * try verifyNoMoreInteractions w/ channel Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * verify channel close -> channel close explicitly Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * rm verifyNoMoreInteractions Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * rm test to see if that is the orphaned managed channel issue Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * re-add test since that doesnt seem to be the issue Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * channel.close(); -> verify(channel).close(); Signed-off-by: Cassandra Coyle <cassie@diagrid.io> * Rewrite and redesign of the DaprErrorDetail in DaprException. Signed-off-by: Artur Souza <asouza.pro@gmail.com> * Update daprdocs too for DaprErrorDetails. Signed-off-by: Artur Souza <asouza.pro@gmail.com> * Fix README.md mm string. Signed-off-by: Artur Souza <asouza.pro@gmail.com> * Fix exception example. Signed-off-by: Artur Souza <asouza.pro@gmail.com> * Use runtime 1.13.0-rc.2 Signed-off-by: Artur Souza <asouza.pro@gmail.com> * Fix exception example to match gRPC output. Signed-off-by: Artur Souza <asouza.pro@gmail.com> * Update error message in IT as per new Dapr runtime version. Signed-off-by: Artur Souza <asouza.pro@gmail.com> * Dapr 1.13 is less tolerant of app downtime to keep timers. Signed-off-by: Artur Souza <asouza.pro@gmail.com> --------- Signed-off-by: Cassandra Coyle <cassie@diagrid.io> Signed-off-by: Artur Souza <asouza.pro@gmail.com> Co-authored-by: Artur Souza <artursouza.ms@outlook.com> Co-authored-by: Artur Souza <asouza.pro@gmail.com> |
||
|---|---|---|
| .. | ||
| content/en | ||
| README.md | ||
README.md
Dapr Java SDK documentation
This page covers how the documentation is structured for the Dapr Java SDK
Dapr Docs
All Dapr documentation is hosted at docs.dapr.io, including the docs for the Java SDK. Head over there if you want to read the docs.
Java SDK docs source
Although the docs site code and content is in the docs repo, the Java SDK content and images are within the content and static directories, respectively.
This allows separation of roles and expertise between maintainers, and makes it easy to find the docs files you are looking for.
Writing Java SDK docs
To get up and running to write Java SDK docs, visit the docs repo to initialize your environment. It will clone both the docs repo and this repo, so you can make changes and see it rendered within the site instantly, as well as commit and PR into this repo.
Make sure to read the docs contributing guide for information on style/semantics/etc.
Docs architecture
The docs site is built on Hugo, which lives in the docs repo. This repo is setup as a git submodule so that when the repo is cloned and initialized, the java-sdk repo, along with the docs, are cloned as well.
Then, in the Hugo configuration file, the daprdocs/content and daprdocs/static directories are redirected to the daprdocs/developing-applications/sdks/java and static/java directories, respectively. Thus, all the content within this repo is folded into the main docs site.