You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2015/10/28 14:42:27 UTC

[jira] [Created] (JCLOUDS-1030) Ignore synthetic members in serialization strategies

Ignasi Barrera created JCLOUDS-1030:
---------------------------------------

             Summary: Ignore synthetic members in serialization strategies
                 Key: JCLOUDS-1030
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1030
             Project: jclouds
          Issue Type: Bug
          Components: jclouds-core
    Affects Versions: 1.9.1
            Reporter: Ignasi Barrera


jclouds relies on the consistency between the number of fields in a class, their order, and the parameters in the constructors and factory methods. This  is specially relevant when using reflection with classes auto-generated by Google Auto.

Libraries that instrument the classes may introduce conflicts with this assumptions. For example, JaCoCo adds two members to the classes: A private static field $jacocoData and a private static method $jacocoInit(). Both members are marked as synthetic.

The jclouds serialization strategies that use reflection, should ignore all synthetic members, as they won't be part of the source code and never expected to be used to map the fields with the serialized values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)