BaseX-Talk February 2013

basex-talk@mailman.uni-konstanz.de

49 participants
78 discussions

Problem with DOM LS serialization
by Michael.Hedenus-EXT＠continental-corporation.com 04 Feb '13

04 Feb '13

Dear All, unfortunately I cannot serialize items using DOM/LS. I get an NullPointerException because Node.getParentNode() returns null. Here's the use-case: public class Test { public static void main(String[] args) throws Exception { System.setProperty("org.basex.path", "D:\\ODX-Development-Neu\\odx-workspace\\.database"); Context context = new Context(); try { // // open DB and query an item // new Open("vag").execute(context); QueryProcessor queryProcessor = new QueryProcessor("//BASE-VARIANT[SHORT-NAME='BV_EnginContrModul1UDS']", context); Item item = queryProcessor.iter().next(); // // serialize item, proofs that result is here // Serializer serializer = queryProcessor.getSerializer(System.out); // can the queryProcessor be closed here? queryProcessor.close(); serializer.serialize(item); serializer.close(); // // write with DOM fails!!! // org.w3c.dom.Node node = (org.w3c.dom.Node)item.toJava(); DOMImplementationLS domImplementationLS = (DOMImplementationLS)DOMImplementationRegistry.newInstance ().getDOMImplementation("LS"); LSOutput lsOutput = domImplementationLS.createLSOutput(); lsOutput.setByteStream(System.out); LSSerializer lsSerializer = domImplementationLS.createLSSerializer(); lsSerializer.getDomConfig().setParameter( "format-pretty-print", Boolean.TRUE); lsSerializer.write(node, lsOutput); } finally { context.close(); } } } And the exception: Caused by: java.lang.NullPointerException at com.sun.org.apache.xml.internal.serialize.DOMSerializerImpl.prepareForSerialization( DOMSerializerImpl.java:1064) at com.sun.org.apache.xml.internal.serialize.DOMSerializerImpl.write( DOMSerializerImpl.java:747) ... 1 more I am using the latest snapshot: BaseX76-20130131.202759 Can you help me? Mit freundlichen Grüßen/Best regards Dr. Michael Hedenus Software Developer Powertrain Engine Systems CSW ETV RGB T2 PIXEL GmbH Im Gewerbepark C15, 93059 Regensburg, Germany Telefon/Phone: +49 941 790-6362 Telefax: +49 941 79013-90771 E-Mail: michael.hedenus-ext(a)continental-corporation.com www.continental-corporation.com ______________________________________________________________________ Continental Automotive GmbH, Siemensstr. 12, 93055 Regensburg, Germany Geschäftsführer/Managing Directors: Helmut Matschi, Gérard Cordonnier, Harald Stuhlmann Sitz der Gesellschaft/Registered office: Hannover Registergericht/Commercial registry: Hannover, HRB 59424, USt-Id. Nr. DE814950663 _______________________________________________________________________ Proprietary and confidential. Distribution only by express authority of Continental AG or its subsidiaries.

2 2

Xquery with server commands
by Raymond Meester 04 Feb '13

04 Feb '13

Consider the following xquery on "db2": for $doc in db:open('db2') return $doc with the following code //start session static ClientSession session; session = new ClientSession("localhost", 1984, "admin", "admin"); session.execute(new Check(db1)); //query ClientQuery query = session.query(xquery); result = query.execute(); query.close(); This code will execute, but with an empty result. This is because within the session only db1 is opened and I am querying db2. When explicit opening (session.execute(new Open(db2)); ) it returns the expected value of course. Do you agree that this can be confusing? I would expect that the xquery in combination with the above code returns 1) an error that quering db2 while it's not opened in the session or 2) that "db:open('db2')" in the xquery performs implicitly a session.execute(new Open(db2), so that it automatically switches to db2.

2 1

Updating DB using Java Code
by John Best 02 Feb '13

02 Feb '13

Dear BaseX Team, I am using BaseX to store XML. This XML DB will get updated regularly through net. After updating, I will need to create Full-Text, Text and Attribute Indexes. Below is the Java Code I am using - str = "http://www.abcd.com/updates/data.xml"; qry = "for $c in doc('"+ str +"')//Doc return insert node $c into doc('myDoc')/Docs"; try { query(qry); } catch(Exception e) { System.out.println(e); } try { System.out.println("Opening the Database....."); new Open("myDocs").execute(CONTEXT); System.out.println("Database opened....."); System.out.println("Indexing started....."); new CreateIndex("FULLTEXT").execute(CONTEXT); new CreateIndex("TEXT").execute(CONTEXT); new CreateIndex("ATTRIBUTE").execute(CONTEXT); System.out.println("Indexing done....."); } catch(Exception e) { System.out.println("Exception while creating Index " + e); } In the above code, I am doing 2 things- first is updating the "myDocs" database and after that Indexing... The first part, updation is not working. I tried to execute the query directly in BaseX, but its not working there too. *But when I open the said DB and run the same query, its updating the DB*.. !! -- Have a nice day JBest

2 1

Re: [basex-talk] URI resolver when calling XSLT
by Christian Grün 01 Feb '13

01 Feb '13

Hi Wendell, hi all, path resolutions should now correctly work for both the XSLT and the Validation Module. You are invited to check out the latest stable snapshot [1]. Best, Christian [1] http://files.basex.org/releases/latest/ ___________________________ On Thu, Jan 31, 2013 at 10:20 PM, Wendell Piez <wapiez(a)wendellpiez.com> wrote: > Dear Christian, > > My problem is actually on the XSLT side, using xsl:import from a > stylesheet being processed by Saxon (using the xslt:transform() > function). I am only surmising they will (would) be resolved the same > way as calling modules of an XSD. Should I send you a demonstration > example? > > Cheers, > Wendell > > > On Thu, Jan 31, 2013 at 4:18 AM, Christian Grün > <christian.gruen(a)gmail.com> wrote: >> ..to simplify testing, could you send me some xml/xsd files your are >> working with? >> >> Thanks, >> Christian >> ___________________________ >> >> On Mon, Jan 28, 2013 at 10:00 PM, Wendell Piez <wapiez(a)wendellpiez.com> wrote: >>> Hi, >>> >>> I've run into a similar problem to the one described (I think) below: >>> I can invoke XSLT in BaseX (fantastic) but I get compiler errors if >>> the stylesheet relies on xsl:import or xsl:include (not so good). >>> >>> As I understand it, the JAXP interface (supported by Saxon and Xalan) >>> allows you to provide your own URIResolver class, which is (I imagine) >>> the way to fix this. But I'm no Java programmer. >>> >>> It would be very (very) nice to be able to do this right. >>> >>> My apologies if this post is no help but only a "me too". :-) >>> >>> Cheers, >>> Wendell >>> >>> On Fri, Jan 25, 2013 at 4:41 PM, Christian Grün >>> <christian.gruen(a)gmail.com> wrote: >>>> Hi Seenivasan, >>>> >>>> finally some feedback.. >>>> >>>>> let $doc := <a /> >>>>> let $schema := doc("../xsd/XDW.xsd") >>>>> return validate:xsd($doc,$schema) >>>> >>>> Yes, I see this is a problem, and I’ve encountered similar use cases, >>>> but I'm currently not sure how to fix this properly. The issue is that >>>> BaseX relies on external schema validation, so we don’t have direct >>>> access to the code executing the validation. >>>> >>>> It could well be that Java’s validator interface provides some methods >>>> to set/modify the path to the current base uri. If you – or someone >>>> else – has time, ideas and/or experience how to fix this, suggestions >>>> and patches are welcome (see [1] for the source code). >>>> >>>>> Basex reports the first error while validating with xsd schema, while java >>>>> uses to report the collection of errors that do not depend on each other. >>>> >>>> A similar observation applies here: the error handling in the >>>> mentioned class could be revised in order to catch more than just the >>>> first error [2]. >>>> >>>> Feel free to ask if you have more questions, >>>> Christian >>>> >>>> [1] https://github.com/BaseXdb/basex/blob/master/src/main/java/org/basex/query/… >>>> [2] https://github.com/BaseXdb/basex/blob/master/src/main/java/org/basex/query/… >>>> _______________________________________________ >>>> BaseX-Talk mailing list >>>> BaseX-Talk(a)mailman.uni-konstanz.de >>>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>> >>> >>> >>> -- >>> Wendell Piez | http://www.wendellpiez.com >>> XML | XSLT | electronic publishing >>> Eat Your Vegetables >>> _____oo_________o_o___ooooo____ooooooo_^ >>> _______________________________________________ >>> BaseX-Talk mailing list >>> BaseX-Talk(a)mailman.uni-konstanz.de >>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > > > > -- > Wendell Piez | http://www.wendellpiez.com > XML | XSLT | electronic publishing > Eat Your Vegetables > _____oo_________o_o___ooooo____ooooooo_^

