Issue 11011
TechnicalInstallation hostingOrganization not populated
11011
Reporter: kbraak
Type: Bug
Summary: TechnicalInstallation hostingOrganization not populated
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2012-03-20 17:56:07.094
Updated: 2013-12-16 17:50:35.721
Resolved: 2012-03-22 15:41:03.535
Description: For example,
http://staging.gbif.org:8080/registry-ws/technical_installation/1ea68ce2-6ea2-11e1-a453-a4093f22ed41
In the registry db, the relation organization has_installation technical installation is saved properly.
When converting the technical installation (persistence) to a technical installation (Registry API) this fields isn't being properly populated.
Please check persistence and service layers.]]>
Author: kbraak@gbif.org
Comment: Persistence layer working provided the correct type for technical installation is used for the agent: http://code.google.com/p/gbif-registry/source/detail?r=2577
Created: 2012-03-21 12:22:51.01
Updated: 2012-03-21 12:22:51.01
Author: kbraak@gbif.org
Created: 2012-03-21 17:17:42.401
Updated: 2012-03-21 17:17:42.401
The API TechnicalInstallation and WritableTechnicalInstallation are now as they should be. Among the changes I had to make, was the addition of the TechnicalInstallationType field to WritableTechnicalInstallation to be able to distinguish its type, ie IPT_INSTALLATION.
Next, I need to ensure that the WS response for TechnicalInstallations in fact contains the hosting organization and the type.