Uploaded image for project: 'Nuxeo Java Client'
  1. Nuxeo Java Client
  2. JAVACLIENT-122

Update Automation call responses management

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.5
    • Component/s: REST

      Description

      entity-type

      nuxeo-java-client handle already those two scenarii for Automation call responses management:

      • When entity-type is declared in the json payload but not in the header - handled already for the RecordSet Object (legacy)
      • When entity-type is declared in the header but not in the json payload - handled already for both Document and Documents

      Finally, It should at last handle this missing one:

      • When no entity-type is declared either in the header or in the json payload:

      A typical scenario is for Automation only when calling operations returning a json blob built manually. See for instance Directory.Entries operation

      Business Objects

      As nuxeo-java-client is not implementing Business Object (past architecture choice), it should handle a way to unmarshall very easily a json blob coming for the server side:

      • Add utils for reading easily all type of structure
      • Add logger for debugging json payload request or response

      -> Ticket for documentation: NXDOC-1118

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: