jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ignasi Barrera <notificati...@github.com>
Subject Re: [jclouds] Added context information for exceptions that are hard to debug (#873)
Date Wed, 28 Oct 2015 13:37:31 GMT
That could explain the failure. I'd say we can completely ignore synthetic fields.

The deserialization strategy just tries to match the number of "names" in the annotation with
the number of parameters in the constructor (or static factory method), to be able to call
it passing the right value to each parameter.

The serialization strategy, when using auto value, assumes that the fields are declared in
the same order than the parameters of the constructor/factory method and the annotation. We
live with this assumption, and it is used to determine, for each field, which value in the
annotation corresponds to it, in order to serialize it under the proper json key. 

This said, since synthetic methods are not in the source code, we should ignore them. I'll
raise a JIRA issue for this and update this PR accordingly.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/873#issuecomment-151846744
Mime
View raw message