News for hackers. Stuff that matters.
Re:AWS Java documentation is fucked by codeonfire on Friday February 12, 2016 @11:09PM (#11092491)
SWF is a developer tar baby. Don't touch. It's incredibly complex for what little it does. At the service side, a simple queue server would replace it. Everything about the 'workflow' is implemented on the client using whatever latest java abomination like AOP backed annotations.
Re:AWS Java documentation is fucked by AReallyGoodName on Friday February 12, 2016 @11:16PM (#11092517)
Author here. I thought that too at first. It's actually straightforward though. I now have a video transcoding workflow that works well.

It's not SWF that's the problem. It's actually really straightforward to use. AOP is not required, annotations are not required and those design patterns are not required. It's just the really messed up documentation that makes you think this.

Check the bottom of the above article. You just take the C# sample and copy and paste it onto Java. Change the syntax to Java. It gets a bit more verbose but is still trivial to grok.

Re:AWS Java documentation is fucked by optimusclimb on Saturday February 13, 2016 @03:22AM (#11093217)
Did you contact support or email someone responsible for SWF in some way, or just write the blog post?
Re:AWS Java documentation is fucked by AReallyGoodName on Saturday February 13, 2016 @03:35AM (#11093256)
jcrites from Amazon has responded above in this thread which is nice.