Uploaded image for project: 'Webservices REST Module'
  1. Webservices REST Module
  2. RESTWS-564

Submitting PersonAttribute Value UUIDs Does not Work Correctly For Attributable values

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Could
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.15
    • Labels:
      None
    • Complexity:
      Low

      Description

      Context
      This should have been fixed as indicated in the linked tickets, nevertheless it does not seem to be the case. When submitting Location value as uuid using the "value" attribute, the value goes in as is, that is no transformation to corresponding internal ID is performed. However converting to internal IDs can be achieved using the attribute "hydratedObject" instead.

      Darius Jazayeri [X] when you suggested "The other option is to leave the "value" property as-is, and expose a "hydratedValue" property, which is settable and gettable" in one of the comments in RESTWS-389 did you mean you expected users to pass the field "hydratedValue" in the payload or you just meant the magic to figure that out should happen in the background?

      Personally I don't think users should deal with the business of figuring out whether they should use "hydratedValue" or "value" when dealing with Attributables so I suggest to check wether the expected value is Attributable in a @PropertySetter and if it is, then assume the passed value is a UUID of the corresponding domain object. Besides I imagine the REST API is designed to work with uuids wherever possible.

      I would like to hear other's ideas on this before proceeding with the approach I suggest.

      Definition of Done
      Being able to use uuids as values for Attributable value in Person Attributes.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              willa Willa Mhawila [X] (Inactive)
              Reporter:
              willa Willa Mhawila [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: