Consider mapping support for primitive typed fields in the application domain objects [DATAGEODE-284]

[spring-projects-issues]

John Blum opened DATAGEODE-284 and commented

If an application domain model class, such as Employee, were defined with primitive typed fields, for example:

 

class Employee {

  private String name;

  private int age;

}

 

It is possible, that when the application domain model class is "evolved" (e.g. when new data fields are added, which Apache Geode PDX handles, i.e. new vs. old domain model class definitions, like adding an age field/property to the Employee class above), then a previously serialized Employee object (with the old class definition not defining age) could result in a NPE when trying to populate a object using the new Employee class definition containing the age field/property.

 

---

Affects: 2.1.14 (Lovelace SR14), 2.2.3 (Moore SR3)