Commit a2d8ecb
authored
invokeAPI check against Family.SUCCESSFUL
I changed the the check against Family.SUCCESSFUL to catch all 2xx HTTP codes, the 201 Created, too.
According to DocuSign API it should be sufficient to detect successful cases.
Why I throw this exception to indicate a bad server response:
If we exit the method at line 757 or 760 with "return null;" we can not react on upper level in our application side based on HTTP code.
No indication is possible what's going wrong in that api call.
If this is not what you asked, please give me a hint ;-)1 parent 5b22d14 commit a2d8ecb
1 file changed
+2
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
22 | 22 | | |
23 | 23 | | |
24 | 24 | | |
25 | | - | |
26 | 25 | | |
27 | 26 | | |
28 | 27 | | |
| |||
747 | 746 | | |
748 | 747 | | |
749 | 748 | | |
750 | | - | |
751 | | - | |
| 749 | + | |
| 750 | + | |
752 | 751 | | |
753 | 752 | | |
754 | 753 | | |
| |||
0 commit comments