Renaud Subiger

The `Prefer` header is defined by openEHR REST API specification: > The Prefer header > > This request header MAY be used by clients for resource representation negotiation. See more...

You are right @ppazos regarding the namespace declaration in the response returned by the server that should normally imply that all elements have to be prefixed by `ns2:`. However, the...

Hi @ppazos, I have added the `package-info.java` with namespace declaration in all sub-packages of `com.nedap.archie`. Unfortunately this change generates JAXBException while unmarshalling in some compositions: ``` javax.xml.bind.UnmarshalException: Unable to create...

@wlad, does Admin API have to support `Prefer` header like the standard openEHR REST API? I just go quickly over the Admin API controllers and none of them is currently...

From "business" perspective, I am not sure that there is an added value for Admin API. But if we manage it, I think we have to address all Admin API...

Dear @flowrider3000 You are right and status code `204 No Content` should definitively be listed in the responses. However, both codes are valid and depend on the `Prefer` header: >...

I closed it by mistake (clicking on the wrong button). I let you close the issue if I answered your question.

Except the workaround proposed by @olzemal, does someone find another alternative? I am having the same issue and trying to find a solution for use case when Helm charts are...

Thanks for the tip @anitakurz 👍 I was trying to migrate an old application that still used an old version of JAXB and custom XJC binding with `generateMixedExtensions="true"` to the...

Regarding the first issue, the current implementation of the FHIR Bridge has a limitation regarding `Bundle` and it expects and supports only 2 types: - DiagnosticReportLab - Blood Gas Panel...