Experimenting a bit with the RESTXQ interface yesterday, using
basexhttp I found that the default web.xml file shipped with BaseX 7.9
has an unfortunate property. The first servlet mapping listed is
RESTXQ
/*
and the last servlet mapping is the default servlet, used for static
dat
Dear Michael,
Yes, RESTXQ is defined on top level in our web.xml file. Files that
are located in the path of the default servlet won't be served by
RESTXQ, but directly by the web server. The two remaining servlet
mappings refer to REST and WebDAV, and both of them don't rely on
RESTXQ either.
I
Michael,
As Christian suggests the web.xml from GraphXQ does date from the old
default basexhttp configuration (~basex 7.8?). Initially I was unconvinced
by the change to what is the current default configuration but I have grown
to appreciate it.
This old configuration gives you a http server wi
On Jan 23, 2015, at 3:27 AM, Andy Bunce wrote:
> Michael,
>
> As Christian suggests the web.xml from GraphXQ does date from the old default
> basexhttp configuration (~basex 7.8?). Initially I was unconvinced by the
> change to what is the current default configuration but I have grown to
> a
Hi Michael,
> Many thanks to both Christian and Andy for their help. If time permits, I
> hope to take up Christian's challenge and contribute some words on
> the web.xml configuration, for use in the documentation.
;) Thanks as well for your observations; it will help me next time
when I revise
> If they aren't written to the BaseX logs, but would be written
> to Jetty logs, then I wonder if it would be helpful to have a
> few hints on turning Jetty logging on (and finding out where
> the log files get written) either in the BaseX documentation
> wiki or in comments in the default jetty.x
6 matches
Mail list logo
