BaseX-Talk

basex-talk@mailman.uni-konstanz.de

4 participants
5268 discussions

Known issue? DB file names with capital letters get corrupted on OS switch.
by France Baril 17 Mar '19

17 Mar '19

Hi, I recently moved from Mac to Linux and noticed that when using the webDAV connection, all files that have capital letters in their name become corrupted when open in Linux. Luckily, out of the thousands of files that we have, less than 2 dozens used capitalization. I still think this could become a large issue for someone someday, so I felt I should report it. -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com

2 2

supporting XML Catalog files in xslt:transform() (patch)
by Liam R. E. Quin 14 Mar '19

14 Mar '19

The enclosed patch -- would you prefer a github pull request? -- makes xslt:transform() aware of XML catalog files, as other XML parsing already is. The same CATFILE preference is used (via the query context). I refactored CatalogWrapper slightly so it could be reused. I also took away the line that sets verbosity to 0, as without it you can control verbosity via a system property, or using the CatalogManager.properties file. I tested this with xml-commons-resolver-1.2/resolver.jar and with the built-in resolver and both seem to work. I have not added tests. In addition, it'd be worth adding something to the documentation, especially about the xml.catalog.verbosity property (just verbosity in the .properties file). Possible breaking change: i also removed the line that sets prefer=public. I spent ages trying to get catalogs working before i dicovered this, as i was using a system identifier! The code could check to see if the corresponding system property is set (users can't override the API with system properties, frustratingly), but since catalogs already say prefer=public or prefer=system in them, and it'd have needed to have been the same to work, i don't think this change breaks anythign in practice. It may make some catalogs start to work that had not been working, so maybe it's worth a line in the release notes. Liam -- Liam Quin, https://www.delightfulcomputing.com/ Available for XML/Document/Information Architecture/XSLT/ XSL/XQuery/Web/Text Processing/A11Y training, work & consulting. Web slave for vintage clipart http://www.fromoldbooks.org/

4 13

Regex j-flag
by Andreas Hartmann 13 Mar '19

13 Mar '19

Hi The "j" flag for regular expressions introduced in version 9.1 doesn't seem to work in 9.1.2 anymore. For example, matches("Fenster", "\bfenst", "ij") produces [FORX0001] invalid regular flag 'j'. The same expression works in 9.1.1. Best Greetings, Andreas

2 1

Write functions in sequence
by Giuseppe G. A. Celano 12 Mar '19

12 Mar '19

Hi I wrote a single script which should do: write a file -> open this file -> write another different file. I put the write expressions in the right sequence, but it seems that the second one cannot happen because the file created by the first write function has not yet been created at the time the second function is invoked. Does anyone have a suggestion about this? Thanks. Best, Giuseppe

3 7

Serialization issue with HTTP response
by Marco Lettere 08 Mar '19

08 Mar '19

Hi all, we have to deal with a third-party REST service which in case of error conditions returns this mime type: /*application/problem+json; charset=utf-8*/. I wrote this RestXQ [1] to mock it. Just copy it into restxq.xqm... When I call it like [2] I get /*[XPTY0004] Cannot convert xs:base64Binary to xs:string: "IntcImFcIjpcImJcIn0i"*/. This is because the response is seen as a binary and this can be double checked calling with [3]. I felt (maybe wrongly) that specializations of the mimetype had been faced in BaseX implementation of http:request somewhere back in time but I couldn't find anything in the mail archives. The strange thing however is that I get the same error when calling like [4] with override-mime-type set to text/json or application/json which instead I was expecting to work. Is the behaviour in this scenario expected or does this hide some inconsistency? Thanks, as usual, for the support. Regards, Marco. [1] declare%rest:path("mc/dummy") %rest:GET %output:method("json") function page:dummy() { <rest:response> <http:response status="400"> <http:header name="Content-Type" value="application/problem+json; charset=utf-8"/> </http:response> </rest:response>, '{"a":"b"}' }; [2] json:parse( http:send-request(<http:request method="get"/>,"http://localhost:8984/mc/dummy")[2] ) [3] json:parse( convert:binary-to-string( http:send-request(<http:request method="get"/>,"http://localhost:8984/mc/dummy")[2] ) ) [4] json:parse( http:send-request(<http:request method="get" override-media-type="application/json"/>,"http://localhost:8984/mc/dummy")[2] )

2 5

Using HTTP Digest Authentication in a RESTXQ services
by Omar Siam 04 Mar '19

04 Mar '19

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 endpoint. I don't seem to get that to work. Any suggestions? Best regards Omar Siam

2 5

RESTXQ and regexp
by Marco Lettere 04 Mar '19

04 Mar '19

Hello all, according to the docs this should be possible: (: Matches all paths with "app" as first, a number as second, and "order" as third segment :) declare %rest:path("app/{$code=[0-9]+}/order") function page:order($full-path) { ... }; (: Matches all other all paths starting with "app/" :) declare %rest:path("app/{$path=.+}") function page:others($path) { ... }; And it actually is... We are currently in the very unfortunate situation where we need the following: (: Matches anything followed by /input :) declare %rest:path("app/{$path=.+}/input") function page:inputs($path) { ... }; (: Matches all other all paths starting with "app/" :) declare %rest:path("app/{$path=.+}") function page:others($path) { ... }; Unfortunately this makes all the calls to be redirected to the page:others function ... is there a motivation behind it or could it be possible to work around that? Thanks, Marco.

3 3

If clause
by Giuseppe G. A. Celano 04 Mar '19

04 Mar '19

Hi, I see that in BaseX 9.1.2 an expression such as "if (3) then 4 " does not raise an error, even if the "else" part is missing. Is this correct? Ciao, Giuseppe

7 13

Class 'BaseXHTTP' missing?
by Jan Stapel 28 Feb '19

28 Feb '19

Hello, i just tried to run the Java REST-Examples found on GIT/the basex-doc. BaseXHTTP cannot be resolved to a type. I am using the current version. Am I missing something? best, Jan

2 1

Activating gzip compression
by Omar Siam 27 Feb '19

27 Feb '19

Hi, I tried both ways of enabling gzip compression for JSON and js (and others). I can't see it actually working. The GzipFilter method from the web.xml sample seems to be deprecated with a warning of "it is bug ridden" ... But then in a browser debugger I cannot see it actually zipping anything. I trief to enable this in my BaseX 9.1.2 instance using <filter> <filter-name>GzipFilter</filter-name> <filter-class>org.eclipse.jetty.servlets.GzipFilter</filter-class> <init-param> <param-name>mimeTypes</param-name> <param-value>text/html,text/xml,text/ecmascript,application/xhtml+xml,application/json,application/javascript,image/svg+xml</param-value> </init-param> </filter> <filter-mapping> <filter-name>GzipFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> The GzipHandler method seems to get loaded but then also in a browser debugger I cannot see it actually zipping anything. For the GzipHandler the documentation https://www.eclipse.org/jetty/documentation/current/gzip-filter.html talks about when it actually gets invoked and mentions: * No content-encoding is specified by the resource I found no way to not specify an encoding for whatever I return in RESTXQ. If I don't specify anything it's UTF-8. it shows up as "; character-set=UTF-8"I did not find a way to specify no encoding. Maybe unrelated but perhaps that is a problem. I modified webapp/WEB-INF/jetty.xml like this so it uses the GzipHandler (copied from the current jetty distribution): <Configure id="Server" class="org.eclipse.jetty.server.Server">  <Call name="addConnector"> ... </Call> <Call name="insertHandler"> <Arg> <New id="GzipHandler" class="org.eclipse.jetty.server.handler.gzip.GzipHandler"> <Set name="minGzipSize"><Property name="jetty.gzip.minGzipSize" deprecated="gzip.minGzipSize" default="2048"/></Set> <Set name="checkGzExists"><Property name="jetty.gzip.checkGzExists" deprecated="gzip.checkGzExists" default="false"/></Set> <Set name="compressionLevel"><Property name="jetty.gzip.compressionLevel" deprecated="gzip.compressionLevel" default="-1"/></Set> <Set name="inflateBufferSize"><Property name="jetty.gzip.inflateBufferSize" default="0"/></Set> <Set name="deflaterPoolCapacity"><Property name="jetty.gzip.deflaterPoolCapacity" default="-1"/></Set> <Set name="syncFlush"><Property name="jetty.gzip.syncFlush" default="false" /></Set> <Set name="excludedAgentPatterns"> <Array type="String"> <Item><Property name="jetty.gzip.excludedUserAgent" deprecated="gzip.excludedUserAgent" default=".*MSIE.6\.0.*"/></Item> </Array> </Set> <Set name="includedMethodList"><Property name="jetty.gzip.includedMethodList" default="GET" /></Set> <Set name="excludedMethodList"><Property name="jetty.gzip.excludedMethodList" default="" /></Set> </New> </Arg> </Call> </Configure> I hope there is a way to get this to work. Best regards Omar Siam

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk