- BaseX-Talk - mailman.uni-konstanz.de

copy behavior ?
by Xavier-Laurent SALVADOR 06 Mar '18

06 Mar '18

Hi List, I was working on multi replacement in Word docx. I saw a strange behavior of "copy/modify". I modified a document.xml and zip my folder content twice when I realized my template was wrong. I had to do it again and, after a hundred tries, I realized that copy/modify clause restored every time the old version of my content. I had to close basexGui and relaunch it to have my changes taken in charge. Hi List, I was working on multi replacement in Word docx. I saw a strange behavior of "copy/modify". I modified a document.xml and zip my folder content twice when I realized my template was wrong. I had to do it again and, after a hundred tries, I realized that copy/modify clause restored every time the old version of my content. I had to close basexGui and relaunch it to have my changes taken in charge. Hi List, I was working on multi replacement in Word docx. I saw a strange behavior of "copy/modify". Here is the fact: I use Basex to modify document.xml then zip its folder in a docx file. After a few try, I needed to modify the original and start the process again. But it always zipped back the elder document.xml version I had corrected ... and deleted (I mean, the text inside $doc was the elder version, see infra). I had to close basexGui and relaunch it to have my new file taken in charge. And I have to do this every time I modify the original docx file. Here is the code : declare function local:mapp($path,$space){ for $x at $count in file:list($path) order by $x descending return if (file:is-dir($path||'/'||$x)) then let $s := count(analyze-string($path||$x,'/')//fn:match) return <zip:dir name = "{replace($x,'/$','')}"> {local:mapp($path||'/'||$x,$s)} </zip:dir> else <zip:entry name="{$x}" src="{$path}/{$x}"/> }; for $x in file:read-text-lines('liste.txt') return *copy $doc := doc("/document.xml")* modify for $w in $doc//w:t[.//text() contains text 'XXXXX'] return replace value of node $w with replace($w,'XXXXX',$x) return ( file:write("document.xml",$doc) , let $rep := "/docx" let $dest := "/tmp" return zip:zip-file( <file xmlns="http://expath.org/ns/zip" href="{$dest}/courrier{$count} .docx"> {local:mapp($rep,1)} </file>) ) All the best, X -- Ce message peut contenir des informations réservées exclusivement à son destinataire. Toute diffusion sans autorisation est interdite. Si vous n'en êtes pas le destinataire, merci de prendre contact avec l'expéditeur et de détruire ce message. *This email may contain material for the sole use of the intended recipient. Any forwarding without express permission is prohibited. If you are not the intended recipient, please contact the sender and delete all copies*. -- Ce message peut contenir des informations réservées exclusivement à son destinataire. Toute diffusion sans autorisation est interdite. Si vous n'en êtes pas le destinataire, merci de prendre contact avec l'expéditeur et de détruire ce message. *This email may contain material for the sole use of the intended recipient. Any forwarding without express permission is prohibited. If you are not the intended recipient, please contact the sender and delete all copies*. -- Ce message peut contenir des informations réservées exclusivement à son destinataire. Toute diffusion sans autorisation est interdite. Si vous n'en êtes pas le destinataire, merci de prendre contact avec l'expéditeur et de détruire ce message. *This email may contain material for the sole use of the intended recipient. Any forwarding without express permission is prohibited. If you are not the intended recipient, please contact the sender and delete all copies*.

2 1

Re: [basex-talk] Problem launching BaseX on fresh Fedora 27
by Kristian Kankainen 05 Mar '18

05 Mar '18

1 0

Problem launching BaseX on fresh Fedora 27
by Kristian Kankainen 04 Mar '18

04 Mar '18

I downloaded both the stable and latest release, they both give me the same error message: > java.awt.HeadlessException > at sun.awt.HeadlessToolkit.setDynamicLayout(HeadlessToolkit.java:294) > at org.basex.BaseXGUI.init(BaseXGUI.java:113) > at org.basex.BaseXGUI.<init>(BaseXGUI.java:67) > at org.basex.BaseXGUI.main(BaseXGUI.java:39) > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.basex.gui.GUIMenuCmd.<init>(GUIMenuCmd.java:916) > at org.basex.gui.GUIMenuCmd.<init>(GUIMenuCmd.java:911) > at org.basex.gui.GUIMenuCmd$1.<init>(GUIMenuCmd.java:35) > at org.basex.gui.GUIMenuCmd.<clinit>(GUIMenuCmd.java:35) > at org.basex.gui.GUIConstants.<clinit>(GUIConstants.java:96) > at org.basex.BaseXGUI.<init>(BaseXGUI.java:69) > at org.basex.BaseXGUI.main(BaseXGUI.java:39) > Caused by: java.awt.HeadlessException > at > sun.awt.HeadlessToolkit.getMenuShortcutKeyMask(HeadlessToolkit.java:236 Do I have some missing Java stuff? I use the latest Fedora and I thought it comes well prepared with Java ... I just installed it a few days ago. Best regards Kristian K

2 2

9.0?
by Marco Lettere 01 Mar '18

01 Mar '18

Hi Christian & team, since XML Prague 18 is approaching I remembered that there used to be this wonderful habit of releasing a new BaseX version for the event :-). I am wondering whether there are any timing plans for the 9.0 release. In particular we are eager to test the new features [1] and [2]. Thank you for any updates on the matter and please continue with your incredible work! Best regards, Marco. [1] https://github.com/BaseXdb/basex/issues/1498 (persistent jobs) [2] https://github.com/BaseXdb/basex/issues/1449 (websocket support)

2 2

Signature of db:add
by Tim Thompson 28 Feb '18

28 Feb '18

Hello, The two argument signature of the db:add function does not seem to work ( http://docs.basex.org/wiki/Database_Module#db:add) Is this still valid in BaseX? When I try something like db:add("test", <test/>), I get an error: [FODC0007] Resource path '' is invalid. Thanks! -- Tim A. Thompson Discovery Metadata Librarian Yale University Library

2 1

Whitespace chopping / option -w
by Hans-Juergen Rennau 27 Feb '18

27 Feb '18

Dear BaseX team, "whitespace chopping" (which happens by default unless command-line option -w is used) does not only remove "whitespace-only" text nodes, but also leading/trainling whitespace in element content, for example: doc.xml:<hello> BaseX is phantastic! </hello> basex -i doc.xml . => <hello>BaseX is phantastic!</hello> While the result is of course true, I regard leading/trailing whitespace in element content as information which has a different "level of significance" than whitespace-only text nodes. In other words: I think it is an important use case that leading/trailing whitespace must be preserved, while the "pretty print whitespace" should be discarded. Did I overlook a way to get rid of whitespace-only text nodes without touching leading/trailing whitespace in element content? If not, it would be wonderful if you added a new option doing just that. With kind regards -Hans-Jürgen

1 0

Update Module question: update:apply
by Bridger Dyson-Smith 26 Feb '18

26 Feb '18

Hi all -- I was working with the update:apply example [1], and it throws an error: [XPTY0004] Cannot convert xs:string to node(): "doc.xml". I'm a little confused by this: if I modify the example, and change the last to `db:add('existing-db', 'doc.xml')` (which is db:add#1, right?), it works fine. However, keeping the local:update and trying to use `db:add#1` generates another error: [XPST0017] db:add(database,input[,path[,options]]): 1 argument supplied, 2-4 expected Would someone be able to shed some light on where this is going wrong? Thanks, Bridger [1] http://docs.basex.org/wiki/Update_Module#update:apply

2 2

Re: [basex-talk] bug in XSLT
by Kristian Kankainen 24 Feb '18

24 Feb '18

2 1

bug in XSLT
by nikos dimitrakas 23 Feb '18

23 Feb '18

There seems to be a problem when using baseX to create html with XSLT. Saxon seems to add a META-tag if the head-tag is present. But it is not <meta/>. It is instead <meta> (without closing tag, which is ok in html) and this causes baseX to give an error: The element type "META" must be terminated by the matching end-tag "</META>". With the newer version of Saxon the error is the same but the case has been changed to <meta> instead of <META>. This can be easily reproduced with the following query: let $s := <xsl:transform version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="html"/> <xsl:template match="/"> <html><head/><body/></html> </xsl:template> </xsl:transform> return xslt:transform(/, $s) In the new XSLT version there is an option to set the output to xhtml and that works, but the html output (which is the only available option in XSLT 1) fails. The generated meta tag seem to be this <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> I have even tried to override this by specifying that meta tag myself with closing tag but that does not work. I even tried setting the attribute include-content-type in the xsl:output, but it had no effect. Setting the output method to xml would work if the html genererated is in fact correct xml (like in the example above). Output metod "text" seems to also behave strangely. Maybe BaseX ignores the output method and tries to treat everything as xml? /nikos

1 0

BaseX not running
by Leo Studer 21 Feb '18

21 Feb '18

Hello I try desperately getting baseX 8.6.7 to run on MacOS X 10.13.3 where I have Java 9 installed Here the error message: BaseX installed with homebrew today: MBP-2015:~ leo$ basexgui WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX (file:/usr/local/Cellar/basex/8.6.7/libexec/BaseX.jar) to method com.apple.eawt.Application.getApplication() WARNING: Please consider reporting this to the maintainers of org.basex.gui.GUIMacOSX WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Failed to initialize native Mac OS X interface MBP-2015:~ leo$ and the same error with the Jar file Last login: Wed Feb 21 18:16:27 on ttys001 MBP-2015:~ leo$ java -jar ~/Downloads/BaseX867.jar WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX (file:/Users/leo/Downloads/BaseX867.jar) to method com.apple.eawt.Application.getApplication() WARNING: Please consider reporting this to the maintainers of org.basex.gui.GUIMacOSX WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Failed to initialize native Mac OS X interface MBP-2015:~ leo$ Any suggestions? Thanks for caring Always Leo

2 1