Hi Omar, hi Emmanuel,
BaseX 9 will provide support for server-side quality factors [1,2]:
With these extensions, it will eventually be possible to handle cases
in which a client provides no content types, and in which multiple
RESTXQ conflicting functions exist for that request.
Hope this helps,
I thought it could be done with it, but I didn’t managed with it. It’s because
I didn’t figure out the parameter bring back the whole string and not only the
matching part of the regex.
Thanks for your message because I tried again, and it works very fine.
Marvelous !
I’ll try to give a workin
Hi Emmanuel,
Thanks for you mail. Indeed I believe that the path extensions are already
covered by the regex syntax [1]; did you already try it out?
Cheers,
Christian
[1] http://docs.basex.org/wiki/RESTXQ#Paths
Am 09.07.2017 17:23 schrieb "Emmanuel Chateau" :
Hallo Christian,
As you know I’
Hallo Christian,
As you know I’m really interested by this issue.
On this topic, I was wondering if it could be possible to implement something
to deal with path extensions in RESTXQ.
It would then be possible to perform later transparent content negotiation in
the function.
For exemple :
```
Hi Omar,
> Thanks for the answer. There is one thing I want to point out: My problem is
> not the quality measure. I have problems because my client lacks them.
Right, that’s what I understood. If quality factors are given, a
function should be chosen, but in your case,
BaseX doesn’t seem to be a
Hi Christian,
Thanks for the answer. There is one thing I want to point out: My
problem is not the quality measure. I have problems because my client
lacks them. It sends 'application/xml,*/*' which is interpreted as: any
function that either satisfies application/xml or any other mime type.
Hi Omar,
Thanks for the reminder. Yes, we still plan to improve support for
quality factors in our RESTXQ implementation. We’ll probably need to
find out how this has been resolved in JAX-RS, and define an
equivalent solution for RESTXQ. I have updated the initial comment in
Issue 1220 [1].
I am
Hi list!
I like my oXygen editor to request raw XML data from my RESTxq endpoints
to test XSL stylesheets. When I do this with RESTxq paths that have
different %rest:produces it fails with the BASX0003 multiple functions
error.
Turns out oXygen sends application/xml, */* as Accept header wit
8 matches
Mail list logo
