| Table of Contents |
|---|
...
(2) use PLFM/trunk/tools/tcgaWorkflow/pom.xml as the example for your pom. You'll want to copy the <dependencies>, <properties>, and <build> sections. There's a lot of java magic wrapped up in that pom.
(3) sanity check your new package, every SageBio workflow has the Hello World workflow embedded in it. Make sure you can run it from your new package:
(4) if the Java package for the workflow code is not already listed in PLFM/trunk/lib/lib-workflow/src/main/resources/META-INF/aop.xml add it there
(45) write your code, at a minimum you will likely want code similar to the following TODO ADD LINKS AFTER THE MERGE TO TRUNK
- workflow interface:
- activity interface:
- workflow implementation:
- activity implementation:
- workflow runner (runs the decider):
- activity runner (runs the activities):
- workflow initiator (kicks off workflows): note that this particular example is rather complicated, an initiator could just kick off a single workflow instance
- workflow configuration utility:
- workflow configuration properties:
- workflow configuration properties template:
- workflow test (important this will help you ensure that your Promise variables are configured correctly):
| Include Page | ||||
|---|---|---|---|---|
|
...
This can happen when the activity or workflow code throws a runtime exception such as a NullPointerException. Unfortunately the unit testing framework provided by SWF does not log them.
"java.lang.IllegalStateException",{"cause":null,"message":"not ready","localizedMessage":"not ready"
Promise Variables were used Incorrectly
...