[jira] [Updated] (GEODE-7382) ReflectionBasedAutoSerializer should consider using the greediest application domain object type constructor it can find to satisfy the values of the domain object

["John Blum (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Blum updated GEODE-7382:
-----------------------------
    Summary: ReflectionBasedAutoSerializer should consider using the greediest application domain object type constructor it can find to satisfy the values of the domain object  (was: ReflectionBasedSerializer should consider using the greediest application domain object type constructor it can find to satisfy the values of the domain object)

> ReflectionBasedAutoSerializer should consider using the greediest application domain object type constructor it can find to satisfy the values of the domain object
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-7382
>                 URL: https://issues.apache.org/jira/browse/GEODE-7382
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: John Blum
>            Priority: Major
>
> ... Regardless of whether or not...
> 1. There exists a public, no-arg constructor or NOT (since a default, public, no-arg constructor is not required in Java).
> 2. And whether or not that constructor is public or not (which also does not matter in Java)
> 3. And simply because constructors provide initialization safety that setters and field injection simply cannot as specified by the JVM spec.  
> Also, consider what happens when the object class type is _immutable_.  That is, all object initialization must happen through a constructor since the object is immutable, which are inherently Thread-safe.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)