exist-open — Open discussion

[Exist-open] Counter-intuitive performance results with transform:transform() - Saxon

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

Hello eXisters,

I was running some simple performance benchmarks to decide how best to optimize a new app, and ran into an unexpected result.

I wanted to see how much faster it was to read a large XML file from the db and pass to Saxon compared to dynamically generating the XML file from an SQL query.  I assumed  the latter would be slower, and I wanted to quantify how much.  But to my surprise, generating the XML file dynamically was an order of magnitude faster in Saxon.

To setup the test, I created big.sql.xml in the database by running the SQL query:

let $big := sql:execute($connection, 'SELECT * FROM lists LIMIT 30000', fn:true())
return xmldb:store('/db/', 'big.sql.xml', $big)

This took 61.8s, with 3.1s for sql:execute() and 58.2s for xmldb:store().  The file size in the database is 167MB.  I don’t care about the slow store time, as this is just a test.

First, I did a simple transform using the saved file:

let $xsl := doc('/db/test.xsl')
let $big := doc('/db/big.sql.xml')
return transform:transform($big, $xsl, ())

This took 8.9s, with 8.9s for transform:transform().

Second, I dynamically ran the SQL query, passing that into the transform:

let $xsl := doc('/db/test.xsl')
let $big := sql:execute($connection, 'SELECT * FROM lists LIMIT 30000', fn:true())
return transform:transform($big, $xsl, ())

This took 4.0s, with 3.1s for sql:execute() and 0.9s for transform:transform().

I was expecting the 3.1s to be added, which it was.  But I was not expecting transform:transform() to drop from 8.9s to 0.9s, a 90% reduction in execution time.  So I’m missing something fundamental about how this works.  Obviously, I’d love to get the 0.9s performance in the first case, while replacing the 3.1s of sql:execute() time with what I assumed would be a much faster doc().

Any insight?

--len

FYI, the simple transform in test.xsl is:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sql="http://exist-db.org/xquery/sql" exclude-result-prefixes="sql" version="3.0" expand-text="yes">
<xsl:output method="xml" version="1.0" encoding=“utf-8" indent="yes"/>
<xsl:mode on-no-match="shallow-skip"/>

<xsl:template match="/sql:result">
<test>
<xsl:sequence select="@*"/>
</test>
</xsl:template>

</xsl:stylesheet>

Re: [Exist-open] mac os launch issue

[Juri L. <ju...@ex...>]

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
>

Re: [Exist-open] mac os launch issue

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

Please use java11 on max;

