Support constructor based serialization

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Codecs
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Rather than instantiating an empty instance via a no-arg constructor, allow for the construction of entities via constructor that takes values for the fields. Questions to answer:

      1. Should all the fields be required in the constructor?
        • If no, should the remaining fields be set via field injection?
      2. Should the constructor parameter names be forced to match field names so we can order them properly when invoking?
        • Should we rely on document order instead?
        • Should we allow for explicitly mapping constructor parameters to fields via annotations on those parameters?

            Assignee:
            Ross Lawley
            Reporter:
            Justin Lee
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: