[JCLOUDS-1200](https://issues.apache.org/jira/browse/JCLOUDS-1200)
Also marking the corresponding getters as nullable, since they would normally not be null, but could be if the exception were serialized and deserialized. I looked into making the fields actually _be_ serializable, but at least `HttpResponse.payload` would not be serializable, so it did not seem worth the bother. Generally callers either just care about the detail message + stack trace, or are going to be `catch`ing a specific type without serialization intervening. You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/1211 -- Commit Summary -- * [JCLOUDS-1200] Mark nonserializable fields in HttpResponseException and subtypes as transient. -- File Changes -- M apis/atmos/src/main/java/org/jclouds/atmos/AtmosResponseException.java (4) M apis/sts/src/main/java/org/jclouds/aws/AWSResponseException.java (4) M core/src/main/java/org/jclouds/http/HttpResponseException.java (5) M providers/azureblob/src/main/java/org/jclouds/azure/storage/AzureStorageResponseException.java (4) M providers/b2/src/main/java/org/jclouds/b2/B2ResponseException.java (4) M providers/gogrid/src/main/java/org/jclouds/gogrid/GoGridResponseException.java (4) M providers/ultradns-ws/src/main/java/org/jclouds/ultradns/ws/UltraDNSWSResponseException.java (4) -- Patch Links -- https://github.com/jclouds/jclouds/pull/1211.patch https://github.com/jclouds/jclouds/pull/1211.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1211