1 0

Java User Function and Context Awareness
by Lansing, Jeff J CIV SPAWARSYSCEN-PACIFIC, 56250 01 Feb '13

01 Feb '13

It seems that there is no way for a Java user function installed in the Repository to get access to the current context node. Yes the context is available because of extending abstract QueryModule, but it seems the value of the current context node has been wiped out by the call from UserFunc.value() [at UserFunc:line 170] before it gets to the actual user function [during line 175]. Is there some way for a user function to recover that value, or is this just a limitation of the user function mechanism? Thanks.

2 10

XQJ, option declaration
by marco fregonese 01 Feb '13

01 Feb '13

Hi there, In my application I have this method: public static String getAllPartsAsTree(String a) throws XQException, XQQueryException { XQConnection con = Connection.getConnection(); XQExpression xqe = con.createExpression(); xqe.bindString(new QName("b"), a, null); String xqueryString = "import module namespace lib=\" http://www.example.com/library_module\";" + "declare option output:method \"xhtml\";" + "declare variable $b external; " + "lib:gethtml($b)"; XQResultSequence rs = xqe.executeQuery(xqueryString) ; String b = rs.getSequenceAsString(null); con.close(); return b; } When I run the app I get the following error message: Exception in thread "main" javax.xml.xquery.XQException: The prefix "output" is unknown in this static context. I can't understand how to interpret the error message. The same query in BaseXGUI works perfectly. I hope someone can help me. Thanks!

2 1

<tag></tag> vs <tag/>
by marco fregonese 01 Feb '13

01 Feb '13

Hi there, I have to return from a query tags like this: <script></script> not self closing tags like this: <script/> Is there any way to do that in BaseX? Thanks.

3 3

URI resolver when calling XSLT
by Wendell Piez 01 Feb '13

01 Feb '13

Hi, I've run into a similar problem to the one described (I think) below: I can invoke XSLT in BaseX (fantastic) but I get compiler errors if the stylesheet relies on xsl:import or xsl:include (not so good). As I understand it, the JAXP interface (supported by Saxon and Xalan) allows you to provide your own URIResolver class, which is (I imagine) the way to fix this. But I'm no Java programmer. It would be very (very) nice to be able to do this right. My apologies if this post is no help but only a "me too". :-) Cheers, Wendell On Fri, Jan 25, 2013 at 4:41 PM, Christian Grün <christian.gruen(a)gmail.com> wrote: > Hi Seenivasan, > > finally some feedback.. > >> let $doc := <a /> >> let $schema := doc("../xsd/XDW.xsd") >> return validate:xsd($doc,$schema) > > Yes, I see this is a problem, and I’ve encountered similar use cases, > but I'm currently not sure how to fix this properly. The issue is that > BaseX relies on external schema validation, so we don’t have direct > access to the code executing the validation. > > It could well be that Java’s validator interface provides some methods > to set/modify the path to the current base uri. If you – or someone > else – has time, ideas and/or experience how to fix this, suggestions > and patches are welcome (see [1] for the source code). > >> Basex reports the first error while validating with xsd schema, while java >> uses to report the collection of errors that do not depend on each other. > > A similar observation applies here: the error handling in the > mentioned class could be revised in order to catch more than just the > first error [2]. > > Feel free to ask if you have more questions, > Christian > > [1] https://github.com/BaseXdb/basex/blob/master/src/main/java/org/basex/query/… > [2] https://github.com/BaseXdb/basex/blob/master/src/main/java/org/basex/query/… > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

4 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk February 2013