Re: [basex-talk] Nullpointer exception using http:send-mail with authentication details, no send-authorization attribute

Hi Markus, thanks for your bug report, which summarizes exactly how the attribute is supposed to work. The bug has been encountered just recently; it is fixed in the latest stable snapshot. Best, Christian On Fri, Feb 15, 2019 at 2:57 AM Markus Wittenberg wrote: > > Hi there, > > I get a

[basex-talk] Nullpointer exception using http:send-mail with authentication details, no send-authorization attribute

 Hi there, I get a Nullpointer exception (see below) using the http:send-mail method with authentication details (Basic Auth), but without the send-authorization attribute in the http:request element. According to the EXPath HTTP Client Module spec

Re: [basex-talk] Using HTTP Digest Authentication in a RESTXQ services

Hi Omar, Digest authentication with RESTXQ should work out of the box. The following changes in the configuration may be required: • You’ll need to enable digest authentication in the web.xml configuration file [1] • By default, the admin user is enabled for RESTXQ requests. You’ll need to

[basex-talk] Using HTTP Digest Authentication in a RESTXQ services

Hi list! I just experimented a bit to see if there is an obvious way to use HTTP digest authentication for some RESTXQ service I plan to write. I would prefer not to reimplement the HTTP digest logic in XQuery. I thought maybe there is a way to use the built in digest logic like for the REST

Re: [basex-talk] Schema 1.1 validation and Xerces cta-full-xpath-checking?

> you may consider adding it explicitly to the Wiki example: Contributions to our Wiki are welcome ;)

Re: [basex-talk] Schema 1.1 validation and Xerces cta-full-xpath-checking?

This is FUN indeed. Thanks Christian! Since I consider it a central feature when using Xerces 1.1 validation (it is one out of four controlled Xerces validation features in Oxygen options, too), you may consider adding it explicitly to the Wiki example: validate:xsd($doc,$schema,map {

Re: [basex-talk] proc:execute

Hi Christian, The problem with Mac is that it is not that easy to chance root settings. However, I have found a workaround, which may be useful to others: instead of invoking something like proc:system("python", "main.py"), I create a bash file like: #!/bin/bash export LC_ALL=en_US.UTF-8

Re: [basex-talk] Global locks

Hi Andy, > Is it required to specify all databases accessed within the manualock scope > or could it work just specifying specific databases as readonly? > And the execution would error if these were violated. Sounds good. I have opened a new issue [1]; we welcome further syntax proposals.

Re: [basex-talk] Schema 1.1 validation and Xerces cta-full-xpath-checking?

Hi Daniel, hi George, With the latest snapshot of BaseX, XSD validation features can now be specified [1,2]. In addition to that, • I have removed the version argument. The most recent supported version XML Schema will now be used by default. • Two additional functions can be used to retrieve

Re: [basex-talk] Global locks

I look forward to the longer term solution :) But in the meantime these pragmas, although not pretty, would allow solutions to specific multitasking performance issues to be explored where currently they can be difficult/impossible. I think there is a certain elegance in advisory nature of

Re: [basex-talk] Docker Volumes Permission denied

Hi Marie, thanks for your observations! The explanation for this behavior is, that the `basexhttp` Process inside the container runs as non-privileged user `basex` with an UID of 1984 & GID 0. Usually processes inside docker containers will run as root and as such will be able to read & write