Feature flags examples

Author: demirkayaender

src/main/java/com/uber/cadence/samples/hello/HelloSignal.java

@@ -19,6 +19,7 @@
 
 import static com.uber.cadence.samples.common.SampleConstants.DOMAIN;
 
+import com.uber.cadence.FeatureFlags;
 import com.uber.cadence.client.WorkflowClient;
 import com.uber.cadence.client.WorkflowClientOptions;
 import com.uber.cadence.client.WorkflowOptions;
@@ -97,7 +98,11 @@ public static void main(String[] args) throws Exception {
     // ClientOptions.newBuilder().setRpcTimeout(5 * 1000).build();
     WorkflowClient workflowClient =
         WorkflowClient.newInstance(
-            new WorkflowServiceTChannel(ClientOptions.defaultInstance()),
+            new WorkflowServiceTChannel(
+                ClientOptions.newBuilder()
+                    .setFeatureFlags(
+                        new FeatureFlags().setWorkflowExecutionAlreadyCompletedErrorEnabled(true))
+                    .build()),
             WorkflowClientOptions.newBuilder().setDomain(DOMAIN).build());
     // Get worker to poll the task list.
     WorkerFactory factory = WorkerFactory.newInstance(workflowClient);

src/main/java/com/uber/cadence/samples/hello/HelloSignalAndResponse.java

@@ -50,9 +50,9 @@
 import org.apache.commons.lang.RandomStringUtils;
 
 /**
- * Demonstrates signalling a workflow, and wait until it's applied and get a
- * response. This should be much performant(lower latency) than using signal+query approach.
- * Requires a Cadence server to be running.
+ * Demonstrates signalling a workflow, and wait until it's applied and get a response. This should
+ * be much performant(lower latency) than using signal+query approach. Requires a Cadence server to
+ * be running.
  */
 @SuppressWarnings("ALL")
 public class HelloSignalAndResponse {