As a user, I want to receive a XML response that contains the PDS4 label metadata in XML format (application/vnd.nasa.pds.pds4+xml)

[tloubrieu-jpl]

💪 Motivation

...so that I can get the original label from the API

📖 Additional Details

We need to reimplement the 'application/pds4+xml' MVC implementation on top of the PDS4Product object (instead of previously on top of the default Product object)

⚖️ Acceptance Criteria

Given a valid lidvid in the registry
When I perform curl -X GET http://{base_url}/products/{lidvid} --header Accept: application/pds+xml
Then I expect to get the original PDS4 XML label for the lidvid

When I perform curl -X GET http://{base_url}/products --header Accept: application/pds+xml
Then I expect to get the search result with original PDS4 XML labels

⚙️ Engineering Details

[tloubrieu-jpl]

This ticket is not closed after pull request NASA-PDS/registry-api-service#90

[al-niessner]

@tloubrieu-jpl @jordanpadams

Oh, I think I understand. I turned application/pds4+xml and application/xml back "on" such that they go through the translation mechanisms. They fail for reasons I do not fully understand when building the XML, which is to say the results are retrieved from ES then fails to be remapped to XML. They both seem to fail for similar reasons. Should probably just fix both at the same time. Something about the converter resolution and null type failure:

2021-12-21 21:40:14.328 DEBUG 54 --- [0.3-8080-exec-8] o.s.w.s.m.m.a.HttpEntityMethodProcessor  : Using 'application/pds4+xml', given [application/pds4+xml] and supported [application/pds4+xml, */*]
2021-12-21 21:40:14.328  WARN 54 --- [0.3-8080-exec-8] .w.s.m.s.DefaultHandlerExceptionResolver : Resolved [org.springframework.http.converter.HttpMessageNotWritableException: No converter for [class gov.nasa.pds.model.Pds4Products] with preset Content-Type 'null']
2021-12-21 21:40:14.328 DEBUG 54 --- [0.3-8080-exec-8] o.s.web.servlet.DispatcherServlet        : Completed 500 INTERNAL_SERVER_ERROR

[al-niessner]

@tloubrieu-jpl @jordanpadams

Same process question: with the PR merged, should this ticket still be open?