Independently on how I hard I try, I'm not able to recreate the problem.
It happened twice in two following days but now it's no t happening
again ...
I've seen that the mail reporting the same exception:
https://mailman.uni-konstanz.de/pipermail/basex-talk/2013-February/004690.html
has been
Hi Marco,
thanks for trying. – It’s difficult to guess how the exception was
caused in your scenario. The stack trace reported by Arto was caused
by a bug in the implementation of xquery:eval() [1], while your stack
trace seems to point to the replace command.
If you manage to reproduce the
On Tue, 2013-02-26 at 18:13 +0100, Ludovic Kuty wrote:
Did you try a netstat -nltp as root under Linux to see if something
is listening on the port ?
or (as root) lsof -i TCP:8984
which will list the process, if any.
Also make sure that you're contacting the right host :) BaseX has a
habit of
Hi,
I have this bit of RestXQ:
declare %restxq:path(test/{$id}.html)
%output:method(xhtml)
%output:omit-xml-declaration(no)
%output:doctype-public(-//W3C//DTD XHTML 1.0 Transitional//EN)
Dear Wendell,
declare %restxq:path(test/{$id}.html)
the RESTXQ spec. requires path segments to be either a string (such as
test) or a template (such as {$id}) [1]. If you require the .html
suffix, you’ll have to remove it from the assigned variable within
your XQuery code:
declare
Hi Francis,
there’s no official way to check the availability of the feature, so I
would suggest to update everything to the latest version. However, all
my changes are backward-compatibe, so you shouldn’t encounter any
surprises when you don’t use repeated bindings and query executions.
Christian,
Ah, how ... non-obvious. Path segment. :- (Expecting more flexible
string-matching behavior, a la Cocoon sitemaps, I guess I didn't even
notice the language saying it wasn't.)
Thanks! I guess I can live with a little working around, if it makes
life easier for others.
Cheers, Wendell
Hi Wendell,
in our use case, we never work with file extensions in the URI, so we
didn’t actually felt that this could be a restriction. Still, I agree
that a more powerful path matcher could add flexibility. RESTXQ is
still pretty young, so just wait and see how the standard evolves.
Best,
8 matches
Mail list logo
