Re: [basex-talk] Quickest way to parse a DomSource

Thank you Martin. It's worth experimenting In the meanwhile (thanks to my colleague who had a closer look at the DOMSource API) I got to understand that there's a getNode() method returning the underlying DOM Node. This allows for minimizing the module import statements. Thus, fyi,  at

Re: [basex-talk] File-io:error. File lock by another process (windows-only)

Hi France, > It seems that basexhttp.bat was launching multiple instance of basex. We have multiple Windows instances running with BaseX, but I cannot recollect having had such an issue before (and I’m not sure how this could happen, as the code for starting the server is pretty

Re: [basex-talk] Quickest way to parse a DomSource

Am 22.07.2019 um 11:32 schrieb Marco Lettere: I have to access portions of the XML representation of the BPMN file by binding the engine's API. The closest that I can get to a standard XML representation is currently a javax.xml.transform.dom.DOMSource. What is the shortest way to transform

[basex-talk] Quickest way to parse a DomSource

Hi all, I'm currently working on the usage of BaseX Xquery scripts inside a BPMN engine. I have to access portions of the XML representation of the BPMN file by binding the engine's API. The closest that I can get to a standard XML representation is currently a

Re: [basex-talk] File-io:error. File lock by another process (windows-only)

Hi, We think we found the issue. It seems that basexhttp.bat was launching multiple instance of basex. It's the second time we see that on Windows systems. Is it possible that the Windows installation process sets environment variables which creates conflicts if other instances are installed