BaseX-Talk June 2010

basex-talk@mailman.uni-konstanz.de

22 participants
32 discussions

Binding for BaseX in Rebol
by sf＠sabufrancis.com 05 Jun '10

05 Jun '10

Hi Thank you for your wonderful Native XML database system. I have been working with it for a few months now, and am quite happy to submit a Rebol binding for BaseX. This was based by my understanding of the Java Binding given by you. Please take a look here http://code.google.com/p/reb-basex Let me have your feedback! Thanks Regards Sabu Francis

2 1

Fwd: Having trouble inserting elements using XQJ two times with the same prepared expression
by Stefano Santoro 02 Jun '10

02 Jun '10

Hi Lukas, just to be thorough I tried all the steps I have described in my earlier e-mail on a different workstations running a different OS (linux), and the attempt yielded the same Exception. Ciao Stefano On Fri, May 28, 2010 at 1:14 PM, Stefano Santoro <stefano(a)santoro.org> wrote: > Hi Lukas, > > Interesting. I have gotten all your maven repository jar files and > included them in the class path as follows: > > $ echo $GVYCP > C:\opt\jlib\basex-api\xmldb-api-1.0.jar;C:\opt\jlib\basex-api\xqj-api-1.0.jar;C:\opt\jlib\basex-api\basex-api-6.1.3.jar;C:\opt\jlib\basex-api\basex-6.1.3.jar > > the same but more clearly listed > > $ dvcp GVYCP > 0) C:\opt\jlib\basex-api\xmldb-api-1.0.jar > 1) C:\opt\jlib\basex-api\xqj-api-1.0.jar > 2) C:\opt\jlib\basex-api\basex-api-6.1.3.jar > 3) C:\opt\jlib\basex-api\basex-6.1.3.jar > > I have run the same java class I have enclosed in the earlier version > as follows: > > $ java -version > java version "1.6.0_17" > Java(TM) SE Runtime Environment (build 1.6.0_17-b04) > Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing) > > $ java -cp ".;${GVYCP}" NPEReproducer > java.lang.ArrayIndexOutOfBoundsException: 5 > at org.basex.query.up.Primitives.add(Primitives.java:52) > at org.basex.query.up.DBPrimitives.add(DBPrimitives.java:40) > at org.basex.query.up.Updates.add(Updates.java:90) > at org.basex.query.up.Insert.atomic(Insert.java:102) > at org.basex.query.up.Insert.atomic(Insert.java:30) > at org.basex.query.expr.Expr.iter(Expr.java:58) > at org.basex.query.QueryContext.iter(QueryContext.java:322) > at org.basex.query.QueryContext.iter(QueryContext.java:290) > at org.basex.api.xqj.BXQDynamicContext.execute(BXQDynamicContext.java:246) > at org.basex.api.xqj.BXQPreparedExpression.executeQuery(BXQPreparedExpression.java:54) > at NPEReproducer.reproduceNPE(NPEReproducer.java:51) > at NPEReproducer.main(NPEReproducer.java:60) > > I have also checked out your basex trunk and was able to build > basex-6.1.3.jar, and even with that jar the same exception was thrown. > > I was not able to build the api maven project as it could not resolve > the jax-rx dependency.(see attached log) > > I was able though to build an api jar from your trunk that contained > only the xml:db and XQJ drivers from trunk, and with that too the same > exception was thrown. > > So I have tried with the jars that I have downloaded from: > > http://www.inf.uni-konstanz.de/dbis/basex/maven/org/xmldb/xmldb-api/1.0/xml… > http://www.inf.uni-konstanz.de/dbis/basex/maven/javax/xml/xquery/xqj-api/1.… > http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex-api/6.1.3/b… > http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex/6.1.3/basex… > > I have also built basex-6.1.3.jar and basex-6.1.3.jar (w/o jaxrx) from > your trunk, and yet I was not able to run it as you were able to do. > > Is there anything I am missing? > > Ciao > Stefano > > > > On Fri, May 28, 2010 at 9:15 AM, Lukas Kircher > <lukaskircher1(a)googlemail.com> wrote: >> Hey Stefano, >> >> thanks for your report. >> >>> I am enclosing a java class file that reproduces this problem against >>> 6.1.3 basex jar files >> >> >> Unfortunately I wasn't able to reproduce the exception by running your >> code - neither with version 6.1.3 nor with our current repository version. >> It runs fine on my machine. Do you have a clue where I could've missed >> something? >> >> Or - if you have another case at hand where you encounter the same problem, >> just let us know and we'll see what we can do. >> >> Kind regards, >> Lukas >> >

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk June 2010