Probably rewrite workflow example for better understanding

[kaibocai]

Describe the proposal

I am reading the workflow example and find it a little bit messy due to combining all APIs in a single workflow example. I was wondering should we separate the single huge workflow into several examples, each giving a more concrete example of a set of APIs. This may help user to better understand it.

Also continueAsNew API has a break change with the release here https://github.com/microsoft/durabletask-java/releases/tag/1.2.0. It will not continue executing logic after it (an exception is thrown out in the durabletask SDK to force yield control back to the sidecar). So example here

java-sdk/examples/src/main/java/io/dapr/examples/workflows/DemoWorkflow.java

Lines 109 to 121 in 0d0d599

	if (shouldComplete) {
	ctx.getLogger().info("Child-Workflow> Calling ChildWorkflow...");
	var childWorkflowInput = "Hello ChildWorkflow!";
	var childWorkflowOutput =
	ctx.callSubWorkflow(DemoSubWorkflow.class.getName(), childWorkflowInput, String.class).await();
	ctx.getLogger().info("Child-Workflow> returned: " + childWorkflowOutput);
	ctx.getLogger().info("Workflow finished");
	ctx.complete("finished");
	return;
	}

will never be triggered once upgrade durabletask-java to v1.2.0.

[rabollin]

Related Issue: #911

[cicoyle]

I think that would be a valuable change - breaking up and making each example more explicit and complete. Is this something you would be able to and want to work on?

[kaibocai]

Yeah, definitely. I can work on improving the workflow example.