Newer versions are not yet supported :(

Cheers

Dannes

> On 23 Aug 2022, at 22:54, Paul Kelly <pa...@po...> wrote:
> 
> 
> Thanks. FWIW:
> 
> Pauls-MacBook-Pro-2:auto-tag paul$ java --version
> java 14.0.1 2020-04-14
> Java(TM) SE Runtime Environment (build 14.0.1+7)
> Java HotSpot(TM) 64-Bit Server VM (build 14.0.1+7, mixed mode, sharing)
> 
> 
>> On Aug 23, 2022, at 4:08 PM, Jean-Paul Rehr <re...@gm...> wrote:
>> 
>> There's probably more thorough responses forthcoming, but I believe that is a Java version issue. You'll need to make sure your Java corresponds with the requirements of eXist 6.
>> 
>>> On Tue, Aug 23, 2022 at 10:03 PM Paul Kelly <pa...@po...> wrote:
>>> Sorry, it’s been a while. Shame on me…
>>> 
>>> eXist: 6.0.1
>>> MacOS: 12.5.1
>>> 
>>> 
>>> 
>>>> On Aug 23, 2022, at 4:00 PM, Jean-Paul Rehr <re...@gm...> wrote:
>>>> 
>>>> Version eXist-db? Version MacOS?
>>>> 
>>>> On Tue, Aug 23, 2022 at 9:35 PM 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, it’s been a while. Shame on me…

eXist: 6.0.1
MacOS: 12.5.1



> On Aug 23, 2022, at 4:00 PM, Jean-Paul Rehr <re...@gm...> wrote:
> 
> Version eXist-db? Version MacOS?
> 
> On Tue, Aug 23, 2022 at 9:35 PM 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>

Re: [Exist-open] mac os launch issue

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

Thanks. FWIW:

Pauls-MacBook-Pro-2:auto-tag paul$ java --version
java 14.0.1 2020-04-14
Java(TM) SE Runtime Environment (build 14.0.1+7)
Java HotSpot(TM) 64-Bit Server VM (build 14.0.1+7, mixed mode, sharing)


> On Aug 23, 2022, at 4:08 PM, Jean-Paul Rehr <re...@gm...> wrote:
> 
> There's probably more thorough responses forthcoming, but I believe that is a Java version issue. You'll need to make sure your Java corresponds with the requirements of eXist 6.
> 
> On Tue, Aug 23, 2022 at 10:03 PM Paul Kelly <pa...@po... <mailto:pa...@po...>> wrote:
> Sorry, it’s been a while. Shame on me…
> 
> eXist: 6.0.1
> MacOS: 12.5.1
> 
> 
> 
>> On Aug 23, 2022, at 4:00 PM, Jean-Paul Rehr <re...@gm... <mailto:re...@gm...>> wrote:
>> 
>> Version eXist-db? Version MacOS?
>> 
>> On Tue, Aug 23, 2022 at 9:35 PM 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>
> 

Re: [Exist-open] mac os launch issue

[Jean-Paul R. <re...@gm...>]

There's probably more thorough responses forthcoming, but I believe that is
a Java version issue. You'll need to make sure your Java corresponds with
the requirements of eXist 6.

On Tue, Aug 23, 2022 at 10:03 PM Paul Kelly <pa...@po...> wrote:

> Sorry, it’s been a while. Shame on me…
>
> eXist: 6.0.1
> MacOS: 12.5.1
>
>
>
> On Aug 23, 2022, at 4:00 PM, Jean-Paul Rehr <re...@gm...> wrote:
>
> Version eXist-db? Version MacOS?
>
> On Tue, Aug 23, 2022 at 9:35 PM 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
>>
>
>

Re: [Exist-open] mac os launch issue

[Jean-Paul R. <re...@gm...>]

Version eXist-db? Version MacOS?

On Tue, Aug 23, 2022 at 9:35 PM 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] mac os launch issue

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

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

Re: [Exist-open] Creating Excel files in eXist-db?

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

Dear Len,

I implemented this https://github.com/foglcz/xsl-excel-engine
It works very well for us.

with best wishes,
Dominic


On Wed, 10 Aug 2022 at 14:50, Len Schultz <le...@wi...> wrote:

> Has anyone created XLSX files in eXist-db?  If so, please share some
> pointers.
>
> --len
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] Parallel transform performance tuning

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

Where can I see/control/test how many parallel XQL transactions and more importantly how many parallel XSL transforms can be done by Saxon on my server?  I’m sending transactions using REST.

  *   I see the database connection pools in etc/conf.xml at /exist/db-connection/pool/@max.  What are the implications of setting @max > 20?
  *   Where can I see/control the HTTP connection pools?  Is that in etc/jetty/jetty-threadpool.xml at /Configure/New/Set[@name=‘maxThreads’]?
  *   Are there any Saxon configuration settings that I should know about?

Any suggestions for how to test how well my machine responds to parallel XQL queries containing XSL transforms?  E.g. do you have any hints how to create a long-running XSL to see how well my server responds?

--len

Re: [Exist-open] Typeswitch Output Formatting

[Peter S. <st...@we...>]

Isn’t that the whitespace before and after the element <ExcludedDistributionChannel>?
You might try to apply your typeswitch function to only the child elements (not all nodes) of the <DealTerms>  and then reintroduce the indentation via serialization settings.

Cheers
Peter


> Am 18.08.2022 um 00:15 schrieb Adam Retter <ad...@ex...>:
> 
> I am not sure immediately why you get an extra line break. As an experiment if you replace "return ()" with "return text {}", do you see the same result?
> 
> On Tue, 16 Aug 2022, 03:53 Nick Sincaglia, <nsi...@nu... <mailto:nsi...@nu...>> wrote:
> I have wrote a Typeswitch function in which I want to remove an XML tag if it is present.
> 
> My typeswitch function looks something like this:
> 
>     for $node in $nodes
>     return
>         typeswitch ($node)
>             (:Ignore text and comments:)
>             case text() return $node
>             case comment() return $node
>             case element(ExcludedDistributionChannel) return ()
>             default return my-typeswitch-transform:dispatch-recurse($node)
> 
> My input looks something like this:
> let $input :=
>         <DealTerms>
>           <TerritoryCode>AD</TerritoryCode>
>           <ExcludedDistributionChannel>
>             <PartyName>
>               <FullName>Adaptr</FullName>
>             </PartyName>
>           </ExcludedDistributionChannel>
>           <PriceInformation>
>             <PriceRangeType>Budget</PriceRangeType>
>           </PriceInformation>
>           <ValidityPeriod>
>             <StartDateTime>2022-12-01T02:35:00Z</StartDateTime>
>           </ValidityPeriod>
>         </DealTerms>
> 
> When I look at my output, I get this:
> 
> let $output :=
>         <DealTerms>
>           <TerritoryCode>AD</TerritoryCode>
> 
>           <PriceInformation>
>             <PriceRangeType>Budget</PriceRangeType>
>           </PriceInformation>
>           <ValidityPeriod>
>             <StartDateTime>2022-12-01T02:35:00Z</StartDateTime>
>           </ValidityPeriod>
>         </DealTerms>
> 
> Is there anything I can do to remove the new line character from the output, which the typeswitch function seems to add?
> 
> I know that this white space is inconsequential to the processing of this document but if I could remove it, I would like to.
> 
> Nick
>  --
> Nick Sincaglia
> President/Founder
> NueMeta, LLC
> Digital Media & Technology
> Phone: +1-630-303-7035
> nsi...@nu... <mailto:nsi...@nu...>
> http://www.nuemeta.com <http://www.nuemeta.com/>
> Skype: nsincaglia
> _______________________________________________
> 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 mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] Typeswitch Output Formatting

[Adam R. <ad...@ex...>]

I am not sure immediately why you get an extra line break. As an experiment
if you replace "return ()" with "return text {}", do you see the same
result?

On Tue, 16 Aug 2022, 03:53 Nick Sincaglia, <nsi...@nu...> wrote:

> I have wrote a Typeswitch function in which I want to remove an XML tag if
> it is present.
>
> My typeswitch function looks something like this:
>
>     for $node in $nodes
>     return
>         typeswitch ($node)
>             (:Ignore text and comments:)
>             case text() return $node
>             case comment() return $node
>             case element(ExcludedDistributionChannel) return ()
>             default return my-typeswitch-transform:dispatch-recurse($node)
>
> My input looks something like this:
> let $input :=
>         <DealTerms>
>           <TerritoryCode>AD</TerritoryCode>
> *          <ExcludedDistributionChannel>*
> *            <PartyName>*
> *              <FullName>Adaptr</FullName>*
> *            </PartyName>*
> *          </ExcludedDistributionChannel>*
>           <PriceInformation>
>             <PriceRangeType>Budget</PriceRangeType>
>           </PriceInformation>
>           <ValidityPeriod>
>             <StartDateTime>2022-12-01T02:35:00Z</StartDateTime>
>           </ValidityPeriod>
>         </DealTerms>
>
> When I look at my output, I get this:
>
> let $output :=
>         <DealTerms>
>           <TerritoryCode>AD</TerritoryCode>
>
>           <PriceInformation>
>             <PriceRangeType>Budget</PriceRangeType>
>           </PriceInformation>
>           <ValidityPeriod>
>             <StartDateTime>2022-12-01T02:35:00Z</StartDateTime>
>           </ValidityPeriod>
>         </DealTerms>
>
> Is there anything I can do to remove the new line character from the
> output, which the typeswitch function seems to add?
>
> I know that this white space is inconsequential to the processing of this
> document but if I could remove it, I would like to.
>
> Nick
>
> --
> Nick Sincaglia
> President/Founder
> NueMeta, LLC
> Digital Media & Technology
> Phone: +1-...@nu... http://www.nuemeta.com
> Skype: nsincaglia
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] Typeswitch Output Formatting

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

I have wrote a Typeswitch function in which I want to remove an XML tag 
if it is present.

My typeswitch function looks something like this:

     for $node in $nodes
     return
         typeswitch ($node)
             (:Ignore text and comments:)
             case text() return $node
             case comment() return $node
             case element(ExcludedDistributionChannel) return ()
             default return my-typeswitch-transform:dispatch-recurse($node)

My input looks something like this:
let $input :=
         <DealTerms>
           <TerritoryCode>AD</TerritoryCode>
*          <ExcludedDistributionChannel>**
**            <PartyName>**
**              <FullName>Adaptr</FullName>**
**            </PartyName>**
**          </ExcludedDistributionChannel>*
           <PriceInformation>
             <PriceRangeType>Budget</PriceRangeType>
           </PriceInformation>
           <ValidityPeriod>
<StartDateTime>2022-12-01T02:35:00Z</StartDateTime>
           </ValidityPeriod>
         </DealTerms>

When I look at my output, I get this:

let $output :=
         <DealTerms>
           <TerritoryCode>AD</TerritoryCode>

           <PriceInformation>
             <PriceRangeType>Budget</PriceRangeType>
           </PriceInformation>
           <ValidityPeriod>
<StartDateTime>2022-12-01T02:35:00Z</StartDateTime>
           </ValidityPeriod>
         </DealTerms>

Is there anything I can do to remove the new line character from the 
output, which the typeswitch function seems to add?

I know that this white space is inconsequential to the processing of 
this document but if I could remove it, I would like to.

Nick

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

Re: [Exist-open] Creating Excel files in eXist-db?

[Kevin B. <kev...@xp...>]

Here is a screen shot from a presentation I did with the system a few years
back.






 

From: Kevin Brown <kev...@xp...> 
Sent: Monday, August 15, 2022 12:10 PM
To: 'Len Schultz' <le...@wi...>; 'exi...@li...'
<exi...@li...>
Subject: RE: [Exist-open] Creating Excel files in eXist-db?

 

For a customer, I created a highly specialized set of queries and XSLs.

They have their own XML structure.

They can create a document in their system which creates a very small
template document.

If they choose to, they can export that to a Word template.

We striped down a .docx, adjusted a few things and checked that into a
structure in eXist.
When you export, we copy that structure, take their XML and make the
document.xml file, inject it, zip it and send it back.

They can then edit in Word. The template Word document has some default
styles that are used to map into specific structures in their XML. Their
specialized XML also includes structures like:

<div type="if" test="state='UT'">blah blah</div> 

Which are also handles in style mapping and tags in Word. 

On check in, everything is reversed essentially uploading the .docx,
stripping out the document.xml, using XSL to make their XML and checking
that in.

The solution even grabs images in SVG and puts them into the Word document,
handles multiple user types by mapping certain areas as not editable, etc.

This whole scenario runs side-by-side with HTML-based editing of their XML
mapped into XHTML and fed to Summernote HTML editor, providing them an
ability to edit in Word or in a web browser (or both).

As it is custom to them, it is not easy to share things. 


A few gotchas - you cannot just use the template as is, you may need to hand
edit some namespaces to get in all right in the extracted .docx.

If you plan to go both ways, you have to control the authors or make sure at
the very least they are not doing dumb things (like instead of picking
"Heading Level 2" they just override font-size and style).
Some of the files in a .docx file must be uploaded as binary even though
they may not look like one. I believe this applies to .res files in the
.docx zip container.

Kevin Brown
Xportability

 

From: Len Schultz <le...@wi... <mailto:le...@wi...> > 
Sent: Wednesday, August 10, 2022 12:15 AM
To: Craig Berry via Exist-open <exi...@li...
<mailto:exi...@li...> >
Subject: [Exist-open] Creating Excel files in eXist-db?

 

Has anyone created XLSX files in eXist-db?  If so, please share some
pointers.

 

--len

 

Re: [Exist-open] Creating Excel files in eXist-db?

[Kevin B. <kev...@xp...>]

For a customer, I created a highly specialized set of queries and XSLs.

They have their own XML structure.

They can create a document in their system which creates a very small
template document.

If they choose to, they can export that to a Word template.

We striped down a .docx, adjusted a few things and checked that into a
structure in eXist.
When you export, we copy that structure, take their XML and make the
document.xml file, inject it, zip it and send it back.

They can then edit in Word. The template Word document has some default
styles that are used to map into specific structures in their XML. Their
specialized XML also includes structures like:

<div type="if" test="state='UT'">blah blah</div> 

Which are also handles in style mapping and tags in Word. 

On check in, everything is reversed essentially uploading the .docx,
stripping out the document.xml, using XSL to make their XML and checking
that in.

The solution even grabs images in SVG and puts them into the Word document,
handles multiple user types by mapping certain areas as not editable, etc.

This whole scenario runs side-by-side with HTML-based editing of their XML
mapped into XHTML and fed to Summernote HTML editor, providing them an
ability to edit in Word or in a web browser.

As it is custom to them, it is not easy to share things. 
A few gotchas - you cannot just use the template as is, you may need to hand
edit some namespaces to get in all right in the extracted .docx.

If you plan to go both ways, you have to control the authors or make sure at
the very least they are not doing dumb things (like instead of picking
"Heading Level 2" they just override font-size and style).
Some of the files in a .docx file must be uploaded as binary even though
they may not look like one. I believe this applies to .res files in the
.docx zip container.

Kevin Brown
Xportability

 

From: Len Schultz <le...@wi...> 
Sent: Wednesday, August 10, 2022 12:15 AM
To: Craig Berry via Exist-open <exi...@li...>
Subject: [Exist-open] Creating Excel files in eXist-db?

 

Has anyone created XLSX files in eXist-db?  If so, please share some
pointers.

 

--len

 

[Exist-open] Fw: Creating Excel files in eXist-db?

[Roy W. <gar...@ya...>]

 

   ----- Forwarded message ----- From: Roy Walter <gar...@ya...>To: Len Schultz <le...@wi...>Sent: Wednesday, 10 August 2022 at 15:06:31 BSTSubject: Re: [Exist-open] Creating Excel files in eXist-db?
  Yes and no.
Excel will open an html table as a sheet. You can give the output file a .xls extension [not xlsx]. Excel will throw a warning but will open the file.
The .xlsx (XML) format is well documented. It's more complicated but you can create those files directly as well.
There's also ODS/ODF, another XML format, e.g., How to Read and Write ODF/ODS Files (OpenDocument Spreadsheets)

| 
| 
| 
|  |  |

 |

 |
| 
|  | 
How to Read and Write ODF/ODS Files (OpenDocument Spreadsheets)

This article will explain the basics of ODF format, and specifically its implementation in spreadsheet applicati...
 |

 |

 |




-- Roy.

    On Wednesday, 10 August 2022 at 13:50:39 BST, Len Schultz <le...@wi...> wrote:  
 
  Has anyone created XLSX files in eXist-db?  If so, please share some pointers.
--len
_______________________________________________
Exist-open mailing list
Exi...@li...
https://lists.sourceforge.net/lists/listinfo/exist-open
    

Re: [Exist-open] Export collection

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

Florian,

That is exactly what I was looking for. Thank you!

Vincent

________________________________
From: Florian Schmitt <fsc...@bu...>
Sent: Wednesday, August 10, 2022 3:51 AM
To: Lizzi, Vincent <Vin...@ta...>; exi...@li... <exi...@li...>
Subject: AW: Export collection


Vincent,



You could use the Java Command Line Client for this task. It accepts an argument “-b” to specify the collection to export:



http://www.exist-db.org/exist/apps/doc/backup#command-line-utility<http://www.exist-db.org/exist/apps/doc/backup#command-line-utility>



For example, the following command will backup the /db/data/export1 collection, including its subcollections, to /tmp/backup (assuming that the eXist-db directory belongs to system user existdb):



sudo -u existdb /opt/eXist-db/bin/backup.sh -b '/db/data/export1' -d /tmp/backup/ -u <user> -p <pw>



Greetings,

Florian





Von: Lizzi, Vincent <Vin...@ta...>
Gesendet: Mittwoch, 10. August 2022 06:17
An: exi...@li...
Betreff: [Exist-open] Export collection



Hi all,



Is there a ready-made way to export a specific collection from eXist-db to disk? In this case, the collection contains several levels of nested collections, XQuery and XML documents. I looked through the documentation but could only find instructions about how to back up an entire database, not a specific collection. It should be easy enough to create an XQuery to export a collection to disk, but it seems worth asking first if such a thing already exists.



Thanks,

Vincent



 _____________________________________________

Vincent M. Lizzi

Head of Information Standards | Taylor & Francis Group

vin...@ta...<mailto:vin...@ta...>



"Everything should be made as simple as possible, but not simpler."





Information Classification: General


Information Classification: General

Re: [Exist-open] Creating Excel files in eXist-db?

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

Hi Len,

