MachineTags not being saved for Endpoints

13594
Reporter: lfrancke
Type: Bug
Summary: MachineTags not being saved for Endpoints
Description: Probably because nested objects are not saved but there's also no way to add them later.
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2013-08-15 17:37:55.392
Updated: 2013-12-16 17:50:21.095
Resolved: 2013-12-13 12:02:41.45

Attachment Screen Shot 2013-12-13 at 11.15.45 AM.png

Author: kbraak@gbif.org
Created: 2013-12-12 14:29:47.234
Updated: 2013-12-12 14:29:47.234
        
Invalid, since a machineTag can't be saved against an Endpoint, only a NetworkEntity like Dataset or Organization.

Closing issue.
    

Author: lfrancke@gbif.org
Comment: Endpoints are MachineTaggable
Created: 2013-12-12 23:50:59.755
Updated: 2013-12-12 23:50:59.755

Author: kbraak@gbif.org
Created: 2013-12-13 11:22:57.844
Updated: 2013-12-13 11:22:57.844
        
Sorry Lars, a big oversight on my part.

Looking at the Registry's ITs, machine tags now appear to be saved for Endpoints.

The following assertion checks the machine tag for an Endpoint is being persisted correctly: https://code.google.com/p/gbif-registry/source/browse/registry/trunk/registry-ws/src/test/java/org/gbif/registry/EndpointTests.java#43

To sanity check, I attach a screenshot showing the persisted machine tags, while the NodeIT.testEndpoints is paused at the assertion above.

Can you please confirm this issue can be close now? Thanks

    

Author: lfrancke@gbif.org
Comment: Excellent! Thanks for following up Kyle. Looks good then.
Created: 2013-12-13 12:02:34.966
Updated: 2013-12-13 12:02:34.966