Re: [basex-talk] Losing some space entities

When I serialize these from a restxq to file with file:write I get the as and as but I get none of the other entities. On Wed, Jan 18, 2017 at 6:59 PM, France Baril wrote: > Import works, playing with webdav is giving good results so far. I still > want to see

Re: [basex-talk] Losing some space entities

Import works, playing with webdav is giving good results so far. I still want to see how it outputs html through file:write with html5 serialization and if I can retain the entites in my pdfs. That's my next step. On Wed, Jan 18, 2017 at 6:02 PM, Christian Grün wrote:

Re: [basex-talk] Losing some space entities

Entities will only be serialized when using WebDAV. Did you try that as well? Am 19.01.2017 12:00 vorm. schrieb "France Baril" < france.ba...@architextus.com>: I haven't run many tests yet, but importing the file and exporting the files again from the gui only retains Also, when the entity is

Re: [basex-talk] Losing some space entities

I haven't run many tests yet, but importing the file and exporting the files again from the gui only retains Also, when the entity is in decimal (&8332;), it gets transformed to hex (not a big deal in my book). Other entities are 'applied', but not retained. I'm on BaseX 8.6 beta 4c3daeb On

Re: [basex-talk] Access-Control-Allow-Origin

Hi Lambert, Welcome to the list. > %rest:header-param("Access-Control-Allow-Origin", "http://localhost:;) With the %rest:header-param annotation, you can bind header parameters from the client request to variables. An example: declare %rest:path("/example1")

[basex-talk] Access-Control-Allow-Origin

Hi: This is probably an extremely newbie-ish question. I'm developing on localhost using MAMP/PHP at port , and basex at port 8984. So I am running into "Cross-Origin Resource Sharing" issues, apparently, when I have the PHP server issue an XMLHttpRequest to the Basex server. I would have

Re: [basex-talk] Gravierende Performance-Einbüße bei Persistierung von mehr als 5000, 160 KB große XML Datenstrukturen.

Hi Lucian, Thanks for taking your time, rerunning the tests and do some profiling. > When inserting a 160 KB xml structure 100.000 times, the persist operation > duration starts by ~45 ms and reach ~2000 ms after 68.000 persist > invocations and 16 hours of run time (!) Indeed this differs