Using BaseX as a standalone xquery library in Java

Anything special to think about when using BaseX outside the database-context? I have built some solutions using the QueryProcessor for generating filesystem reports using the supplied modules for calculating file-sizes and checksums. I hava also built a number of wrappers for calling and aggregating results from web-services. All these queries are embedded and run in our normal java-processes. Everything has worked out really well. And BaseX gives you access to a lot of good functionality like XQuery 3.0 and a rich set of modules. But I'm a bit curious if there are any drawback or special things to think about with using Basex as a general xquery-library like you would use Saxon for example? Regards, Johan Mörén

Hi Johan,

Thanks for the kudos and for describing your use case. It's perfectly fine to BaseX outside the database context! I'm aware of many scenarios, in which BaseX is used without databases, or in which the data is even stored in relational or other NoSQL stores. As XQuery is more and more evolving into a general-purpose language (we like to call it "Information Processing Language"), and as many of our modules are built to cover non-database aspects, I can only recommend to leave the database realm. Best, Christian

Hi Johan, here comes an example of user experience. For many years I have used XQuery exclusively with the Saxon processor. I could not imagine that any other processor might offer comparable reliability, conformance and performance. But about three years ago I started to use BaseX, too - in the beginning, only to take advantage of the possibility to process huge documents (via database) which cannot be loaded into memory, as well as functionality not supported by the Saxon Home Edition (e.g. the file module). Since then, I have been finding myself using BaseX more and more: it is very reliable (also when dealing with extremely complex applications, with 10000s of lines), highly performant and offers absolutely amazing support for the newest specifications (XQuery 3.0, XQuery Update Facility), not to mention its being, at the same time, a database system, its REST support and its great wealth of useful extension functions. In summary: I regard BaseX as an outstanding XQuery processor which I recommend warmly. Regards, Hans-Juergen --------------------------------------------

Betreff: [basex-talk] Using BaseX as a standalone xquery library in Java An: basex-talk at mailman.uni-konstanz.de Datum: Dienstag, 18. Februar, 2014 10:19 Uhr Anything special to think about when using BaseX outside the database-context? I have built some solutions using the QueryProcessor for generating filesystem reports using the supplied modules for calculating file-sizes and checksums. I hava also built a number of wrappers for calling and aggregating results from web-services. All these queries are embedded and run in our normal java-processes. Everything has worked out really well. And BaseX gives you access to a lot of good functionality like XQuery 3.0 and a rich set of modules. But I'm a bit curious if there are any drawback or special things to think about with using Basex as a general xquery-library like you would use Saxon for example? Regards,Johan Mörén -----Integrierter Anhang folgt----- _______________________________________________ BaseX-Talk mailing list BaseX-Talk at mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk