exist-open — Open discussion

[Exist-open] Can eXist read and display data from an xpt file?

[Ted H. <meg...@gm...>]

I tried installing a computer program called R on my computer and it can't
seem to read any xpt files.  I was wondering if eXist can read such files.

Re: [Exist-open] New installation on Windows 11

[Hayim L. <hl...@um...>]

Thank you, will do so!


On Fri, Oct 21, 2022 at 11:14 AM Joe Wicentowski <jo...@gm...> wrote:

> Hi Hayim,
>
> I don't have any experience using eXist on Windows (at least since ~2008),
> but hopefully other folks here may. You might also try asking in the eXist
> community Slack, if you haven't already. I think the Slack is more active
> than the mailing list these days.
>
> (For anyone who's not already joined, see the invitation link in the eXist
> GitHub repository's README under Resources:
> https://github.com/eXist-db/exist#resources.)
>
> Joe
>
> On Thu, Oct 20, 2022 at 1:10 PM Hayim Lapin <hl...@um...> wrote:
>
>> Hello all, I am circling back to see if anyone has experienced this
>> installation problem.
>> I have updated Java to the latest version and run the startup script with
>> admin privileges.
>> Now I encounter the following error:
>> Cannot run program C:\path\to\java.javaw.exe (in director
>> C:\path\to\exist): CreateProcess error=206, The filename or extension is
>> too long
>>
>> Many thanks!
>> HL
>>
>> On Wed, Oct 12, 2022 at 8:23 PM Hayim Lapin <hl...@um...> wrote:
>>
>>> Java(TM) SE Runtime Environment (build 1.8.0_341-b10)
>>> Do I need the jdk?
>>>
>>> On Wed, Oct 12, 2022 at 7:10 PM Joe Wicentowski <jo...@gm...>
>>> wrote:
>>>
>>>> Which version of Java is installed?
>>>>
>>>> On Wed, Oct 12, 2022 at 4:39 PM Hayim Lapin <hl...@um...> wrote:
>>>>
>>>>> Hello list,
>>>>> I am trying to install exist 6.0.1 on a new computer running windows
>>>>> 11. I can successfully run exist-installer-6.0.1.jar, and can start up from
>>>>> the windows icon, but I only get as far as the first-use screen. After
>>>>> that, nothing; exist does not start.
>>>>> Any suggestions about how to troubleshoot this?
>>>>>
>>>>> Many thanks,
>>>>> HL
>>>>>
>>>>> _______________________________________________
>>>>> Exist-open mailing list
>>>>> Exi...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>>
>>>> --
>>>> Sent from my iPhone
>>>>
>>>

Re: [Exist-open] New installation on Windows 11

[Joe W. <jo...@gm...>]

Hi Hayim,

I don't have any experience using eXist on Windows (at least since ~2008),
but hopefully other folks here may. You might also try asking in the eXist
community Slack, if you haven't already. I think the Slack is more active
than the mailing list these days.

(For anyone who's not already joined, see the invitation link in the eXist
GitHub repository's README under Resources:
https://github.com/eXist-db/exist#resources.)

Joe

On Thu, Oct 20, 2022 at 1:10 PM Hayim Lapin <hl...@um...> wrote:

> Hello all, I am circling back to see if anyone has experienced this
> installation problem.
> I have updated Java to the latest version and run the startup script with
> admin privileges.
> Now I encounter the following error:
> Cannot run program C:\path\to\java.javaw.exe (in director
> C:\path\to\exist): CreateProcess error=206, The filename or extension is
> too long
>
> Many thanks!
> HL
>
> On Wed, Oct 12, 2022 at 8:23 PM Hayim Lapin <hl...@um...> wrote:
>
>> Java(TM) SE Runtime Environment (build 1.8.0_341-b10)
>> Do I need the jdk?
>>
>> On Wed, Oct 12, 2022 at 7:10 PM Joe Wicentowski <jo...@gm...> wrote:
>>
>>> Which version of Java is installed?
>>>
>>> On Wed, Oct 12, 2022 at 4:39 PM Hayim Lapin <hl...@um...> wrote:
>>>
>>>> Hello list,
>>>> I am trying to install exist 6.0.1 on a new computer running windows
>>>> 11. I can successfully run exist-installer-6.0.1.jar, and can start up from
>>>> the windows icon, but I only get as far as the first-use screen. After
>>>> that, nothing; exist does not start.
>>>> Any suggestions about how to troubleshoot this?
>>>>
>>>> Many thanks,
>>>> HL
>>>>
>>>> _______________________________________________
>>>> Exist-open mailing list
>>>> Exi...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>
>>> --
>>> Sent from my iPhone
>>>
>>

Re: [Exist-open] New installation on Windows 11

[Hayim L. <hl...@um...>]

Hello all, I am circling back to see if anyone has experienced this
installation problem.
I have updated Java to the latest version and run the startup script with
admin privileges.
Now I encounter the following error:
Cannot run program C:\path\to\java.javaw.exe (in director
C:\path\to\exist): CreateProcess error=206, The filename or extension is
too long

Many thanks!
HL

On Wed, Oct 12, 2022 at 8:23 PM Hayim Lapin <hl...@um...> wrote:

> Java(TM) SE Runtime Environment (build 1.8.0_341-b10)
> Do I need the jdk?
>
> On Wed, Oct 12, 2022 at 7:10 PM Joe Wicentowski <jo...@gm...> wrote:
>
>> Which version of Java is installed?
>>
>> On Wed, Oct 12, 2022 at 4:39 PM Hayim Lapin <hl...@um...> wrote:
>>
>>> Hello list,
>>> I am trying to install exist 6.0.1 on a new computer running windows 11.
>>> I can successfully run exist-installer-6.0.1.jar, and can start up from the
>>> windows icon, but I only get as far as the first-use screen. After that,
>>> nothing; exist does not start.
>>> Any suggestions about how to troubleshoot this?
>>>
>>> Many thanks,
>>> HL
>>>
>>> _______________________________________________
>>> Exist-open mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>
>> --
>> Sent from my iPhone
>>
>

Re: [Exist-open] xqDoc - potential updates

[Omar S. <Oma...@oe...>]

Hi,

You can also have a look at this:
https://github.com/acdh-oeaw/openapi4restxq

I didn't do most of it the original is at.
https://gitlab.gwdg.de/subugoe/openapi4restxq

Am 19.10.2022 um 16:17 schrieb Loren Cahlander:
> Hello folks,
>
> I am looking at maybe doing some updates to the xqDoc spec and the 
> codebase.  I have code that transforms the xqDoc resources with RestXQ 
> into an OpenAPI 3 API documentation.  The things that I want to figure 
> out is:
>
>   * Figure out how to specify the schema of the parameters and the return
>   * Document the various HTTP return codes and the response content
>     for each return code
>
>
> I would like to get the input from everyone using xqDoc
>
> Thank you,
> Loren
Best regards

-- 
Mag. Ing. Omar Siam
Austrian Center for Digital Humanities and Cultural Heritage
Österreichische Akademie der Wissenschaften | Austrian Academy of Sciences
Stellvertretende Behindertenvertrauensperson | Deputy representative for disabled persons
Bäckerstraße 13, 1010 Wien, Österreich | Vienna, Austria
T: +43 1 51581-7295
oma...@oe...  |www.oeaw.ac.at/acdh

[Exist-open] xqDoc - potential updates

[Loren C. <lor...@gm...>]

Hello folks,

I am looking at maybe doing some updates to the xqDoc spec and the codebase.  I have code that transforms the xqDoc resources with RestXQ into an OpenAPI 3 API documentation.  The things that I want to figure out is:

Figure out how to specify the schema of the parameters and the return
Document the various HTTP return codes and the response content for each return code

I would like to get the input from everyone using xqDoc

Thank you,
Loren

Re: [Exist-open] Exist Xquery Wait and Receive Times

[IonutzC <rev...@ya...>]

 I think you are right on the logic behind this, but I still think it's more of an eXist specific issue. I took the result, duplicated it 5 or six 6 times and put the xml in a file, wrote a php script and asked it to retrieve the contents and show it in the browser. All of this on the same server.
In the end, the receiving time for this file is under 1 seconds with php, so it still appears there is an issue somewhere that concerns eXist in particular.
Cheers.

    On Saturday, October 15, 2022 at 05:59:21 PM GMT+2, Nick Sincaglia <nsi...@nu...> wrote:  
 
  This is just a guess but 6MB of XML data might take a time for the browser to render. If you run the same script in "View Source" mode, it might not try to render the XML and might display the data within 2 to 3 seconds again. 
 
 Nick
 
 On 10/15/22 2:10 AM, IonutzC via Exist-open wrote:
  
 
 Hello folks, 
  I noticed a weird issue concerning .xql calls (via AJAX, but the same happens when I run them directly in the browser). I have a query and if I check it in eXide it takes about 3 to 4 seconds of waiting time and 2 to 3 seconds of receiving time. The overall result is 6MB, so not the smallest but also not the largest amount of data to transfer. 
  Now, the weird thing is that whenever I call the same .xql via AJAX (or, like I mentioned above, if I simply load it in the browser), the waiting time grows considerably, like 5 or 6 seconds extra, making the whole request incredibly slow. I checked the profiling tool in monex and it still shows the low number I get in eXide rather than the realistic time it takes to get the data. So either the serialization process or the data transfer issue is creating a problem. In any case, as far as I can tell there is nothing wrong with my script but rather eXist as a whole appears to be causing and issue somewhere or I am doing something incorrectly and I am not aware of it. 
  Did anyone run into anything similar or do you have any suggestion how one might go around tackling this? 
  Cheers!  
  
  _______________________________________________
Exist-open mailing list
Exi...@li...
https://lists.sourceforge.net/lists/listinfo/exist-open
 
 -- 
Nick Sincaglia 
President/Founder
NueMeta, LLC
Digital Media & Technology
Phone: +1-630-303-7035
nsi...@nu... 
http://www.nuemeta.com
Skype: nsincaglia _______________________________________________
Exist-open mailing list
Exi...@li...
https://lists.sourceforge.net/lists/listinfo/exist-open
  

Re: [Exist-open] Exist Xquery Wait and Receive Times

[Nick S. <nsi...@nu...>]

This is just a guess but 6MB of XML data might take a time for the 
browser to render. If you run the same script in "View Source" mode, it 
might not try to render the XML and might display the data within 2 to 3 
seconds again.

Nick

On 10/15/22 2:10 AM, IonutzC via Exist-open wrote:
> Hello folks,
>
> I noticed a weird issue concerning .xql calls (via AJAX, but the same 
> happens when I run them directly in the browser). I have a query and 
> if I check it in eXide it takes about 3 to 4 seconds of waiting time 
> and 2 to 3 seconds of receiving time. The overall result is 6MB, so 
> not the smallest but also not the largest amount of data to transfer.
>
> Now, the weird thing is that whenever I call the same .xql via AJAX 
> (or, like I mentioned above, if I simply load it in the browser), the 
> waiting time grows considerably, like 5 or 6 seconds extra, making the 
> whole request incredibly slow. I checked the profiling tool in monex 
> and it still shows the low number I get in eXide rather than the 
> realistic time it takes to get the data. So either the serialization 
> process or the data transfer issue is creating a problem. In any case, 
> as far as I can tell there is nothing wrong with my script but rather 
> eXist as a whole appears to be causing and issue somewhere or I am 
> doing something incorrectly and I am not aware of it.
>
> Did anyone run into anything similar or do you have any suggestion how 
> one might go around tackling this?
>
> Cheers!
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

-- 
Nick Sincaglia
President/Founder
NueMeta, LLC
Digital Media & Technology
Phone: +1-630-303-7035
nsi...@nu...  
http://www.nuemeta.com
Skype: nsincaglia

[Exist-open] Exist Xquery Wait and Receive Times

[IonutzC <rev...@ya...>]

Hello folks,
I noticed a weird issue concerning .xql calls (via AJAX, but the same happens when I run them directly in the browser). I have a query and if I check it in eXide it takes about 3 to 4 seconds of waiting time and 2 to 3 seconds of receiving time. The overall result is 6MB, so not the smallest but also not the largest amount of data to transfer.
Now, the weird thing is that whenever I call the same .xql via AJAX (or, like I mentioned above, if I simply load it in the browser), the waiting time grows considerably, like 5 or 6 seconds extra, making the whole request incredibly slow. I checked the profiling tool in monex and it still shows the low number I get in eXide rather than the realistic time it takes to get the data. So either the serialization process or the data transfer issue is creating a problem. In any case, as far as I can tell there is nothing wrong with my script but rather eXist as a whole appears to be causing and issue somewhere or I am doing something incorrectly and I am not aware of it.
Did anyone run into anything similar or do you have any suggestion how one might go around tackling this?
Cheers!

Re: [Exist-open] New installation on Windows 11

[Hayim L. <hl...@um...>]

I have tried regressing to exist 5.4.1 and receive this message at the end
of first run:
Cannot run program """"C:\ ….[java install directory] javaw.exe"""" (in …
[exist 5.4.1 installation directory]): CreateProcess error=206, The
filename or extension is too long.

I *can* start from the startup.bat file, but without the system tray
utilities.

On Wed, Oct 12, 2022 at 8:23 PM Hayim Lapin <hl...@um...> wrote:

> Java(TM) SE Runtime Environment (build 1.8.0_341-b10)
> Do I need the jdk?
>
> On Wed, Oct 12, 2022 at 7:10 PM Joe Wicentowski <jo...@gm...> wrote:
>
>> Which version of Java is installed?
>>
>> On Wed, Oct 12, 2022 at 4:39 PM Hayim Lapin <hl...@um...> wrote:
>>
>>> Hello list,
>>> I am trying to install exist 6.0.1 on a new computer running windows 11.
>>> I can successfully run exist-installer-6.0.1.jar, and can start up from the
>>> windows icon, but I only get as far as the first-use screen. After that,
>>> nothing; exist does not start.
>>> Any suggestions about how to troubleshoot this?
>>>
>>> Many thanks,
>>> HL
>>>
>>> _______________________________________________
>>> Exist-open mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>
>> --
>> Sent from my iPhone
>>
>

Re: [Exist-open] New installation on Windows 11

[Hayim L. <hl...@um...>]

Java(TM) SE Runtime Environment (build 1.8.0_341-b10)
Do I need the jdk?

On Wed, Oct 12, 2022 at 7:10 PM Joe Wicentowski <jo...@gm...> wrote:

> Which version of Java is installed?
>
> On Wed, Oct 12, 2022 at 4:39 PM Hayim Lapin <hl...@um...> wrote:
>
>> Hello list,
>> I am trying to install exist 6.0.1 on a new computer running windows 11.
>> I can successfully run exist-installer-6.0.1.jar, and can start up from the
>> windows icon, but I only get as far as the first-use screen. After that,
>> nothing; exist does not start.
>> Any suggestions about how to troubleshoot this?
>>
>> Many thanks,
>> HL
>>
>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
> --
> Sent from my iPhone
>

Re: [Exist-open] New installation on Windows 11

[Joe W. <jo...@gm...>]

Which version of Java is installed?

On Wed, Oct 12, 2022 at 4:39 PM Hayim Lapin <hl...@um...> wrote:

> Hello list,
> I am trying to install exist 6.0.1 on a new computer running windows 11. I
> can successfully run exist-installer-6.0.1.jar, and can start up from the
> windows icon, but I only get as far as the first-use screen. After that,
> nothing; exist does not start.
> Any suggestions about how to troubleshoot this?
>
> Many thanks,
> HL
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
-- 
Sent from my iPhone

[Exist-open] New installation on Windows 11

[Hayim L. <hl...@um...>]

Hello list,
I am trying to install exist 6.0.1 on a new computer running windows 11. I
can successfully run exist-installer-6.0.1.jar, and can start up from the
windows icon, but I only get as far as the first-use screen. After that,
nothing; exist does not start.
Any suggestions about how to troubleshoot this?

Many thanks,
HL

Re: [Exist-open] Fwd: Errors deploying collection

[Nick S. <nsi...@nu...>]

Hayim,
     We use the Expath http-client a lot. Based on the small amount of 
code that you have pasted below, I can share some code snippets that we 
might use to do something similar. The below code has been pulled from 
various files and has not been tested but my hope is that it is close 
enough to help you identify how to use the http-client library to get 
the results you are looking for.

import module namespace http = "http://expath.org/ns/http-client";
import module namespace jx = "http://joewiz.org/ns/xquery/json-xml" at 
"../../../core/json-xml/modules/json-xml.xqm";
let $constructed-url := "http://52.12.26.11:8080/collatex/collate"
let $headers := <http:header name="Content-Type" value="application/json"/>
     (:
         NOTE: headers should be formatted the following way (they do 
not use a parent tag)
<http:header>...</http:header>
<http:header>...</http:header>
     :)

     let $get-request :=
         <http:request href="{$constructed-url}" method="GET">
             <http:header name="Connection" value= "close"/>
             {$headers}
         </http:request>

     let $response := http:send-request($get-request)
     let $response-body-decoded := util:base64-decode($response[2])
     let $parse-response-body := 
jx:json-to-xml(xs:string($response-body-decoded))
     return
         $parse-response-body

Does this help? If you have more questions, let me know. I am happy to help.

Nick

On 10/11/22 11:52 AM, Hayim Lapin wrote:
> Dear list,
> This is technically an expath problem rather than an eXist problem, 
> but I was hoping that the accumulated knowledge on the list might 
> provide a quick fix and that this is not list abuse.
>
> I am upgrading an app from eXist version 4 to 5+ and need to rewrite 
> an http-post request in one function from the older http-client to the 
> new expath http client. In the attached xql file the post request 
> begins at line 102.
>
> My attempted rewrite is wrong. I've tried the following, where $tokens 
> is a json represntation of textual data from which CollateX 
> <https://collatex.net> generates an alignment table that is returned 
> in json as $results
>
> let $results := parse-json(
>         content:get-metadata-and-content(
> http:send-request(<http:request 
> href="http://52.12.26.11:8080/collatex/collate" method="post">
>         <http:body media-type="text/plain" 
> content-type="text/plain">{($tokens,$headers)}</http:body>
>         </http:request>
>         )))
>         return ... (: do stuff with $results :)
>
> Unfortunately, I cannot figure out how to address the error report 
> ("Invalid attributes") that eXist returns.
>
>     /db/apps/digitalmishnah/modules/view.xqlerr:XPTY0004 checking
>     function parameter 1 in call
>     contentextraction:get-metadata-and-content(untyped-value-check[xs:base64Binary,
>     hc:send-request(element {"http:request"} { attribute {href} {
>     http://52.12.26.11:8080/collatex/collate } attribute {method} {
>     post } text { } element {"http:body"} { attribute {media-type} {
>     text/plain } attribute {content-type} { text/plain } { ( $tokens,
>     $headers ) } } text { } } )]): Invalid attributes [at line 106,
>     column 9] In function: cmp:compare-mishnah(node(), xs:string,
>     xs:string*, xs:string)
>     [41:7:/db/apps/digitalmishnah/modules/compare.xql]
>     cmp:compare-view(node(), map(*))
>     [-1:-1:/db/apps/digitalmishnah/modules/compare.xql]
>     templates:process-output(element(), map(*), item()*,
>     element(function))
>     [211:9:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:call-by-introspection(element(), map(*), map(*),
>     function(*))
>     [189:28:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:call(item(), element(), map(*))
>     [137:36:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [428:17:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process-output(element(), map(*), item()*)
>     [230:9:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process-output(element(), map(*), item()*,
>     element(function))
>     [211:9:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:call-by-introspection(element(), map(*), map(*),
>     function(*))
>     [189:28:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:call(item(), element(), map(*))
>     [137:36:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [133:51:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:process(node()*, map(*))
>     [90:9:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>     templates:apply(node()+, function(*), map(*)?, map(*)?)
>     [53:5:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
>
>
> I'd be truly grateful for any pointers.
>
> Many thanks,
> HL
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

-- 
Nick Sincaglia
President/Founder
NueMeta, LLC
Digital Media & Technology
Phone: +1-630-303-7035
nsi...@nu...  
http://www.nuemeta.com
Skype: nsincaglia

[Exist-open] Fwd: Errors deploying collection

[Hayim L. <hl...@um...>]

Dear list,
This is technically an expath problem rather than an eXist problem, but I
was hoping that the accumulated knowledge on the list might provide a quick
fix and that this is not list abuse.

I am upgrading an app from eXist version 4 to 5+ and need to rewrite an
http-post request in one function from the older http-client to the new
expath http client. In the attached xql file the post request begins at
line 102.

My attempted rewrite is wrong. I've tried the following, where $tokens is a
json represntation of textual data from which CollateX
<https://collatex.net> generates an alignment table that is returned in
json as $results

let $results := parse-json(
        content:get-metadata-and-content(
        http:send-request(<http:request href="
http://52.12.26.11:8080/collatex/collate" method="post">
        <http:body media-type="text/plain"
content-type="text/plain">{($tokens,$headers)}</http:body>
        </http:request>
        )))
        return ... (: do stuff with $results :)

Unfortunately, I cannot figure out how to address the error report
("Invalid attributes") that eXist returns.

/db/apps/digitalmishnah/modules/view.xqlerr:XPTY0004 checking function
> parameter 1 in call
> contentextraction:get-metadata-and-content(untyped-value-check[xs:base64Binary,
> hc:send-request(element {"http:request"} { attribute {href} {
> http://52.12.26.11:8080/collatex/collate } attribute {method} { post }
> text { } element {"http:body"} { attribute {media-type} { text/plain }
> attribute {content-type} { text/plain } { ( $tokens, $headers ) } } text {
> } } )]): Invalid attributes [at line 106, column 9] In function:
> cmp:compare-mishnah(node(), xs:string, xs:string*, xs:string)
> [41:7:/db/apps/digitalmishnah/modules/compare.xql] cmp:compare-view(node(),
> map(*)) [-1:-1:/db/apps/digitalmishnah/modules/compare.xql]
> templates:process-output(element(), map(*), item()*, element(function))
> [211:9:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:call-by-introspection(element(), map(*), map(*), function(*))
> [189:28:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:call(item(), element(), map(*))
> [137:36:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [148:81:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [428:17:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process-output(element(), map(*), item()*)
> [230:9:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process-output(element(), map(*), item()*, element(function))
> [211:9:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:call-by-introspection(element(), map(*), map(*), function(*))
> [189:28:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:call(item(), element(), map(*))
> [137:36:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [133:51:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:process(node()*, map(*))
> [90:9:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]
> templates:apply(node()+, function(*), map(*)?, map(*)?)
> [53:5:C:\users\hlapin\eXist-db-6.0.1\data\expathrepo\shared-0.9.1\content\templates.xql]


I'd be truly grateful for any pointers.

Many thanks,
HL

[Exist-open] [ANN] Updated XARs for JDBC drivers

[Loren C. <lor...@gm...>]

I have updated the JDBC driver files based on the version number from the various JDBC drivers.

https://github.com/eXist-db/exist-snowflake-jdbc-driver/releases/tag/v3.13.23 <https://github.com/eXist-db/exist-snowflake-jdbc-driver/releases/tag/v3.13.23>
https://github.com/eXist-db/exist-mariadb-jdbc-driver/releases/tag/v3.0.8 <https://github.com/eXist-db/exist-mariadb-jdbc-driver/releases/tag/v3.0.8>
https://github.com/eXist-db/exist-mssql-jdbc-driver/releases/tag/v11.2.1.jre8 <https://github.com/eXist-db/exist-mssql-jdbc-driver/releases/tag/v11.2.1.jre8>
https://github.com/eXist-db/exist-ojdbc10-jdbc-driver/releases/tag/v19.16.0.0 <https://github.com/eXist-db/exist-ojdbc10-jdbc-driver/releases/tag/v19.16.0.0>
https://github.com/eXist-db/exist-ojdbc8-jdbc-driver/releases/tag/v21.7.0.0 <https://github.com/eXist-db/exist-ojdbc8-jdbc-driver/releases/tag/v21.7.0.0>
https://github.com/eXist-db/exist-postgresql-jdbc-driver/releases/tag/v42.5.0 <https://github.com/eXist-db/exist-postgresql-jdbc-driver/releases/tag/v42.5.0>
https://github.com/eXist-db/exist-mysql-jdbc-driver/releases/tag/v8.0.30 <https://github.com/eXist-db/exist-mysql-jdbc-driver/releases/tag/v8.0.30>
I will make sure that when new versions are released for each JDBC driver that the XAR version is created and released.

[Exist-open] Declarative Amsterdam 2022 - Register now!

[Erik S. <er...@xa...>]

On 7 and 8 November Declarative Amsterdam is going to take place at CWI, Science Park, Amsterdam.

The Program for Declarative Amsterdam 2022 <https://declarative.amsterdam/program>  is official.
It features tutorials and presentations on languages and tools such as RumbleDB, Schematron, Fore, ixml, SQL, XProc, ePub, and various other topics in the field of declarative programming and declarative data. Speakers are Achim Berndzen, Diederik Gerth van Wijk, Erik Siegel, G. Ken Holman, Geert Bormans, Ghislain Fourny, Günter Burgstaller, Joep Meindertsma, Joern Turner, Juri Leino, Liam Quin, Maggie Appleton, Manuel Meyer, and Steven Pemberton.

The conference will be hybrid: you can attend on-site or via Zoom. Register now at: https://declarative.amsterdam/registration. Please note that there is a discount available for early birds.

We hope to see you there, either in person or virtually! Also, please tell friends and colleagues. We think the tutorials will be interesting for students, so do inform them as well.
Lastly, do not forget to participate in the Challenge <https://declarative.amsterdam/challenge> .

Best wishes,

The Declarative Amsterdam Conference Committee.

 

Re: [Exist-open] Asynchronous xmldb:store()?

[Dominic L. <dom...@gm...>]

Dear All,

For me it is also a problem that updates can take so long, both storing and
updating files. I'd say that a primary limitation of exist as an enterprise
platform is that updating a single node in a large file is way too slow.
So if anybody has any tips on speeding up stores please respond to the
thread.

Having said that, where appropriate I use this function to make
asynchronous calls using the scheduler. It seems like a workaround but it
works ok. Perhaps the exist team should wrap
scheduler:schedule-xquery-periodic-job() in a function called
scheduler:run-async() as an easy way to offer async natively?

declare function local:async-script($script-name as xs:string, $parameters
as element(parameters)?){

    (: Clear job if completed :)
    let $clear-complete-job :=
        if(scheduler:get-scheduled-jobs()//scheduler:job[@name eq
$script-name][scheduler:trigger/state/text() eq 'COMPLETE']) then
            scheduler:delete-scheduled-job($script-name)
        else ()

    (: Only schedule if not already there :)
    where not(scheduler:get-scheduled-jobs()//scheduler:job[@name eq
$script-name])
    return (
        (: Log so we can monitor :)
        util:log('info', concat('async-script:', $script-name)),
        (: Schedule a one-off job :)
        scheduler:schedule-xquery-periodic-job(
            concat('/db/apps/scripts/', $script-name, '.xq'),
            10000,
            $script-name,
            $parameters,
            5000,
            0
        )
    )
};

With best wishes,
Dominic



On Thu, 15 Sept 2022 at 05:32, Lizzi, Vincent <
Vin...@ta...> wrote:

> I have what seems like a very similar question: is there any way to make
> xmldb:store faster?
>
>
>
> I’ve been observing, in a long-running process that stores thousands of
> documents at a time, is that as the database grows in size the time that it
> takes to store documents increases.
>
>
>
> I thought about removing the collection index configuration temporarily to
> store documents first and then run reindex as a second step. However, the
> reindex process can take days on a large collection and there are no
> progress indicators to show whether the reindex is working or hung, so this
> doesn’t seem like a good option.
>
>
>
> Are there any suggestions on what could be done to make xmldb:store faster
> or asynchronous?
>
>
>
> Thanks,
>
> Vincent
>
>
>
> _____________________________________________
>
> *Vincent M. Lizzi*
>
> Head of Information Standards | Taylor & Francis Group
>
> vin...@ta...
>
>
>
>
>
>
>
> Information Classification: General
>
> *From:* Len Schultz <le...@wi...>
> *Sent:* Wednesday, September 14, 2022 4:20 AM
> *To:* Craig Berry via Exist-open <exi...@li...>
> *Subject:* [Exist-open] Asynchronous xmldb:store()?
>
>
>
> Is there a way to have an XQuery script execute a xmldb:store(), then
> return data without waiting for the store to complete?  My queries can
> create rather large XML variables that I’d like to save for debugging,
> logging, and later inspection.  The stores can take quite a bit of time.
> So I’d like to avoid the performance hit of storing the document on the
> query latency, and therefore the application latency.  Any suggestions for
> how to implement an asynchronous store?
>
>
>
> --len
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] mac os launch issue

[Dannes W. <di...@ex...>]

M1 is actually Apple’s ARM based processor… as opposed to Intel;

I suspect that in general that processor platform has still some quirks…

D.

> On 12 Sep 2022, at 21:19, Paul Kelly <pa...@po...> wrote:
> 
> Sorry, dropped the ball here. Not ARM, it’s Apple M1 Pro

Re: [Exist-open] Asynchronous xmldb:store()?

[Lizzi, V. <Vin...@ta...>]

I have what seems like a very similar question: is there any way to make xmldb:store faster?

I've been observing, in a long-running process that stores thousands of documents at a time, is that as the database grows in size the time that it takes to store documents increases.

I thought about removing the collection index configuration temporarily to store documents first and then run reindex as a second step. However, the reindex process can take days on a large collection and there are no progress indicators to show whether the reindex is working or hung, so this doesn't seem like a good option.

Are there any suggestions on what could be done to make xmldb:store faster or asynchronous?

Thanks,
Vincent

_____________________________________________
Vincent M. Lizzi
Head of Information Standards | Taylor & Francis Group
vin...@ta...<mailto:vin...@ta...>




Information Classification: General
From: Len Schultz <le...@wi...>
Sent: Wednesday, September 14, 2022 4:20 AM
To: Craig Berry via Exist-open <exi...@li...>
Subject: [Exist-open] Asynchronous xmldb:store()?

Is there a way to have an XQuery script execute a xmldb:store(), then return data without waiting for the store to complete?  My queries can create rather large XML variables that I'd like to save for debugging, logging, and later inspection.  The stores can take quite a bit of time.  So I'd like to avoid the performance hit of storing the document on the query latency, and therefore the application latency.  Any suggestions for how to implement an asynchronous store?

--len

[Exist-open] Alternate unique identifier generators

[Loren C. <lor...@gm...>]

Hello folks,

I have created a installable package with a library module to generate alternate unique identifiers. https://github.com/lcahlander/exist-alt-identifier <https://github.com/lcahlander/exist-alt-identifier>

I would like to transfer this repository over to eXist-db control.  I would like your input before I do that.  I am using ULID https://github.com/ulid/spec <https://github.com/ulid/spec> in my current application.  I can add additional alternate unique identifiers if the community requests, otherwise I have a security update that I have added to create a new version of the XAR.  I would also like to have the XAR added to the package manager.

https://github.com/lcahlander/exist-alt-identifier/releases/tag/v1.0.1 <https://github.com/lcahlander/exist-alt-identifier/releases/tag/v1.0.1>

All the best,
Loren

[Exist-open] Asynchronous xmldb:store()?

[Len S. <le...@wi...>]

Is there a way to have an XQuery script execute a xmldb:store(), then return data without waiting for the store to complete?  My queries can create rather large XML variables that I’d like to save for debugging, logging, and later inspection.  The stores can take quite a bit of time.  So I’d like to avoid the performance hit of storing the document on the query latency, and therefore the application latency.  Any suggestions for how to implement an asynchronous store?

--len

Re: [Exist-open] mac os launch issue

[Alasdair D. <ala...@gm...>]

Hi Paul,

Interesting.  I’m about to upgrade to a MacBook Air M2.  

Have you installed the Oracle Java or did you use OpenJDK?  I found that OpenJDK is more likely to work.  Also, install MacPorts or Home Brew.

Alasdair 

Sent from my iPhone

> On 13 Sep 2022, at 5:20 am, Paul Kelly <pa...@po...> wrote:
> 
> 
> Sorry, dropped the ball here. Not ARM, it’s Apple M1 Pro
> 
> Had trouble getting older versions of java to work on the mac so I’m using an AWS instance now
> 
> 
>> On Aug 24, 2022, at 11:50 AM, Juri Leino <ju...@ex...> wrote:
>> 
>> Is this an arm Mac?
>> 
>>> On 23. August 2022 at 20:40:56, Paul Kelly (pa...@po...) wrote:
>>> 
>>> Nothing to do with notarization I think. Maybe to do with 32/64 bit as I’m told exit(13) is all about?
>>> 
>>> In any case, eXist will not launch on my MacBook Pro. Anyone else experienced this? 
>>> 
>>> 2022-08-23 14:22:07.988069 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: internal event: WILL_SPAWN, code = 0
>>> 2022-08-23 14:22:07.988072 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: service state: spawn scheduled
>>> 2022-08-23 14:22:07.988073 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: service state: spawning
>>> 2022-08-23 14:22:07.988090 <Notice>: Coalition Cache Hit: app<application.org.exist.start.Main.52363637.52363935(501)> [791]
>>> 2022-08-23 14:22:07.988261 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: launching: non-ipc demand
>>> 2022-08-23 14:22:07.988830 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: xpcproxy spawned with pid 2870
>>> 2022-08-23 14:22:07.988846 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: internal event: SPAWNED, code = 0
>>> 2022-08-23 14:22:07.988848 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: service state: xpcproxy
>>> 2022-08-23 14:22:07.988872 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: internal event: SOURCE_ATTACH, code = 0
>>> 2022-08-23 14:22:07.998761 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: service state: running
>>> 2022-08-23 14:22:07.998784 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: internal event: INIT, code = 0
>>> 2022-08-23 14:22:07.998790 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: job state = running
>>> 2022-08-23 14:22:07.998846 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: Successfully spawned eXist-JavaAppLauncher[2870] because non-ipc demand
>>> 2022-08-23 14:22:08.363624 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: exited due to exit(13)
>>> 2022-08-23 14:22:08.363641 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: service state: exited
>>> 2022-08-23 14:22:08.363645 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: internal event: EXITED, code = 0
>>> 2022-08-23 14:22:08.363649 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: job state = exited
>>> 2022-08-23 14:22:08.363681 (gui/501 [100004]) <Notice>: service inactive: application.org.exist.start.Main.52363637.52363935
>>> 2022-08-23 14:22:08.363685 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: service state: not running
>>> 2022-08-23 14:22:08.364400 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: removing job: caller = runningboardd
>>> 2022-08-23 14:22:08.364409 (gui/501 [100004]) <Notice>: removing service: application.org.exist.start.Main.52363637.52363935
>>> 2022-08-23 14:22:08.364544 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: internal event: PETRIFIED, code = 0
>>> 2022-08-23 14:22:08.364548 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: job state = removed
>>> 
>>> 
>>> Thanks,
>>> 
>>> Paul
>>> _______________________________________________ 
>>> Exist-open mailing list 
>>> Exi...@li... 
>>> https://lists.sourceforge.net/lists/listinfo/exist-open 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] mac os launch issue

[Paul K. <pa...@po...>]

Sorry, dropped the ball here. Not ARM, it’s Apple M1 Pro

Had trouble getting older versions of java to work on the mac so I’m using an AWS instance now


> On Aug 24, 2022, at 11:50 AM, Juri Leino <ju...@ex...> wrote:
> 
> Is this an arm Mac?
> 
> On 23. August 2022 at 20:40:56, Paul Kelly (pa...@po... <mailto:pa...@po...>) wrote:
> 
>> Nothing to do with notarization I think. Maybe to do with 32/64 bit as I’m told exit(13) is all about?
>> 
>> In any case, eXist will not launch on my MacBook Pro. Anyone else experienced this? 
>> 
>> 2022-08-23 14:22:07.988069 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: internal event: WILL_SPAWN, code = 0
>> 2022-08-23 14:22:07.988072 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: service state: spawn scheduled
>> 2022-08-23 14:22:07.988073 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: service state: spawning
>> 2022-08-23 14:22:07.988090 <Notice>: Coalition Cache Hit: app<application.org.exist.start.Main.52363637.52363935(501)> [791]
>> 2022-08-23 14:22:07.988261 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: launching: non-ipc demand
>> 2022-08-23 14:22:07.988830 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: xpcproxy spawned with pid 2870
>> 2022-08-23 14:22:07.988846 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: internal event: SPAWNED, code = 0
>> 2022-08-23 14:22:07.988848 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: service state: xpcproxy
>> 2022-08-23 14:22:07.988872 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: internal event: SOURCE_ATTACH, code = 0
>> 2022-08-23 14:22:07.998761 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: service state: running
>> 2022-08-23 14:22:07.998784 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: internal event: INIT, code = 0
>> 2022-08-23 14:22:07.998790 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: job state = running
>> 2022-08-23 14:22:07.998846 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: Successfully spawned eXist-JavaAppLauncher[2870] because non-ipc demand
>> 2022-08-23 14:22:08.363624 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: exited due to exit(13)
>> 2022-08-23 14:22:08.363641 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: service state: exited
>> 2022-08-23 14:22:08.363645 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: internal event: EXITED, code = 0
>> 2022-08-23 14:22:08.363649 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: job state = exited
>> 2022-08-23 14:22:08.363681 (gui/501 [100004]) <Notice>: service inactive: application.org.exist.start.Main.52363637.52363935
>> 2022-08-23 14:22:08.363685 (gui/501/application.org.exist.start.Main.52363637.52363935 [2870]) <Notice>: service state: not running
>> 2022-08-23 14:22:08.364400 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: removing job: caller = runningboardd
>> 2022-08-23 14:22:08.364409 (gui/501 [100004]) <Notice>: removing service: application.org.exist.start.Main.52363637.52363935
>> 2022-08-23 14:22:08.364544 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: internal event: PETRIFIED, code = 0
>> 2022-08-23 14:22:08.364548 (gui/501/application.org.exist.start.Main.52363637.52363935) <Notice>: job state = removed
>> 
>> 
>> Thanks,
>> 
>> Paul
>> _______________________________________________ 
>> Exist-open mailing list 
>> Exi...@li... <mailto:Exi...@li...> 
>> https://lists.sourceforge.net/lists/listinfo/exist-open <https://lists.sourceforge.net/lists/listinfo/exist-open> 

[Exist-open] Support for old versions

[L'omobob <sa...@gm...>]

Hello !

Is there some official schedule about security update and support for every
version, with a long term vision (2 or 3 years ahead) ?

Thanks !