Pete Aven wrote a nice series of blog posts illustrating how to create MS
Office documents with XQuery. One covered Excel:


https://web.archive.org/web/20141111041736/http://developer.marklogic.com/blog/smallchanges/2007-12-04

I link to the series on my "Learn XQuery" list (PRs welcome):

  https://github.com/joewiz/learn-xquery

Joe

On Wed, Aug 10, 2022 at 8:50 AM Len Schultz <le...@wi...> wrote:

> Has anyone created XLSX files in eXist-db?  If so, please share some
> pointers.
>
> --len
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] Creating Excel files in eXist-db?

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

Has anyone created XLSX files in eXist-db?  If so, please share some pointers.

--len

Re: [Exist-open] Export collection

[Florian S. <fsc...@bu...>]

Vincent,

You could use the Java Command Line Client for this task. It accepts an argument “-b” to specify the collection to export:

http://www.exist-db.org/exist/apps/doc/backup#command-line-utility

For example, the following command will backup the /db/data/export1 collection, including its subcollections, to /tmp/backup (assuming that the eXist-db directory belongs to system user existdb):

sudo -u existdb /opt/eXist-db/bin/backup.sh -b '/db/data/export1' -d /tmp/backup/ -u <user> -p <pw>

Greetings,
Florian


Von: Lizzi, Vincent <Vin...@ta...>
Gesendet: Mittwoch, 10. August 2022 06:17
An: exi...@li...
Betreff: [Exist-open] Export collection

Hi all,

Is there a ready-made way to export a specific collection from eXist-db to disk? In this case, the collection contains several levels of nested collections, XQuery and XML documents. I looked through the documentation but could only find instructions about how to back up an entire database, not a specific collection. It should be easy enough to create an XQuery to export a collection to disk, but it seems worth asking first if such a thing already exists.

Thanks,
Vincent


 _____________________________________________

Vincent M. Lizzi

Head of Information Standards | Taylor & Francis Group

vin...@ta...<mailto:vin...@ta...>



"Everything should be made as simple as possible, but not simpler."



Information Classification: General

[Exist-open] Export collection

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

Hi all,

Is there a ready-made way to export a specific collection from eXist-db to disk? In this case, the collection contains several levels of nested collections, XQuery and XML documents. I looked through the documentation but could only find instructions about how to back up an entire database, not a specific collection. It should be easy enough to create an XQuery to export a collection to disk, but it seems worth asking first if such a thing already exists.

Thanks,
Vincent


 _____________________________________________

Vincent M. Lizzi

Head of Information Standards | Taylor & Francis Group

vin...@ta...<mailto:vin...@ta...>


"Everything should be made as simple as possible, but not simpler."



Information Classification: General

Re: [Exist-open] Deployment woes

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

Curiouser and curiouser
Still trying to navigate my way through logs/expath-repo.log to go back to
the installation date but in the meantime discovered that checking the
directory through linux shows the directory in question [1] but that the
exide "manage" interface (and the left-hand directory tree) does not [2].

[ec2-user@ip-172-31-10-199 WEB-INF]$ sudo ls -l
data/expathrepo/digitalmishnah-tei-0.1/
total 64
-rw-rw-rw-  1 root root  326 Jul 28 00:23 build.properties
-rw-rw-rw-  1 root root  519 Jul 28 00:23 build.xml
-rw-rw-rw-  1 root root  937 Jul 28 00:23 collection.xconf
drwxrwxrwx  2 root root 4096 Jul 28 00:23 doc_templates
-rw-rw-rw-  1 root root  234 Jul 28 00:23 expath-pkg.xml
-rw-rw-rw-  1 root root  364 Jul 28 00:23 local.build.properties
drwxrwxrwx  9 root root 4096 Jul 28 00:23 mishnah
drwxrwxrwx  2 root root 4096 Jul 28 00:23 ography
drwxrwxrwx 10 root root 4096 Jul 28 00:23 pagexml
-rw-rw-rw-  1 root root 1047 Jul 28 00:23 plain_text_out.txt
-rw-rw-rw-  1 root root 1213 Jul 28 00:23 README.MD
-rw-rw-rw-  1 root root  508 Jul 28 00:23 repo.xml
drwxrwxrwx  3 root root 4096 Jul 28 00:23 standoff
drwxrwxrwx  2 root root 4096 Jul 28 00:23 tei-facs
*drwxrwxrwx  4 root root 4096 Jul 28 00:23 tosefta*
drwxrwxrwx  2 root root 4096 Jul 28 00:23 txt

[2]
[image: image.png]

On Sun, Aug 7, 2022 at 2:20 PM Hayim Lapin <hl...@um...> wrote:

> Thank you, very helpful. I am definitely open to using a command line
> client. Will read over the github site and report back.
>
> On Fri, Aug 5, 2022 at 10:41 AM Juri Leino <jur...@ji...> wrote:
>
>> I assume you install the package using the dashboard.
>>
>> Would you be open to try a new command line client? It gives you
>> immediate feedback about the reason why the installation failed.
>>
>> If yes you could have a look at https://github.com/eXist-db/xst (not
>> officially released yet)
>>
>> Hayim Lapin wrote:
>>
>>
>> Hello list,
>> Resubmitting this question because I'm stumped. Tried switching
>> versions within exist 4 in case there was a bug that got fixed, but no go.
>> Any suggestions about debugging?
>>
>> On Tue, Aug 2, 2022 at 11:22 AM Hayim Lapin <hl...@um...
>> <mailto:hl...@um...>> wrote:
>>
>>     Dear list,
>>     This is for an application that used to work but I had to create a
>>     new instance to host it and redeploy. It is not yet compatible
>>     with new versions of exist, so I am still working in exist 4.7.1
>>     I build the xar from the desktop using ant, and can verify by
>>     unzipping that all the files are present. When I deploy using
>>     package manager only SOME of the directories are deployed.
>>     Any suggestions about what is happening and/or where the log file
>>     that might help me debug would be located?
>>     Many thanks
>>     HL
>>
>>
>>
>>
>>
>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>>

Re: [Exist-open] Deployment woes

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

Thank you, very helpful. I am definitely open to using a command line
client. Will read over the github site and report back.

On Fri, Aug 5, 2022 at 10:41 AM Juri Leino <jur...@ji...> wrote:

> I assume you install the package using the dashboard.
>
> Would you be open to try a new command line client? It gives you immediate
> feedback about the reason why the installation failed.
>
> If yes you could have a look at https://github.com/eXist-db/xst (not
> officially released yet)
>
> Hayim Lapin wrote:
>
>
> Hello list,
> Resubmitting this question because I'm stumped. Tried switching
> versions within exist 4 in case there was a bug that got fixed, but no go.
> Any suggestions about debugging?
>
> On Tue, Aug 2, 2022 at 11:22 AM Hayim Lapin <hl...@um...
> <mailto:hl...@um...>> wrote:
>
>     Dear list,
>     This is for an application that used to work but I had to create a
>     new instance to host it and redeploy. It is not yet compatible
>     with new versions of exist, so I am still working in exist 4.7.1
>     I build the xar from the desktop using ant, and can verify by
>     unzipping that all the files are present. When I deploy using
>     package manager only SOME of the directories are deployed.
>     Any suggestions about what is happening and/or where the log file
>     that might help me debug would be located?
>     Many thanks
>     HL
>
>
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>

Re: [Exist-open] Deployment woes

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

Hello list,
Resubmitting this question because I'm stumped. Tried switching versions
within exist 4 in case there was a bug that got fixed, but no go.
Any suggestions about debugging?

On Tue, Aug 2, 2022 at 11:22 AM Hayim Lapin <hl...@um...> wrote:

> Dear list,
> This is for an application that used to work but I had to create a new
> instance to host it and redeploy. It is not yet compatible with new
> versions of exist, so I am still working in exist 4.7.1
> I build the xar from the desktop using ant, and can verify by unzipping
> that all the files are present. When I deploy using package manager only
> SOME of the directories are deployed.
> Any suggestions about what is happening and/or where the log file that
> might help me debug would be located?
> Many thanks
> HL
>

[Exist-open] Deployment woes

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

Dear list,
This is for an application that used to work but I had to create a new
instance to host it and redeploy. It is not yet compatible with new
versions of exist, so I am still working in exist 4.7.1
I build the xar from the desktop using ant, and can verify by unzipping
that all the files are present. When I deploy using package manager only
SOME of the directories are deployed.
Any suggestions about what is happening and/or where the log file that
might help me debug would be located?
Many thanks
HL