I'm trying to define a call to an http service but orbeon doesn't understand the returned media type.
Our REST service returns a content type of
Content-Type=application/vnd.infomedix+json;v="33"
unless we supply an Accept header value to ask for something else, so we could say
Accept=application/vnd.infomedix+xml;v="33"
or even
Accept=text/xml
in the request headers to get xml. This call will return a content type header with the same media string as was passed in. This is all done so we can have control over our formats and versions of our REST interface.
Both of the above are specifying that the underlying structure is "json" or "xml" respectively.
When the type is the json variant I would expect that orbeon would recognise this as json and convert it into the appropriate xml model in the instance but this is not happening, instead I get an error
2017-01-27 16:32:50,981 72373259 ERROR [ajp-0.0.0.0-8209-2] processor.XFormsServer - xforms-submit-error - Mediatype is neither text nor XML for replace="text": application/vnd.infomedix+json
2017-01-27 16:32:50,987 72373265 ERROR [ajp-0.0.0.0-8209-2] processor.XFormsServer - xforms-submit-done|error - setting body document {body: "
{
"patientNs" : "IHN",
"dob" : "19801012",
...
"firstName" : "Emily",
"lastName" : "YOUNG",
}"}
I could use the xml variant if I could supply an Accept header to the HTTP service definition but there doesn't seem to be a way to do that.
So,
1) Is there a way to populate the Accept header? If not is it possible to get that added to the service definition?
2) I think the error (above) is a bug, the content type of application/vnd.infomedix+json is a valid json type and should be accepted and converted into the xml model instance.
thanks.
Locked
