-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As an API user, I want to get an XML response #456
Comments
We are still having an issue with xml not serializing the list values in the properties dictionnary. |
Does this also relate to #440? |
@viviant100 @tloubrieu-jpl Hi Thomas, I don't see the changes in jpl-gamma, is the fix in pds-registry-app-1.0.3? |
Hi @gxtchen , Now this component is hosted in the repository https://github.com/NASA-PDS/registry-api . Sorry I missed to tell you that. |
Hi @gxtchen , I updated the registry-api repository so that you have a released package to test with. See the instructions in the main README on https://github.com/NASA-PDS/registry-api Let me know if you have questions. Thanks |
@tloubrieu-jpl after running docker compose --profile=dev-api up command, all processes exited except for docker-elasticsearch-1. I can't load the api then. |
@viviant100 @tloubrieu-jpl |
Motivation
...so that the API can support numerous format responses to support the community.
Details
Note: The content should match the application/json structure
That can be done easily by applying the default springboot content negotiation instead of the custom made content negotiation which returns the original pds4 label.
The pds4 label response could be kept for content-type=application/pds4+xml
Acceptance criteria
Given any API request
When I perform with content-type header 'application/xml'
I expect to get the same attributes and same structure as the same request run with content-type header set to
application/json
The text was updated successfully, but these errors were encountered: