BaseX-Talk

basex-talk@mailman.uni-konstanz.de

1 participants
5252 discussions

Re: [basex-talk] losing line breaks with xslt:transform(...)
by Simon Görke 30 Jul '13

30 Jul '13

Christian, thanks for the hint, but no change for the better. I also tried with the basex-internal xslt-processor (instead of saxon) but resulted in the same problem. Any ideas welcome... Greets, Simon -----Ursprüngliche Nachricht----- Von: Christian Grün [mailto:christian.gruen@gmail.com] Gesendet: Freitag, 26. Juli 2013 14:56 An: Simon Görke Cc: BaseX Betreff: Re: [basex-talk] losing line breaks with xslt:transform(...) Hi Simon, not sure if that helps, but you can try to deactivate whitespace chopping in the prolog of your XQuery expression: declare option db:chop "no"; ... Best, Christian ___________________________ 2013/7/26 Simon Görke <simon.goerke(a)ils.uni-stuttgart.de>: > Hi, > > I have small issue regarding the xslt:transform function (or what lies > beneath). We are currently migrating a larger number of existing > stylesheets into a basex-environment (before they were used with saxon > on the filesystem). > > The problem is, that all line breaks which are generated explicitly in > the stylesheets (e.g. by using <xsl:text>
</xsl:text>) get lost. > Line feeds within a xsl:text element are correctly transformed. See > below for the xslt and example output. > > First we thought this might be linked to the whitespace chopping of > the database where the transformation result is stored, however I get > the same behavior when directly looking at the output of > xslt:transform(...) in the basex-gui. > Is there any options to influence this behavior? We are using saxon9 > within basex version 7.6. > > Thanks for your help > Simon > > > ------------------------------- > Excerpt from example stylesheet: > ... > <Document> > <xsl:text> > block1 line1 > block1 line2 > </xsl:text> > > <xsl:text>
</xsl:text> > <xsl:text>block2 line1</xsl:text> > <xsl:text>
</xsl:text> > <xsl:text>block2 line2</xsl:text> > > <xsl:text> > </xsl:text> > > <xsl:text>block3 line1</xsl:text> > > <xsl:text> > </xsl:text> > > <xsl:text>block3 line2</xsl:text> > > </Document> > .... > > ------------------------------------ > Result when running the stylesheet with saxon on the filesystem; All > line break variants actually result in new lines: > <Document> > block1 zeile1 > block1 zeile2 > block2 zeile1 > block2 zeile1 > block3 zeile1 > block3 zeile1 > </Document> > ---------------------------------- > > Result from calling xslt:transform in basex (saxon is used also within > basex); Only the line break within the xsl:text is visible in the > output: > <Document> > block1 line1 > block1 line2block2 line1block2 line2block3 line1block3 line2 > </Document> > ---------------------------------- > > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

2 1

connection provblems with basex 7.6
by Andreas Wombacher 30 Jul '13

30 Jul '13

Hi, I am running a server in Java on a linux machine and want to connect to it from a windows machine (either GUI or java code). It is not working. I get as a response that the connection is refused. On the linux machine the server is running - I see the port being listened on. The firewall is also open on that port - I can telnet the port and get a response. Any idea? I use these settings in .basex # Client/Server Architecture HOST = 130.89.1.182 PORT = 19840 SERVERPORT = 1984 EVENTPORT = 1985 USER = XXXX PASSWORD = XXXX SERVERHOST = silo1.ewi.utwente.nl thanbks in advance. best regards Andreas

1 0

losing line breaks with xslt:transform(...)
by Simon Görke 26 Jul '13

26 Jul '13

Hi, I have small issue regarding the xslt:transform function (or what lies beneath). We are currently migrating a larger number of existing stylesheets into a basex-environment (before they were used with saxon on the filesystem). The problem is, that all line breaks which are generated explicitly in the stylesheets (e.g. by using <xsl:text>
</xsl:text>) get lost. Line feeds within a xsl:text element are correctly transformed. See below for the xslt and example output. First we thought this might be linked to the whitespace chopping of the database where the transformation result is stored, however I get the same behavior when directly looking at the output of xslt:transform(...) in the basex-gui. Is there any options to influence this behavior? We are using saxon9 within basex version 7.6. Thanks for your help Simon ------------------------------- Excerpt from example stylesheet: ... <Document> <xsl:text> block1 line1 block1 line2 </xsl:text> <xsl:text>
</xsl:text> <xsl:text>block2 line1</xsl:text> <xsl:text>
</xsl:text> <xsl:text>block2 line2</xsl:text> <xsl:text> </xsl:text> <xsl:text>block3 line1</xsl:text> <xsl:text> </xsl:text> <xsl:text>block3 line2</xsl:text> </Document> .... ------------------------------------ Result when running the stylesheet with saxon on the filesystem; All line break variants actually result in new lines: <Document> block1 zeile1 block1 zeile2 block2 zeile1 block2 zeile1 block3 zeile1 block3 zeile1 </Document> ---------------------------------- Result from calling xslt:transform in basex (saxon is used also within basex); Only the line break within the xsl:text is visible in the output: <Document> block1 line1 block1 line2block2 line1block2 line2block3 line1block3 line2 </Document> ----------------------------------

2 1

A Resilient BaseX deployment
by Andrew Miller 24 Jul '13

24 Jul '13

Hi Folks, We are looking at deploying BaseX as a resilient deployment. If the BaseX server fails, then a stand-by server is to take over. My problem is how to replicate the data from the active Master to the passive slave. I found a thread from July 2012 proposing replicating the data directory using rsync. However, I have concerns about this. Firstly, if BaseX is writing to the database at the time of failure then the database on the Master would be corrupted, wouldn't it? Secondly, rsync does not guarantee a consistent file set is transferred. If BaseX updates the database during the rsync transfer, or the server fails during the rsync transfer, the database on the Slave would be corrupt, wouldn't it? I am considering using a cron job to do a "CREATE BACKUP" on the database at regular intervals and push the resulting zip file to the slave. If the Master fails during this process, we can detect the failure (at best we get an incomplete zip file, which will not be valid). If this happens we can fall back to the previous backup. If the Master fails, we detect this (using monit), start BaseX on the slave and do a database restore. I think this should give us a resilient deployment. In the worse case scenario (master dying during a replication) we lose changes since the last back-up, but at least we get a working database. Does this sound like a sound strategy? When I do a database restore, does BaseX automatically cope if the latest backup is corrupt? -- Andrew Miller Crocodile RCS Ltd

2 2

Basex json module and namespaces
by Arto Viitanen 24 Jul '13

24 Jul '13

Is there any way to make json module (mainly json:serialize) handle namespaces? I tried following: let $str := '{"name":"Mike Mac","address":{"postnumber":20221,"city":"NYC","street":"23 west A 22"},"email":"mm(a)gmail.com"}' let $json := json:parse($str) return json:serialize($json) and I get the string, with linefeed etc. But I would like to add the $json element inside another element, which have default namespace. let $str := '{"name":"Mike Mac","address":{"postnumber":20221,"city":"NYC","street":"23 west A 22"},"email":"mm(a)gmail.com"}' let $json := json:parse($str) let $wrapper := copy $x := <wrapper xmlns="namespace-uri"/> modify (insert node $json into $x) return $x let $json2 := $wrapper/*[1] return json:serialize($json2) (That is, insert the $json inside the <wrapper> -element, get it out and serialize it.) Instead of the same result as in the first case, I get 'BXJS0001 JSON serialization: Element <json> has invalid attribute "xmlns". ' But since it is default namespace, there is no easy way to drop it. My question is: is there any way to let json:serialize handle or ignore namespaces; at least default namespaces? -- Arto Viitanen Microteam Oy Tampere, Finland

2 1

early EOF bei Fileupload
by Florian Eckey 24 Jul '13

24 Jul '13

Hallo zusammen, ich habe ein Problem beim Fileupload. Dieser funktioniert nur sporadisch oder eher gesagt eigentlich funktioniert es in den seltensten Fällen. Ich bekomme dann immer einen 400 early EOF in den basex-Logs angezeigt. Ich habe im Internet recherchiert und herausgefunden, dass dies wohl an dem Jetty Servlet Container liegt, habe aber noch keine Lösung dafür gefunden. Ein Update der Jetty Version bringt leider auch nichts. Meine konkrete Implementierung schicke ich erst einmal nicht mit, da diese ja grundsätzlich funktioniert und ich eher vermute, dass das Problem eben am Jetty liegt. Das komische ist, dass der Request korrekt vom Browser abgeschickt wird und ich den Server und den Client auf einem gemeinsamen Rechner laufen habe. Hat jemand vielleicht ein ähnliches Problem oder dieses schon gelöst? Viele Grüße Florian

3 2

Protocol Question
by Gerald de Jong 23 Jul '13

23 Jul '13

I'm trying to quickly prototype a REST server which uses BaseX for persistence using NodeJS. I'm able to create a session, add a document, query that document, and then close the session. Fine. But when I create a query that should return no results, it seems the NodeJS module for BaseX I'm using seems to completely misunderstand the result and never execute the callback. I looked at the protocol spec http://docs.basex.org/wiki/Server_Protocolbut it doesn't seem to give back what is specified here. I need a sanity check. The driver sends this: -- Delving BV, Vasteland 8, Rotterdam http://www.delving.eu http://twitter.com/fluxe skype: beautifulcode +31629339805

2 6

json and restxq
by Jean-philippe Magué 22 Jul '13

22 Jul '13

Hello again, As we were testing the version 7.7, we ran into a problem (that actually existed in 7.6 too). We cannot produce json with restxq. We came up with a minimal file that illustrate the problem: ------- module namespace local = 'http://www.example.com/local'; declare %restxq:path("") %output:method("json") function local:test-json() { '{}' }; ------- This produce the following error : HTTP ERROR 400 Problem accessing /. Reason: [BXJS0002] JSON serialization: Atomic values cannot be serialized. Are we missing something ? Best, Jean-Philippe -- Jean-Philippe Magué Maître de Conférences en Humanités Numériques Responsable de l'Atelier des Humanités Numériques : ahn.ens-lyon.fr Ecole Normale Supérieure de Lyon +33 (0)4 26 23 38 08 -- "Using computers will therefore lead us to a more profound and systematic knowledge of human expression; in principle, it can help us to be more humanistic than before." Busa, 1980.

2 1

Circular module dependency
by Jean-philippe Magué 22 Jul '13

22 Jul '13

Hi, I'm having problem with modules importing each other. I have the two following restxq modules : moduleA.xqm ------------------ module namespace moduleA = 'http:/www.example.com/moduleA'; import module namespace moduleB = 'http:/www.example.com/moduleB' at 'moduleB.xqm'; declare function moduleA:f() { "" }; ------------------ moduleB.xqm ------------------ module namespace moduleB = 'http:/www.example.com/moduleB'; import module namespace moduleA = 'http:/www.example.com/moduleA' at 'moduleA.xqm'; ------------------ They fail to compile with the following error: Stopped at line 7, column 29 in /Users/jmague/work/basex/webapp/restxq/moduleA.xqm: [XQST0034] Duplicate declaration of function moduleA:f(...). Are cross imports just forbidden ? Yet, the XQuery specification state that (section 4.12.4 Cycles) : "Implementations must resolve cycles in the import graph, either at the level of module URIs or at the level of location URIs, and ensure that each module is imported only once." Best, Jean-Philippe -- Jean-Philippe Magué Maître de Conférences en Humanités Numériques Responsable de l'Atelier des Humanités Numériques : ahn.ens-lyon.fr Ecole Normale Supérieure de Lyon +33 (0)4 26 23 38 08 -- "Using computers will therefore lead us to a more profound and systematic knowledge of human expression; in principle, it can help us to be more humanistic than before." Busa, 1980.

3 4

Re: [basex-talk] ICE watch in stock
by silicon watch 22 Jul '13

22 Jul '13

ICE silicon watch 8 ready units colours available in STOCK now. Unit price: USD1.75/pc polybag package one year guarantee period Also, we can make your custom watch design with your logo and your unit colours. please contact us for more details about this watch and general watches price list. Thanks for your time, Daisy Sales manager TALECT INDUSTRIAL LIMITED Email: daisy(a)talect.cn talectdaisy(a)gmail.com Skype: talect MSN: talectdaisy(a)hotmail.com Tel: 0086-755-82130052 Fax: 0086-755-82130042 Web: www.talect.cn http://cntalect.en.alibaba.com/ http://www.hktdc.com/em/sztalect

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk