Hi Fabrice,
I guess it would be better to use RESTXQ for building responses that match the JSON API specification. Did you try that already?
Cheers Christian
Am 09.06.2017 15:11 schrieb "Fabrice ETANCHAUD" <fetanchaud@pch.cerfrance.fr
:
Hi all,
Dear Christian, I hope you are doing well.
On the same subject, would it be possible for the REST interface to handle PUT requests of
application/vnd.api+json http://www.iana.org/assignments/media-types/application/vnd.api+json
resources (http://jsonapi.org/) like JSON ones ?
Best regards,
Fabrice
*De :* basex-talk-bounces@mailman.uni-konstanz.de [mailto: basex-talk-bounces@mailman.uni-konstanz.de] *De la part de* Andy Bunce *Envoyé :* vendredi 9 juin 2017 12:38 *À :* Christian Grün *Cc :* basex-talk@mailman.uni-konstanz.de *Objet :* Re: [basex-talk] fetch:content-type file: customisation
Hi Christian,
Just these two I am thinking about at the moment.
Is there some reason not to go with "application/*xproc*+xml"? [1] Many in the existing list are in this style e.g. atom=application/atom+xml svg=image/svg+xml
lostxml=application/lost+xml
And it looks like BaseX will treat it as XML [2]
/Andy [1] https://www.w3.org/XML/XProc/docs/langspec.html#media-type-registration [2] https://github.com/BaseXdb/basex/blob/master/basex-core/ src/main/java/org/basex/util/http/MediaType.java#L148
On 9 June 2017 at 11:01, Christian Grün christian.gruen@gmail.com wrote:
Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce bunce.andy@gmail.com wrote:
Hi,
I notice that fetch:content-type()[1] returns "application/octet-stream"
for
files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as "application/xproc+xml" or add a mechanism to allow extension/customisation? Maybe similar to [3] For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2] https://github.com/BaseXdb/basex/blob/master/basex-core/
src/main/resources/media-types.properties
[3] http://docs.oracle.com/javase/7/docs/api/javax/activation/
MimetypesFileTypeMap.html
set-mime-mapping-to-a-file-served-as-static-content-by- jetty-runner/33809187#33809187