I think this will fix the issue of bad status responses hosing the long term checking, but need to figure out a good way to test
This fix will catch errors associated with the attempt to retrieve or parse the status document. isComplete is true ONLY for a process status of success. Any other valid WPS status keeps isComplete False. We are not happy with the "print" behavior and need to work with implementors for a better solution. The standard "Exception" may not be the most appropriate either, but will work for now.
Just a little final cleanup.
Implemented correct multiplicity for FeatureWeightedGridStatistics. Added test and example coverage.
Implemented another test to catch changes to function input names. A few tweaks to the previous additions as well.
Merge pull request #35 from dblodgett-usgs/master

A workable solution to network glitches and server restart events. Also added the correct multiplicity for featureWeightedGridStats.