BaseX-Talk November 2010

basex-talk@mailman.uni-konstanz.de

16 participants
20 discussions

update on context nodes
by Stefano Santoro 12 Nov '10

12 Nov '10

Hi, when I bind a DOM tree as the context item in XQJ against an XQuery script that performs updates, the passed DOM tree is not modified. Here is a groovy example import groovy.xml.XmlUtil import groovy.xml.DOMBuilder import groovy.xml.dom.DOMCategory import javax.xml.xquery.XQConstants docbuilder = DOMBuilder.newInstance() doc = docbuilder.sample() { renameMe(id:11) { renameInner(isit:"true","yes") } deleteMe(id:12) { alongWithMe("bummer") } insertBeforeMe(id:14) { alongWith(me:"true","Oh Yeah") andMe(too:"yes","Oh Yeah") } insertAfterMe(id:15) { atLevelThree(level:3) { atLevelFour(level:4, "fourth level") atLevelFour(level:4, "fourth level again") } alongWith(me:"true","Oh Yeah") } } // prints the DOM tree before updates XmlUtil.serialize(doc, System.out) ds = Class.forName("org.basex.api.xqj.BXQDataSource").newInstance() cnn = ds.getConnection() stmt = """ let \$r := . return ( rename node \$r/renameMe as 'gotRenamed', delete node \$r/deleteMe[@id='12'], insert node <gotInsertedBefore id='13'> <alongWithMe>Cool</alongWithMe> </gotInsertedBefore> before \$r/insertBeforeMe[@id='14'], insert node <gotInsertedAfter id='16'> <alongWithMe>Cool</alongWithMe> </gotInsertedAfter> after \$r/insertAfterMe[@id='15'] ) """ xe = cnn.prepareExpression(stmt) xe.bindNode(XQConstants.CONTEXT_ITEM, doc, null) xqs = xe.executeQuery() // the DOM tree was not modified XmlUtil.serialize(doc, System.out) xqs.close() xe.close() cnn.close() Should I pass it as an external variable instead? Ciao Stefano

2 1

Re: [basex-talk] Can't build using maven 3
by Michael Seiferle 10 Nov '10

10 Nov '10

Hi Stefano, (this time with cc to the list, as this might be of general interest :-)) sorry again for the inconvenience. We currently have no automatic deployment of the minor Version jars to our repository (we are about to change that soon, hopefully). The recoomended and "clean" solution is installing the latest repository version of BaseX into your local subversion repository via: > $ cd basex > $ svn up > $ mvn -DskipTests=true install This should avoid the errors below. Let me know if this helps and feel free to ask more! Kind regards Michael Am 10.11.2010 um 19:41 schrieb Stefano Santoro: > [WARNING] The POM for org.basex:basex:jar:6.3.2 is missing, no dependency information available > Downloading: http://repository.codehaus.org/org/basex/basex/6.3.2/basex-6.3.2.jar > Downloading: http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex/6.3.2/basex… > Downloading: http://repo1.maven.org/maven2/org/basex/basex/6.3.2/basex-6.3.2.jar >

1 0

predicate evaluation issue
by Martin Gieseking 10 Nov '10

10 Nov '10

Hello again, :) I think, I've found another bug. This time it's somehow related to implicit type casting. When running the query /a/b[@*=2] on the following XML document, both b nodes are selected, although the first one has no matching attribute. /a/b[@*='2'] returns the correct node. <a> </a> Best regards, Martin

2 3

types & encoding when talking to BaseX server
by Godmar Back 10 Nov '10

10 Nov '10

Hi, I have 2 questions regarding: https://svn.uni-konstanz.de/dbis/basex/trunk/api/etc/java/BaseXClient.java a) create() takes an InputStream. Which character encoding is assumed (I'm guessing UTF-8?) b) Query.next() returns a String. Is there a way/need to determine the type of the Query result (e.g., String, boolean, etc.)? (Or is an XQuery's result type statically determinable, in which case this would not be needed?) - Godmar

1 0

Re: [basex-talk] BaseXGUI
by Christian Grün 10 Nov '10

10 Nov '10

Dear Luca, > Hi, I'm playing with basex and succesfully running a server and the basic client BaseXClient remotely via an internet connection. I'm trying to do the same thing with BaseXGUI but I can only administer the remote server via BaseXGUI. Is there a way to connect and issue commands to a remote server using BaseXGUI? Currently, that's not possible; the visualization demand a much tighter integration with the backend, which cannot be realized via the client/server architecture. As this a frequently requested feature, we might add a console mode in a future version to allow text-based requests via the GUI. Best, Christian PS: mails to the mailing list are preferred.

1 0

Build error
by Huib Verweij 10 Nov '10

10 Nov '10

Hi, recently I have been unable to compile BaseX, the build fails on the org.basex.test.query.FNFormatIntegerTest test. It says: ------------------------------------------------------------------------------- Test set: org.basex.test.query.FNFormatIntegerTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.564 sec <<< FAILURE! test(org.basex.test.query.FNFormatIntegerTest) Time elapsed: 0.419 sec <<< FAILURE! java.lang.AssertionError: 7 wrong queries; [E] expected, [F] found: -- format-integer-014: string-join(for $i in 1 to 20 return format-integer($i, 'Ÿ°'), '|') [E] Ÿ°|Ÿ¢|Ÿ£|Ÿ§|Ÿ•|Ÿ¶|Ÿß|Ÿ®|Ÿ©|Ÿ°Ÿ†|Ÿ°Ÿ°|Ÿ°Ÿ¢|Ÿ°Ÿ£|Ÿ°Ÿ§|Ÿ°Ÿ•|Ÿ°Ÿ¶|Ÿ°Ÿß|Ÿ°Ÿ®|Ÿ°Ÿ©|Ÿ¢Ÿ† [F] Stopped at line 1, column 61: [FODF1340] Invalid picture string: "Ÿ°". -- format-integer-015: string-join(for $i in 1 to 20 return format-integer($i, 'Ÿ©'), '|') [E] Ÿ°|Ÿ¢|Ÿ£|Ÿ§|Ÿ•|Ÿ¶|Ÿß|Ÿ®|Ÿ©|Ÿ°Ÿ†|Ÿ°Ÿ°|Ÿ°Ÿ¢|Ÿ°Ÿ£|Ÿ°Ÿ§|Ÿ°Ÿ•|Ÿ°Ÿ¶|Ÿ°Ÿß|Ÿ°Ÿ®|Ÿ°Ÿ©|Ÿ¢Ÿ† [F] Stopped at line 1, column 61: [FODF1340] Invalid picture string: "Ÿ©". -- format-integer-046: string-join(for $i in 1 to 5 return format-integer($i, '‚ë†'), '|') [E] ‚ë†|‚ë°|‚ë¢|‚ë£|‚ë§ [F] Stopped at line 1, column 61: [FODF1340] Invalid picture string: "‚ë†". -- format-integer-047: string-join(for $i in 1 to 5 return format-integer($i, '‚ë¥'), '|') [E] ‚ë¥|‚ëµ|‚ë∂|‚ë∑|‚ë∏ [F] Stopped at line 1, column 61: [FODF1340] Invalid picture string: "‚ë¥". -- format-integer-048: string-join(for $i in 1 to 5 return format-integer($i, '‚íà'), '|') [E] ‚íà|‚íâ|‚íä|‚íã|‚íå [F] Stopped at line 1, column 61: [FODF1340] Invalid picture string: "‚íà". -- format-integer-049: string-join(for $i in 1 to 5 return format-integer($i, 'Œë'), '|') [E] Œë|Œí|Œì|Œî|Œï [F] Stopped at line 1, column 60: [FODF1340] Invalid picture string: "Œë". -- format-integer-050: string-join(for $i in 1 to 5 return format-integer($i,'Œ±'), '|') [E] Œ±|Œ≤|Œ≥|Œ¥|Œµ [F] Stopped at line 1, column 59: [FODF1340] Invalid picture string: "Œ±". at org.junit.Assert.fail(Assert.java:91) at org.basex.test.query.QueryTest.test(QueryTest.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.ParentRunner.run(ParentRunner.java:220) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.Surefire.run(Surefire.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017) The latest from SVN also fails. I'm on a Macbook. Any thoughts on what I can do, or is it a mac-specific bug, or ...? Kind regards, Huib.

2 3

erroneous evaluation of position() on descendant axis
by Martin Gieseking 09 Nov '10

09 Nov '10

Hi, while playing around with BaseX, I stumbled over some weird results in conjunction with positional predicates on the descendant axis. As far as I can see, there seems to be a bug in the evaluation of function position(). Example: When I load the following XML document and evaluate the path expression /descendant::c[1], both c element nodes are returned, but only the first one is expected. So, currently the result is identical to that of //c[1]. <a> <c/> <c/> </a> Best regards, Martin

3 7

Can't build using maven 3
by Stefano Santoro 09 Nov '10

09 Nov '10

Hi, I have checked out basex from subversion, and I could not compile it using maven 3, first it complains that the jar and compiler plugins do not have versions elements in the pom.xml. Second when I attempt a compilation I get the following errors: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project basex: Compilation failure: Compilation failure: [ERROR] /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[17,47] package com.sun.org.apache.xml.internal.resolver does not exist [ERROR] /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[18,53] package com.sun.org.apache.xml.internal.resolver.tools does not exist [ERROR] /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,14] cannot find symbol [ERROR] symbol : class CatalogManager [ERROR] location: class org.basex.build.xml.SAXWrapper [ERROR] /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,38] cannot find symbol [ERROR] symbol : class CatalogManager [ERROR] location: class org.basex.build.xml.SAXWrapper [ERROR] /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[99,32] cannot find symbol [ERROR] symbol : class CatalogResolver [ERROR] location: class org.basex.build.xml.SAXWrapper ssantoro@ssantoroubu:~/opt/basex/basex$ mvn -version Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400) Java version: 1.6.0_22 Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix" ssantoro@ssantoroubu:~/opt/basex/basex$ java -version java version "1.6.0_22" Java(TM) SE Runtime Environment (build 1.6.0_22-b04) Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode) Ciao Stefano Ciao Stefano

3 4

BaseX 6.3.1
by Christian Grün 08 Nov '10

08 Nov '10

Hi all, things are moving forward again; the latest minor release of BaseX 6.3.1 contains a bunch of improved features; we've revised our APIs, and we have added improved language support to XQuery Full Text. Next, we're doing our best to improve the availability of all BaseX features, many of which are just too hidden to be noticed by everyone, and to work on the documentation. Finally, we're glad to announce that we've successfully created the infrastructure to offer commercial requests and professional support on BaseX. The project itself will remain open source, of course. More is to come.. Here's the latest changelog (which is now available on the homepage as well): [ADD] Fulltext: Built-in support for Snowball, Wordnet, and Lucene stemmers [ADD] Fulltext: Internal German stemmer added [ADD] REST: support for hierarchical collections added; details will follow [ADD] REST/GET: bind parameter added to enable external variable bindings [ADD] REST/POST: <variable/> and <output/> elements added [ADD] APIs: bind(), execute() & info() added to query iterator [ADD] APIs: add() implemented for adding documents to existing databases [MOD] REST: start was simplified; just launch basex-api/etc/basexrest(.bat) [MOD] JAX-RX: latest version was moved to our BaseX SVN repository [MOD] Warning: start class BaseXWin was renamed to BaseXGUI [MOD] Work on the upcoming Windows installer [FIX] XQuery: improved handling of extended kind tests in sequence types [FIX] XQuery 3.0 functions (e.g. format-integer()) [FIX] XQuery Update, Namespaces, collections [FIX] GUI: realtime filtering Have fun, Christian ___________________________ Christian Grün University of Konstanz Department of Computer & Information Science D-78457 Konstanz, Germany Tel: +49-7531-88-4449, Fax: +49-7531-88-3577 http://www.inf.uni-konstanz.de/~gruen

1 0

REST interface does not support/comply-with 'default' XForms mediatype (application/xml) for PUT, POST (and possibly others)
by Mahender Didwania 04 Nov '10

04 Nov '10

If I attempt to create a resource using PUT or POST using XForms Submission mechanism, it fails because by default, XForms Submissions use application/xml as content-type, but BaseX expects text/xml. BaseX actually fails the request if given application/xml! Would like BaseX to support XForms - XForms default submission mediatypes are listed at http://www.w3.org/TR/xforms11/#submit-options Thanks.

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk November 2010