exist-open — Open discussion

[Exist-open] Not able to remove a collection

[Sanil, S. <ss...@bl...>]

Hi,
When we try to remove a collection either through the UI or through calling the rest API we get this error. Is there any other way to remove the collection?

Please advise.
Thanks.

Re: [Exist-open] RESOURCE_ACCESS_FAILED during backup

[Alberto S. <has...@gm...>]

It seems the file was empty. Deleted it, a couple of restarts, and things
look like are running again.
Thanks

On Fri, May 16, 2025 at 2:13 PM Alberto Simões <has...@gm...> wrote:

> Hello
>
> Updated my exist image to 6.4.0
> Looked to the logs (not just export logs).
> I found the culprit:
>
> lexmart_exist.1.6071ajjw6txx@academia    | 16 May 2025 13:11:18,171
> [qtp1260390769-39] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT:
> Skipping damaged document tangentoide_1-76d57.xml
> lexmart_exist.1.6071ajjw6txx@academia    | 16 May 2025 13:11:39,790
> [qtp1260390769-39] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT:
> Found an orphaned document: tangentoide_1-76d57.xml
>
> Not sure what to do from here.
> Looking around while waiting for suggestions, in case I find anything.
>
> Thanks
>
> On Thu, May 15, 2025 at 3:11 PM Alberto Simões <has...@gm...>
> wrote:
>
>> Hello, Joe
>>
>> eXistDB 6.3.0, running on Docker. Dockerfile below.
>> Hope this helps.
>> Thanks
>>
>> FROM alpine:latest AS build
>> WORKDIR /autodeploy
>> RUN apk --no-cache add zip
>> COPY lexmart-restxq-api/ ./
>> RUN zip -r lexmart-restxq-api.xar *
>> FROM existdb/existdb:6.3.0 AS production
>> WORKDIR /exist
>> COPY docker/exist/conf.xml etc/conf.xml
>> COPY docker/exist/jetty/lib etc/webapp/WEB-INF/lib
>> COPY docker/exist/jetty/web.xml etc/webapp/WEB-INF/web.xml
>> COPY --from=build /autodeploy/*.xar autodeploy/
>> COPY docker/exist/autodeploy/*.xar autodeploy/
>> EXPOSE 8080
>>
>>
>>
>> On Thu, May 15, 2025 at 1:23 PM Joe Wicentowski <jo...@gm...> wrote:
>>
>>> Hi Alberto,
>>>
>>> For troubleshooting, which version of eXist, Java, OS, etc.?
>>>
>>> Joe
>>>
>>> Sent from my iPhone
>>>
>>>
>>> On Thu, May 15, 2025 at 6:28 AM Alberto Simões <has...@gm...>
>>> wrote:
>>>
>>>> Hello
>>>>
>>>> Triggering a full backup, I am getting this error:
>>>>
>>>> ...
>>>>   DOCUMENT: 108000 of 111595
>>>>   DOCUMENT: 109000 of 111595
>>>>   DOCUMENT: 110000 of 111595
>>>>   DOCUMENT: 111000 of 111595
>>>>   DOCUMENT: 111595 of 111595
>>>> ----------------------------------------------
>>>> RESOURCE_ACCESS_FAILED:
>>>> Failed to access document data
>>>> Document ID: 170957
>>>>
>>>> What can I do to:
>>>>  - understand what is the problematic document
>>>>  - try to understand if I had data lost
>>>>  - fix it :-)
>>>>
>>>> Thank you in advance.
>>>>
>>>> --
>>>> Alberto Simões
>>>> _______________________________________________
>>>> Exist-open mailing list
>>>> Exi...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>
>>>
>>
>> --
>> Alberto Simões
>>
>
>
> --
> Alberto Simões
>


-- 
Alberto Simões

Re: [Exist-open] RESOURCE_ACCESS_FAILED during backup

[Alberto S. <has...@gm...>]

Hello

Updated my exist image to 6.4.0
Looked to the logs (not just export logs).
I found the culprit:

lexmart_exist.1.6071ajjw6txx@academia    | 16 May 2025 13:11:18,171
[qtp1260390769-39] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT:
Skipping damaged document tangentoide_1-76d57.xml
lexmart_exist.1.6071ajjw6txx@academia    | 16 May 2025 13:11:39,790
[qtp1260390769-39] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT:
Found an orphaned document: tangentoide_1-76d57.xml

Not sure what to do from here.
Looking around while waiting for suggestions, in case I find anything.

Thanks

On Thu, May 15, 2025 at 3:11 PM Alberto Simões <has...@gm...> wrote:

> Hello, Joe
>
> eXistDB 6.3.0, running on Docker. Dockerfile below.
> Hope this helps.
> Thanks
>
> FROM alpine:latest AS build
> WORKDIR /autodeploy
> RUN apk --no-cache add zip
> COPY lexmart-restxq-api/ ./
> RUN zip -r lexmart-restxq-api.xar *
> FROM existdb/existdb:6.3.0 AS production
> WORKDIR /exist
> COPY docker/exist/conf.xml etc/conf.xml
> COPY docker/exist/jetty/lib etc/webapp/WEB-INF/lib
> COPY docker/exist/jetty/web.xml etc/webapp/WEB-INF/web.xml
> COPY --from=build /autodeploy/*.xar autodeploy/
> COPY docker/exist/autodeploy/*.xar autodeploy/
> EXPOSE 8080
>
>
>
> On Thu, May 15, 2025 at 1:23 PM Joe Wicentowski <jo...@gm...> wrote:
>
>> Hi Alberto,
>>
>> For troubleshooting, which version of eXist, Java, OS, etc.?
>>
>> Joe
>>
>> Sent from my iPhone
>>
>>
>> On Thu, May 15, 2025 at 6:28 AM Alberto Simões <has...@gm...>
>> wrote:
>>
>>> Hello
>>>
>>> Triggering a full backup, I am getting this error:
>>>
>>> ...
>>>   DOCUMENT: 108000 of 111595
>>>   DOCUMENT: 109000 of 111595
>>>   DOCUMENT: 110000 of 111595
>>>   DOCUMENT: 111000 of 111595
>>>   DOCUMENT: 111595 of 111595
>>> ----------------------------------------------
>>> RESOURCE_ACCESS_FAILED:
>>> Failed to access document data
>>> Document ID: 170957
>>>
>>> What can I do to:
>>>  - understand what is the problematic document
>>>  - try to understand if I had data lost
>>>  - fix it :-)
>>>
>>> Thank you in advance.
>>>
>>> --
>>> Alberto Simões
>>> _______________________________________________
>>> Exist-open mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>
>>
>
> --
> Alberto Simões
>


-- 
Alberto Simões

Re: [Exist-open] RESOURCE_ACCESS_FAILED during backup

[Alberto S. <has...@gm...>]

Hello, Joe

eXistDB 6.3.0, running on Docker. Dockerfile below.
Hope this helps.
Thanks

FROM alpine:latest AS build
WORKDIR /autodeploy
RUN apk --no-cache add zip
COPY lexmart-restxq-api/ ./
RUN zip -r lexmart-restxq-api.xar *
FROM existdb/existdb:6.3.0 AS production
WORKDIR /exist
COPY docker/exist/conf.xml etc/conf.xml
COPY docker/exist/jetty/lib etc/webapp/WEB-INF/lib
COPY docker/exist/jetty/web.xml etc/webapp/WEB-INF/web.xml
COPY --from=build /autodeploy/*.xar autodeploy/
COPY docker/exist/autodeploy/*.xar autodeploy/
EXPOSE 8080



On Thu, May 15, 2025 at 1:23 PM Joe Wicentowski <jo...@gm...> wrote:

> Hi Alberto,
>
> For troubleshooting, which version of eXist, Java, OS, etc.?
>
> Joe
>
> Sent from my iPhone
>
>
> On Thu, May 15, 2025 at 6:28 AM Alberto Simões <has...@gm...>
> wrote:
>
>> Hello
>>
>> Triggering a full backup, I am getting this error:
>>
>> ...
>>   DOCUMENT: 108000 of 111595
>>   DOCUMENT: 109000 of 111595
>>   DOCUMENT: 110000 of 111595
>>   DOCUMENT: 111000 of 111595
>>   DOCUMENT: 111595 of 111595
>> ----------------------------------------------
>> RESOURCE_ACCESS_FAILED:
>> Failed to access document data
>> Document ID: 170957
>>
>> What can I do to:
>>  - understand what is the problematic document
>>  - try to understand if I had data lost
>>  - fix it :-)
>>
>> Thank you in advance.
>>
>> --
>> Alberto Simões
>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>

-- 
Alberto Simões

Re: [Exist-open] RESOURCE_ACCESS_FAILED during backup

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

Hi Alberto,

For troubleshooting, which version of eXist, Java, OS, etc.?

Joe

Sent from my iPhone


On Thu, May 15, 2025 at 6:28 AM Alberto Simões <has...@gm...> wrote:

> Hello
>
> Triggering a full backup, I am getting this error:
>
> ...
>   DOCUMENT: 108000 of 111595
>   DOCUMENT: 109000 of 111595
>   DOCUMENT: 110000 of 111595
>   DOCUMENT: 111000 of 111595
>   DOCUMENT: 111595 of 111595
> ----------------------------------------------
> RESOURCE_ACCESS_FAILED:
> Failed to access document data
> Document ID: 170957
>
> What can I do to:
>  - understand what is the problematic document
>  - try to understand if I had data lost
>  - fix it :-)
>
> Thank you in advance.
>
> --
> Alberto Simões
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] Call for presentations Declarative Amsterdam 2025

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

Hi all,

Following the success of the past six editions, the seventh edition of Declarative Amsterdam will once again take place at the Science Park, Amsterdam, on Thursday/Friday 6/7 November 2025. As usual, it will be a hybrid conference with the opportunity to attend live or online, for both attendees and presenters.

Declarative techniques are a style of computing that expresses the purpose of computation without describing its control flow. It allows you to focus on the ‘what’, rather than the ‘how’.

Declarative Amsterdam will have presentations on past experiences, current trends and future perspectives in fields such as functional programming, declarative data modeling, databases, XML and related technologies, JSON, CSS, XForms, semantic web, data science, data visualization, grammars, parsing, and domain-specific languages.


Call for presentations


We invite practitioners, software architects and engineers, academic researchers and others to submit a proposal for a tutorial or a presentation.

Tutorials can be between 1 and 2.5 hours, and preferably include hands-on sessions for participants.

Presentations can be between 15 and 45 minutes. Speakers can present in person, or prepare a video, and be available online for the question and answer session afterwards.

A presentation can be about an established technology, a new idea, a product, or application, as long as it addresses the topic of the conference.

Proposals should include a title, duration and summary (90–200 words), and may also include a full paper. Presenters have the option of submitting a full paper or slides, to be published on the Declarative Amsterdam website.

All presentations are made available for the wider audience after the conference on our website and on  <https://www.youtube.com/@declarativeamsterdam> YouTube. For papers and topics from previous years, see the website:  <https://declarative.amsterdam> https://declarative.amsterdam

Please submit your proposals at  <https://declarative.amsterdam/cfp> https://declarative.amsterdam/cfp


Timeline


Submission deadline: 31 July
Acceptance: Beginning of September
Videos, tutorials, papers: Beginning of October
Conference: 7 and 8 November

All the best,
Declarative Amsterdam 2025 organizing committee

 

[Exist-open] RESOURCE_ACCESS_FAILED during backup

[Alberto S. <has...@gm...>]

Hello

Triggering a full backup, I am getting this error:

...
  DOCUMENT: 108000 of 111595
  DOCUMENT: 109000 of 111595
  DOCUMENT: 110000 of 111595
  DOCUMENT: 111000 of 111595
  DOCUMENT: 111595 of 111595
----------------------------------------------
RESOURCE_ACCESS_FAILED:
Failed to access document data
Document ID: 170957

What can I do to:
 - understand what is the problematic document
 - try to understand if I had data lost
 - fix it :-)

Thank you in advance.

-- 
Alberto Simões

Re: [Exist-open] Opening a file in eXide in a large folder

[Alberto S. <has...@gm...>]

Hello, All

It was a PEBKAC kind of problem.
Sorry for spamming the mailing list.

Thanks

On Wed, May 14, 2025 at 11:55 AM Alberto Simões <has...@gm...> wrote:

> Hello
>
> I have a folder with a lot of files (probably more than 100K).
> When I try to open a file, with open or manage files, in eXide, I can
> filter by some of the names, but not for recent files.
>
> Is there any limit that might be producing this?
> Is there a way to open a file if you know its full name, instead of using
> the browse mechanism?
>
> Thanks
>
> --
> Alberto Simões
>


-- 
Alberto Simões

[Exist-open] [ANN} Release of eXist-db 6.4.0

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

Dear eXist-db Community,

I'd like to share the announcement that Juri Leino posted earlier today on
Slack [1].

Best,
Joe

--

We are happy to announce that version 6.4.0 of eXist-db was released last
week [2]. It is a small feature release that addresses three breaking
regressions that were discovered in 6.3.0. We recommend that all users of
eXist-db 6.0.0-6.3.0 upgrade to version 6.4.0.

Important facts:

- DMG and installers are now signed by eXist Solutions GmbH and
- Docker images and the DMG run natively on arm Macs and x86 platforms

Thanks to all who helped get it out! These include Leif-Jöran Olsson,
Wolfgang Meier, Dannes Wessels, Duncan Paterson, Patrick Reinhart, Olaf
Schreck, and everyone else who contributed in any other way like posting
issues and testing. For more detailed information please have a look at the
release notes [2].

This marks the last planned update to eXist-db 6, and we will now shift
focus on version 7.


[1] https://exist-db.slack.com/archives/CG2MRUZ35/p1747212643173699. For
anyone who hasn't joined the Slack community, please consider joining.
Invite link:
https://join.slack.com/t/exist-db/shared_invite/enQtNjQ4MzUyNTE4MDY3LWNkYjZjMmZkNWQ5MDBjODQ3OTljNjMyODkwNmY1MzQwNjUwZjMzZTY1MGJkMjY5NDFhOWZjMDZiMDdhMzY4NGY
.

[2] https://exist-db.org/exist/apps/wiki/blogs/eXist/eXistdb640

[Exist-open] Opening a file in eXide in a large folder

[Alberto S. <has...@gm...>]

Hello

I have a folder with a lot of files (probably more than 100K).
When I try to open a file, with open or manage files, in eXide, I can
filter by some of the names, but not for recent files.

Is there any limit that might be producing this?
Is there a way to open a file if you know its full name, instead of using
the browse mechanism?

Thanks

-- 
Alberto Simões

Re: [Exist-open] Versioning lock errors in 5.x and 6.x

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

Hi Felix,

The versioning module does appear to have a number of known issues, listed
at https://github.com/eXist-db/xquery-versioning-module/issues, including
compatibility issues with eXist 5.2.0. I'd welcome you to review those and
see if they match your issue or if yours is new/different. If they match
yours, you could add a note listing your eXist version(s) as still
affected. If your issue is different, please create a new issue reporting
it. It would be great to restore compatibility with the current version of
eXist.

Joe

On Fri, May 9, 2025 at 12:18 PM felix jeneau <fel...@ho...>
wrote:

> I'm attempting to use the 'Versioning' package and am running into, what
> appears to be, locking issues.
>
> In eXide, the very first save of an XML doc errors out and shows this in a
> popup:
>
> 'void org.exist.dom.persistent.DocumentImpl.(org.exist.storage.BrokerPool,
> org.exist.collections.Collection, org.exist.xmldb.XmldbURI)'
>
>
>
> eXist then becomes unresponsive and requires a restart.  I can see in
> Monex, a bunch of 'waiting for' -> 'COLLECTION ( WRITE_LOCK )' under
> 'Waiting Threads.'
>
>
> Dunno if it's related, but under 'Active Threads,' I see a stacktrace:
>
> java.base@17.0.12/jdk.internal.misc.Unsafe.park(Native Method)
> java.base@17.0.12
> /java.util.concurrent.locks.LockSupport.park(LockSupport.java:211)
> java.base@17.0.12
> /java.util.concurrent.locks.AbstractQueuedLongSynchronizer.acquire(AbstractQueuedLongSynchronizer.java:348)
> java.base@17.0.12
> /java.util.concurrent.locks.AbstractQueuedLongSynchronizer.acquireShared(AbstractQueuedLongSynchronizer.java:659)
>
> uk.ac.ic.doc.slurp.multilock.MultiLock.intentionReadLock(MultiLock.java:501)
> org.exist.storage.lock.LockManager.lock(LockManager.java:293)
>
> org.exist.storage.lock.LockManager.acquirePathReadLock(LockManager.java:267)
>
> org.exist.storage.lock.LockManager.acquireCollectionReadLock(LockManager.java:219)
> org.exist.storage.NativeBroker.readLockCollection(NativeBroker.java:1837)
> org.exist.storage.NativeBroker.openCollection(NativeBroker.java:869)
> ...
>
>
> After killing the process and restarting, if I try to save a doc in eXide,
> the popup says:
>
> 'org.exist.storage.lock.Lock org.exist.collections.Collection.getLock()'
>
> and Monex shows all of the stuff mentioned above.
>
>
>
> exist.log, doesn't show any errors.  Just:
>
> DEBUG (TemporaryFileManager.java [returnTemporaryFile]:135) - Deleted
> temporary file:
> /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/exist-db-temp-file-manager-6286306081099162350/exist-db-temp-13573353218066578415.tmp
> DEBUG (Txn.java [close]:211) - Resetting transaction state for next use.
> DEBUG (MutableCollection.java [checkPermissionsForAddDocument]:1697) -
> Found old doc 3074
> DEBUG (Txn.java [close]:190) - Transaction was not committed or aborted,
> auto aborting!
> WARN  (TransactionManager.java [close]:421) - Transaction was not
> committed or aborted, auto aborting!
> DEBUG (TransactionManager.java [doAbortTransaction]:400) - Aborted
> transaction: 891
>
>
> Nothing in the two logs associated with locking.
>
>
> (I did modify log4j2.xml to also log for the versioning package, but
> didn't see anything of relevance)
>
>
>
> These are both new instances of eXist.  (5.5.1 and 6.4.0). The file is
> only opened in a single tab in eXide, so there shouldn't be an issue with
> multiple users accessing the same file.
>
>
>
> Any ideas?  Is this possibly a bug with the package?
>
>
>
> (side note, installing the versioning package directly doesn't seem to
> work properly.  After installing it, regardless of restart, I kept getting
> missing-class errors for VersioningModule and VersioningFilter.  I had to
> copy the jars over to the lib folder, update startup.xml to include the
> dependencies, and add the module to conf.xml)
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] Versioning lock errors in 5.x and 6.x

[felix j. <fel...@ho...>]

I'm attempting to use the 'Versioning' package and am running into, what appears to be, locking issues.

In eXide, the very first save of an XML doc errors out and shows this in a popup:

'void org.exist.dom.persistent.DocumentImpl.(org.exist.storage.BrokerPool, org.exist.collections.Collection, org.exist.xmldb.XmldbURI)'



eXist then becomes unresponsive and requires a restart.  I can see in Monex, a bunch of 'waiting for' -> 'COLLECTION ( WRITE_LOCK )' under 'Waiting Threads.'


Dunno if it's related, but under 'Active Threads,' I see a stacktrace:

java.base@17.0.12/jdk.internal.misc.Unsafe.park(Native Method)
java.base@17.0.12/java.util.concurrent.locks.LockSupport.park(LockSupport.java:211)
java.base@17.0.12/java.util.concurrent.locks.AbstractQueuedLongSynchronizer.acquire(AbstractQueuedLongSynchronizer.java:348)
java.base@17.0.12/java.util.concurrent.locks.AbstractQueuedLongSynchronizer.acquireShared(AbstractQueuedLongSynchronizer.java:659)
uk.ac.ic.doc.slurp.multilock.MultiLock.intentionReadLock(MultiLock.java:501)
org.exist.storage.lock.LockManager.lock(LockManager.java:293)
org.exist.storage.lock.LockManager.acquirePathReadLock(LockManager.java:267)
org.exist.storage.lock.LockManager.acquireCollectionReadLock(LockManager.java:219)
org.exist.storage.NativeBroker.readLockCollection(NativeBroker.java:1837)
org.exist.storage.NativeBroker.openCollection(NativeBroker.java:869)
...


After killing the process and restarting, if I try to save a doc in eXide, the popup says:

'org.exist.storage.lock.Lock org.exist.collections.Collection.getLock()'

and Monex shows all of the stuff mentioned above.



exist.log, doesn't show any errors.  Just:

DEBUG (TemporaryFileManager.java [returnTemporaryFile]:135) - Deleted temporary file: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/exist-db-temp-file-manager-6286306081099162350/exist-db-temp-13573353218066578415.tmp
DEBUG (Txn.java [close]:211) - Resetting transaction state for next use.
DEBUG (MutableCollection.java [checkPermissionsForAddDocument]:1697) - Found old doc 3074
DEBUG (Txn.java [close]:190) - Transaction was not committed or aborted, auto aborting!
WARN  (TransactionManager.java [close]:421) - Transaction was not committed or aborted, auto aborting!
DEBUG (TransactionManager.java [doAbortTransaction]:400) - Aborted transaction: 891


Nothing in the two logs associated with locking.


(I did modify log4j2.xml to also log for the versioning package, but didn't see anything of relevance)



These are both new instances of eXist.  (5.5.1 and 6.4.0). The file is only opened in a single tab in eXide, so there shouldn't be an issue with multiple users accessing the same file.



Any ideas?  Is this possibly a bug with the package?



(side note, installing the versioning package directly doesn't seem to work properly.  After installing it, regardless of restart, I kept getting missing-class errors for VersioningModule and VersioningFilter.  I had to copy the jars over to the lib folder, update startup.xml to include the dependencies, and add the module to conf.xml)

Re: [Exist-open] Multiple different serialization formats in a single xquery

[Sascha G. <gr...@bb...>]

Dear Pieter, dear Peter,

thanks a lot for your suggestions! I tried out Pieters 
util:declare-options() solution and it seems to work fine so far. For 
documentations sake, here is the updated/fixed version of my attempt:

xquery version "3.1";
let $p_format := request:get-parameter("format", ())

let $test :=
<html>
     <head>
         <title>Test Title</title>
     </head>
     <body>
         <h1>Hello, World!</h1>
     </body>
</html>

return
     if ($p_format = "tei-xml") then 
(util:declare-option("exist:serialize", "method=xml"), $test) else 
(util:declare-option("exist:serialize", "method=html5 
media-type=text/html"), $test)


Serialization, doctype and Content-Type header look good with this variant.

Thanks a lot!

Sascha

Am 17.04.2025 um 15:25 schrieb Sascha Grabsch via Exist-open:
> Dear list members,
> 
> I'm trying to output different formats (XML and HTML5) from a single 
> xquery script, but can't get it to work. Here is my test case:
> 
> xquery version "3.1";
> let $p_format := request:get-parameter("format", ())
> 
> let $test :=
> <html>
>      <head>
>          <title>Test Title</title>
>      </head>
>      <body>
>          <h1>Hello, World!</h1>
>      </body>
> </html>
> 
> return
>      if ($p_format = "tei-xml") then (serialize($test, map { "method": 
> "xml" })) else (serialize($test, map { "method": "html" }))
> 
> 
> However in both cases this does not work as expected:
> 
> method:xml - The serialization option method:xml does not return valid 
> XML, since the returned document is wrongly escaped 
> (&lt;html&gt;&lt;head&gt;&lt;title&gt;Test Title&lt;/title&gt;&lt;/ 
> head&gt;&lt;body&gt;&lt;h1&gt;Hello, World!&lt;/h1&gt;&lt;/body&gt;&lt;/ 
> html&gt;). The content-type in the response header however is correct 
> ("application/xml").
> 
> method:html - While the serialization option method:html correctly adds 
> a doctype for HTML5 (i. e. <!DOCTYPE html>), the actual response in a 
> browser is wrongly escaped (as in &lt;!DOCTYPE html&gt;
> &lt;html&gt;&lt;head&gt;&lt;title&gt;Test Title&lt;/title&gt;&lt;/ 
> head&gt;&lt;body&gt;&lt;h1&gt;Hello, World!&lt;/h1&gt;&lt;/body&gt;&lt;/ 
> html&gt;). Additionally the content-type in the response header is 
> "application/xml" instead of "text/html".
> 
> 
> According to <https://exist-db.org/exist/apps/doc/xquery.xml#fn- 
> serialize> I would have expected to be able to return different 
> serializations via fn:serialize, but it seems it is only possible to 
> have one serialization per XQuery script via "declare option 
> exist:serialize ..."?
> 
> I would be glad about any information or hints what I might be missing.
> 
> Thanks a lot!
> 
> Sascha

Re: [Exist-open] Multiple different serialization formats in a single xquery

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

Hi Sascha,

another way to dynamically set serialization options is via `response:stream($content as item()*, $serialization-options as xs:string) as empty-sequence()`. 
"It directly streams its input to the servlet's output stream. It should thus be the last statement in the XQuery.“ (XQuery Function Documentation)

Cheers
Peter


> Am 22.04.2025 um 07:15 schrieb Pieter Lamers <pie...@be...>:
> 
> Hi Sascha,
> 
> I think the problem is that you can serialize a snippet using fn:serialize but the whole response is serialized according to exist serialization settings. Apart from the declare options route in the prolog of your xquery, you can also set these inline via the following, e.g. util:declare-option("exist:serialize", "method=json")
> 
> I think this will get you going.
> 
> Best,
> Pieter
> 
> On 17/04/2025 15:25, Sascha Grabsch via Exist-open wrote:
>> Dear list members,
>> 
>> I'm trying to output different formats (XML and HTML5) from a single xquery script, but can't get it to work. Here is my test case:
>> 
>> xquery version "3.1";
>> let $p_format := request:get-parameter("format", ())
>> 
>> let $test :=
>> <html>
>>     <head>
>>         <title>Test Title</title>
>>     </head>
>>     <body>
>>         <h1>Hello, World!</h1>
>>     </body>
>> </html>
>> 
>> return
>>     if ($p_format = "tei-xml") then (serialize($test, map { "method": "xml" })) else (serialize($test, map { "method": "html" }))
>> 
>> 
>> However in both cases this does not work as expected:
>> 
>> method:xml - The serialization option method:xml does not return valid XML, since the returned document is wrongly escaped (&lt;html&gt;&lt;head&gt;&lt;title&gt;Test Title&lt;/title&gt;&lt;/head&gt;&lt;body&gt;&lt;h1&gt;Hello, World!&lt;/h1&gt;&lt;/body&gt;&lt;/html&gt;). The content-type in the response header however is correct ("application/xml").
>> 
>> method:html - While the serialization option method:html correctly adds a doctype for HTML5 (i. e. <!DOCTYPE html>), the actual response in a browser is wrongly escaped (as in &lt;!DOCTYPE html&gt;
>> &lt;html&gt;&lt;head&gt;&lt;title&gt;Test Title&lt;/title&gt;&lt;/head&gt;&lt;body&gt;&lt;h1&gt;Hello, World!&lt;/h1&gt;&lt;/body&gt;&lt;/html&gt;). Additionally the content-type in the response header is "application/xml" instead of "text/html".
>> 
>> 
>> According to <https://exist-db.org/exist/apps/doc/xquery.xml#fn-serialize> I would have expected to be able to return different serializations via fn:serialize, but it seems it is only possible to have one serialization per XQuery script via "declare option exist:serialize ..."?
>> 
>> I would be glad about any information or hints what I might be missing.
>> 
>> Thanks a lot!
>> 
>> Sascha
> 
> -- 
> Pieter Lamers
> John Benjamins Publishing Company
> Postal Address: P.O. Box 36224, 1020 ME AMSTERDAM, The Netherlands
> Visiting Address: Klaprozenweg 75D, 1033 NN AMSTERDAM, The Netherlands
> Warehouse: Kelvinstraat 11-13, 1446 TK PURMEREND, The Netherlands
> tel: +31 20 630 4747
> web: www.benjamins.com <http://www.benjamins.com/>
> 
> 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li... <mailto:Exi...@li...>
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] Multiple different serialization formats in a single xquery

[Pieter L. <pie...@be...>]

Hi Sascha,

I think the problem is that you can serialize a snippet using 
fn:serialize but the whole response is serialized according to exist 
serialization settings. Apart from the declare options route in the 
prolog of your xquery, you can also set these inline via the following, 
e.g. util:declare-option("exist:serialize", "method=json")

I think this will get you going.

Best,
Pieter

On 17/04/2025 15:25, Sascha Grabsch via Exist-open wrote:
> Dear list members,
>
> I'm trying to output different formats (XML and HTML5) from a single 
> xquery script, but can't get it to work. Here is my test case:
>
> xquery version "3.1";
> let $p_format := request:get-parameter("format", ())
>
> let $test :=
> <html>
>     <head>
>         <title>Test Title</title>
>     </head>
>     <body>
>         <h1>Hello, World!</h1>
>     </body>
> </html>
>
> return
>     if ($p_format = "tei-xml") then (serialize($test, map { "method": 
> "xml" })) else (serialize($test, map { "method": "html" }))
>
>
> However in both cases this does not work as expected:
>
> method:xml - The serialization option method:xml does not return valid 
> XML, since the returned document is wrongly escaped 
> (&lt;html&gt;&lt;head&gt;&lt;title&gt;Test 
> Title&lt;/title&gt;&lt;/head&gt;&lt;body&gt;&lt;h1&gt;Hello, 
> World!&lt;/h1&gt;&lt;/body&gt;&lt;/html&gt;). The content-type in the 
> response header however is correct ("application/xml").
>
> method:html - While the serialization option method:html correctly 
> adds a doctype for HTML5 (i. e. <!DOCTYPE html>), the actual response 
> in a browser is wrongly escaped (as in &lt;!DOCTYPE html&gt;
> &lt;html&gt;&lt;head&gt;&lt;title&gt;Test 
> Title&lt;/title&gt;&lt;/head&gt;&lt;body&gt;&lt;h1&gt;Hello, 
> World!&lt;/h1&gt;&lt;/body&gt;&lt;/html&gt;). Additionally the 
> content-type in the response header is "application/xml" instead of 
> "text/html".
>
>
> According to 
> <https://exist-db.org/exist/apps/doc/xquery.xml#fn-serialize> I would 
> have expected to be able to return different serializations via 
> fn:serialize, but it seems it is only possible to have one 
> serialization per XQuery script via "declare option exist:serialize ..."?
>
> I would be glad about any information or hints what I might be missing.
>
> Thanks a lot!
>
> Sascha

-- 
Pieter Lamers
John Benjamins Publishing Company
Postal Address: P.O. Box 36224, 1020 ME AMSTERDAM, The Netherlands
Visiting Address: Klaprozenweg 75D, 1033 NN AMSTERDAM, The Netherlands
Warehouse: Kelvinstraat 11-13, 1446 TK PURMEREND, The Netherlands
tel: +31 20 630 4747
web: www.benjamins.com

[Exist-open] Multiple different serialization formats in a single xquery

[Sascha G. <gr...@bb...>]

Dear list members,

I'm trying to output different formats (XML and HTML5) from a single 
xquery script, but can't get it to work. Here is my test case:

xquery version "3.1";
let $p_format := request:get-parameter("format", ())

let $test :=
<html>
     <head>
         <title>Test Title</title>
     </head>
     <body>
         <h1>Hello, World!</h1>
     </body>
</html>

return
     if ($p_format = "tei-xml") then (serialize($test, map { "method": 
"xml" })) else (serialize($test, map { "method": "html" }))


However in both cases this does not work as expected:

method:xml - The serialization option method:xml does not return valid 
XML, since the returned document is wrongly escaped 
(&lt;html&gt;&lt;head&gt;&lt;title&gt;Test 
Title&lt;/title&gt;&lt;/head&gt;&lt;body&gt;&lt;h1&gt;Hello, 
World!&lt;/h1&gt;&lt;/body&gt;&lt;/html&gt;). The content-type in the 
response header however is correct ("application/xml").

method:html - While the serialization option method:html correctly adds 
a doctype for HTML5 (i. e. <!DOCTYPE html>), the actual response in a 
browser is wrongly escaped (as in &lt;!DOCTYPE html&gt;
&lt;html&gt;&lt;head&gt;&lt;title&gt;Test 
Title&lt;/title&gt;&lt;/head&gt;&lt;body&gt;&lt;h1&gt;Hello, 
World!&lt;/h1&gt;&lt;/body&gt;&lt;/html&gt;). Additionally the 
content-type in the response header is "application/xml" instead of 
"text/html".


According to 
<https://exist-db.org/exist/apps/doc/xquery.xml#fn-serialize> I would 
have expected to be able to return different serializations via 
fn:serialize, but it seems it is only possible to have one serialization 
per XQuery script via "declare option exist:serialize ..."?

I would be glad about any information or hints what I might be missing.

Thanks a lot!

Sascha
-- 
Berlin-Brandenburgische Akademie der Wissenschaften
TELOTA ⁠(The Electronic Life Of The Academy)
Jägerstr. 22/23 | 10117 Berlin
gr...@bb... | +49 30 20370 536

Re: [Exist-open] backup fails

[Eduard D. <ed...@fr...>]

Solved this by using BackupSystemTask for just one collection, needed to dive into the code to find out the correct parameters.




Eduard Drenth, Software Architekt


ed...@fr...


Doelestrjitte 8

8911 DX  Ljouwert

(058) 213 14 14

+31 62 094 34 28

https://www.fryske-akademy.nl/
https://frysker.nl/
https://frisian.eu/
[cid:b8fb4d34-8acc-44b1-afa4-85f1d4419a8e]

gpg: https://keyserver.ubuntu.com/pks/lookup?search=eduard+drenth&fingerprint=on&op=index

________________________________
From: Eduard Drenth <ed...@fr...>
Sent: Friday, April 4, 2025 10:58 AM
To: Exist-open <Exi...@li...>
Subject: [Exist-open] backup fails

Dear all,

The full backups of exist-db (6.2) fail since ± a week. Looks like I can still download the data and I have a week old backup. Don't fully trust the backup though because the backup file is accompanied with a report (see below) that shows an error.

exist logging shows:

 31 Mar 2025 20:00:00,037 [db.exist.scheduler.quartz-worker-2] INFO  (ConsistencyCheckTask.java [execute]:152) - Starting consistency check...
 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [execute]:165) - Errors found: 1
 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [execute]:170) - Fatal errors were found: pausing the consistency check task.
 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] INFO  (ConsistencyCheckTask.java [execute]:175) - Finished consistency check
 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] INFO  (ConsistencyCheckTask.java [execute]:179) - Starting backup...
 31 Mar 2025 20:00:10,305 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT: Skipping damaged document collection.xconf
 31 Mar 2025 20:00:30,270 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT: Found an orphaned document: collection.xconf

Backup logging shows:

  DOCUMENT: 70237 of 70237
----------------------------------------------
RESOURCE_ACCESS_FAILED:
Failed to access document data
Document ID: 2075

Regards,
Eduard



Eduard Drenth, Software Architekt


ed...@fr...


Doelestrjitte 8

8911 DX  Ljouwert

(058) 213 14 14

+31 62 094 34 28

https://www.fryske-akademy.nl/
https://frysker.nl/
https://frisian.eu/
[cid:a4941762-f448-4133-a3bf-ef679ade1fa0]

gpg: https://keyserver.ubuntu.com/pks/lookup?search=eduard+drenth&fingerprint=on&op=index

[Exist-open] backup fails

[Eduard D. <ed...@fr...>]

Dear all,

The full backups of exist-db (6.2) fail since ± a week. Looks like I can still download the data and I have a week old backup. Don't fully trust the backup though because the backup file is accompanied with a report (see below) that shows an error.

exist logging shows:

 31 Mar 2025 20:00:00,037 [db.exist.scheduler.quartz-worker-2] INFO  (ConsistencyCheckTask.java [execute]:152) - Starting consistency check...
 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [execute]:165) - Errors found: 1
 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [execute]:170) - Fatal errors were found: pausing the consistency check task.
 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] INFO  (ConsistencyCheckTask.java [execute]:175) - Finished consistency check
 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] INFO  (ConsistencyCheckTask.java [execute]:179) - Starting backup...
 31 Mar 2025 20:00:10,305 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT: Skipping damaged document collection.xconf
 31 Mar 2025 20:00:30,270 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT: Found an orphaned document: collection.xconf

Backup logging shows:

  DOCUMENT: 70237 of 70237
----------------------------------------------
RESOURCE_ACCESS_FAILED:
Failed to access document data
Document ID: 2075

Regards,
Eduard



Eduard Drenth, Software Architekt


ed...@fr...


Doelestrjitte 8

8911 DX  Ljouwert

(058) 213 14 14

+31 62 094 34 28

https://www.fryske-akademy.nl/
https://frysker.nl/
https://frisian.eu/
[cid:a4941762-f448-4133-a3bf-ef679ade1fa0]

gpg: https://keyserver.ubuntu.com/pks/lookup?search=eduard+drenth&fingerprint=on&op=index

Re: [Exist-open] Query exceeded predefined output-size-limit (1, 000, 000) for document fragments

[Alberto S. <am...@zb...>]

Hello

Thank you all.
I have a collection with a large number of files that might be causing these shortages.
Bumped the output size limit. Let's see how it handles it.

Thanks

Alberto Simões

On Thursday, March 20th, 2025 at 08:55, Guillaume Mella <gui...@un...> wrote:

> Hello,
>
> Le 19/03/2025 à 16:21, Alberto Simões a écrit :
>
>> Hello
>>
>> I am getting this message: Query exceeded predefined output-size-limit (1,000,000) for document fragments (see below complete log for error).
>>
>> What is the cause, and how can I fix it?
>> Thanks
>
> You are reaching the limit defined in the self documented existdb/etc/conf.xml
>
> <!--
>
> This is the global configuration for the query watchdog. The
>
> watchdog monitors all query processes, and can terminate any
>
> long-running queries if they exceed one of the predefined limits.
>
> These limits are as follows:
>
> - output-size-limit:
>
> this attribute limits the size of XML fragments constructed
>
> using XQuery, and thus sets the maximum amount of main memory a
>
> query is allowed to use. This limit is expressed as the maximum
>
> number of nodes allowed for an in-memory DOM tree. The purpose
>
> of this option is to avoid memory shortages on the server in
>
> cases where users are allowed to run queries that produce very
>
> large output fragments.
>
> - query-timeout:
>
> this attribute sets the maximum amount of time (expressed in
>
> milliseconds) that the query can take before it is killed..
>
> -->
>
> <watchdog
>
> output-size-limit
>
> =
>
> "1000000"
>
> query-timeout
>
> =
>
> "-1"
>
> />
>
> I often increase this value to one order of magnitude. even in the docker instances...
>
> Cheers,
> --
> Guillaume

Re: [Exist-open] Query exceeded predefined output-size-limit (1, 000, 000) for document fragments

[Guillaume M. <gui...@un...>]

Hello,

Le 19/03/2025 à 16:21, Alberto Simões a écrit :
> Hello
>
> I am getting this message: Query exceeded predefined output-size-limit 
> (1,000,000) for document fragments  (see below complete log for error).
>
> What is the cause, and how can I fix it?
> Thanks

You are reaching the limit defined in the self documented 
existdb/etc/conf.xml

   <!--
This is the global configuration for the query watchdog. The
watchdog monitors all query processes, and can terminate any
long-running queries if they exceed one of the predefined limits.
These limits are as follows:

- output-size-limit:
this attribute limits the size of XML fragments constructed
using XQuery, and thus sets the maximum amount of main memory a
query is allowed to use. This limit is expressed as the maximum
number of nodes allowed for an in-memory DOM tree. The purpose
of this option is to avoid memory shortages on the server in
cases where users are allowed to run queries that produce very
large output fragments.

- query-timeout:
this attribute sets the maximum amount of time (expressed in
milliseconds) that the query can take before it is killed..

-->
       <watchdog output-size-limit="1000000"query-timeout="-1"/>

I often increase this value to one order of magnitude. even in the 
docker instances...

Cheers,
--
Guillaume

Re: [Exist-open] Query exceeded predefined output-size-limit (1, 000, 000) for document fragments

[Pieter L. <pie...@be...>]

Hi Alberto,

on a main module you can set a different size limit. It is reached when 
your output has too many nodes.
to get a max of 10M nodes use the following:

declare option exist:output-size-limit "10000000";

when I need to set a large output-size-limit in a function I use the 
following function (which could be simplified):

declare function my:set-output-size-limit( $new-limit as xs:integer ) as 
empty-sequence()
{
   let $output-size-limit-option as xs:string := 'exist:output-size-limit'
   let $set-output-size-limit := 
util:declare-option($output-size-limit-option, $new-limit cast as xs:string)
   return ()
};

Best,
Pieter


On 19/03/2025 16:21, Alberto Simões wrote:
> Hello
>
> I am getting this message: Query exceeded predefined output-size-limit 
> (1,000,000) for document fragments  (see below complete log for error).
>
> What is the cause, and how can I fix it?
> Thanks
>
> lexmart_exist.1.vi427hqb2os7@academia    | 19 Mar 2025 15:12:32,497 
> [qtp478864778-47] WARN  (XQueryWatchDog.java [proceed]:174) - Query 
> exceeded predefined output-size-limit (1,000,000) for document 
> fragments: {
> lexmart_exist.1.vi427hqb2os7@academia    |     for  <130>
> lexmart_exist.1.vi427hqb2os7@academia    |         $resource in $subset
> lexmart_exist.1.vi427hqb2os7@academia    |       <131>
> lexmart_exist.1.vi427hqb2os7@academia    |         let  <131>
> lexmart_exist.1.vi427hqb2os7@academia    | $isCollection := $resource 
> = "/",
> lexmart_exist.1.vi427hqb2os7@academia    |             let  <132>
> lexmart_exist.1.vi427hqb2os7@academia    | $path := if (
> lexmart_exist.1.vi427hqb2os7@academia    | $isCollection
> lexmart_exist.1.vi427hqb2os7@academia    |                 ) then
> lexmart_exist.1.vi427hqb2os7@academia    | 
> {http://www.w3.org/2005/xpath-functions}concat($collection 
> <http://www.w3.org/2005/xpath-functions}concat($collection>, $resource)
> lexmart_exist.1.vi427hqb2os7@academia    | else
> lexmart_exist.1.vi427hqb2os7@academia    | 
> {http://www.w3.org/2005/xpath-functions}concat($collection 
> <http://www.w3.org/2005/xpath-functions}concat($collection>, "/", 
> $resource)
> lexmart_exist.1.vi427hqb2os7@academia    |             return
> lexmart_exist.1.vi427hqb2os7@academia    | where <137>
> lexmart_exist.1.vi427hqb2os7@academia    | 
> sm:has-access(untyped-value-check[xs:anyURI, $path cast as xs:anyURI], 
> "r")
> lexmart_exist.1.vi427hqb2os7@academia    |
> lexmart_exist.1.vi427hqb2os7@academia    |
> lexmart_exist.1.vi427hqb2os7@academia    | }
>
> -- 
> Alberto Simões
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

-- 
Pieter Lamers
John Benjamins Publishing Company
Postal Address: P.O. Box 36224, 1020 ME AMSTERDAM, The Netherlands
Visiting Address: Klaprozenweg 75D, 1033 NN AMSTERDAM, The Netherlands
Warehouse: Kelvinstraat 11-13, 1446 TK PURMEREND, The Netherlands
tel: +31 20 630 4747
web:www.benjamins.com

Re: [Exist-open] Query exceeded predefined output-size-limit (1, 000, 000) for document fragments

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

Take a look in conf.xml, you can increase the limit in there

On Wed, 19 Mar 2025, 19:07 Alberto Simões, <has...@gm...> wrote:

> Hello
>
> I am getting this message: Query exceeded predefined output-size-limit
> (1,000,000) for document fragments  (see below complete log for error).
>
> What is the cause, and how can I fix it?
> Thanks
>
> lexmart_exist.1.vi427hqb2os7@academia    | 19 Mar 2025 15:12:32,497
> [qtp478864778-47] WARN  (XQueryWatchDog.java [proceed]:174) - Query
> exceeded predefined output-size-limit (1,000,000) for document fragments: {
> lexmart_exist.1.vi427hqb2os7@academia    |     for  <130>
> lexmart_exist.1.vi427hqb2os7@academia    |         $resource in $subset
> lexmart_exist.1.vi427hqb2os7@academia    |       <131>
> lexmart_exist.1.vi427hqb2os7@academia    |         let  <131>
> lexmart_exist.1.vi427hqb2os7@academia    |             $isCollection :=
> $resource = "/",
> lexmart_exist.1.vi427hqb2os7@academia    |             let  <132>
> lexmart_exist.1.vi427hqb2os7@academia    |                 $path := if (
> lexmart_exist.1.vi427hqb2os7@academia    |
> $isCollection
> lexmart_exist.1.vi427hqb2os7@academia    |                 ) then
> lexmart_exist.1.vi427hqb2os7@academia    |                     {
> http://www.w3.org/2005/xpath-functions}concat($collection, $resource)
> lexmart_exist.1.vi427hqb2os7@academia    |                 else
> lexmart_exist.1.vi427hqb2os7@academia    |                     {
> http://www.w3.org/2005/xpath-functions}concat($collection, "/", $resource)
> lexmart_exist.1.vi427hqb2os7@academia    |             return
> lexmart_exist.1.vi427hqb2os7@academia    |                 where <137>
> lexmart_exist.1.vi427hqb2os7@academia    |
> sm:has-access(untyped-value-check[xs:anyURI, $path cast as xs:anyURI], "r")
> lexmart_exist.1.vi427hqb2os7@academia    |
> lexmart_exist.1.vi427hqb2os7@academia    |
> lexmart_exist.1.vi427hqb2os7@academia    | }
>
> --
> Alberto Simões
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] Query exceeded predefined output-size-limit (1, 000, 000) for document fragments

[Alberto S. <has...@gm...>]

Hello

I am getting this message: Query exceeded predefined output-size-limit
(1,000,000) for document fragments  (see below complete log for error).

What is the cause, and how can I fix it?
Thanks

lexmart_exist.1.vi427hqb2os7@academia    | 19 Mar 2025 15:12:32,497
[qtp478864778-47] WARN  (XQueryWatchDog.java [proceed]:174) - Query
exceeded predefined output-size-limit (1,000,000) for document fragments: {
lexmart_exist.1.vi427hqb2os7@academia    |     for  <130>
lexmart_exist.1.vi427hqb2os7@academia    |         $resource in $subset
lexmart_exist.1.vi427hqb2os7@academia    |       <131>
lexmart_exist.1.vi427hqb2os7@academia    |         let  <131>
lexmart_exist.1.vi427hqb2os7@academia    |             $isCollection :=
$resource = "/",
lexmart_exist.1.vi427hqb2os7@academia    |             let  <132>
lexmart_exist.1.vi427hqb2os7@academia    |                 $path := if (
lexmart_exist.1.vi427hqb2os7@academia    |                     $isCollection
lexmart_exist.1.vi427hqb2os7@academia    |                 ) then
lexmart_exist.1.vi427hqb2os7@academia    |                     {
http://www.w3.org/2005/xpath-functions}concat($collection, $resource)
lexmart_exist.1.vi427hqb2os7@academia    |                 else
lexmart_exist.1.vi427hqb2os7@academia    |                     {
http://www.w3.org/2005/xpath-functions}concat($collection, "/", $resource)
lexmart_exist.1.vi427hqb2os7@academia    |             return
lexmart_exist.1.vi427hqb2os7@academia    |                 where <137>
lexmart_exist.1.vi427hqb2os7@academia    |
sm:has-access(untyped-value-check[xs:anyURI, $path cast as xs:anyURI], "r")
lexmart_exist.1.vi427hqb2os7@academia    |
lexmart_exist.1.vi427hqb2os7@academia    |
lexmart_exist.1.vi427hqb2os7@academia    | }

-- 
Alberto Simões

[Exist-open] A git module for eXist?

[Roth, M. <mat...@ya...>]

Hi List,

I am in the process of updating an exist-3.x instance to an exist-6.x instance. We would like to be able to directly clone, branch, and commit to a locally hosted git repository. In our eXist-3.x instance we do most of this via subversion and the old SVN module. But in the last decade we have migrated a lot of our local repositories to git and think this would be a good time to migrate away from this old dependency.

The problem I am running into is I don't see any modules that currently replicate the same features of the old SVN module in git. I see two abandoned projects.


  1.
 eXgit [0<https://github.com/shabanovd/eXgit/>] - This seemed to have the most community support
  2.
 eXgit [1<https://github.com/dariok/eXgit/tree/master>] - Yeah, same name, different project. The xar would not work in 6.2.0, and the instructions for using the jar also seemed to not function, nor generate any log messages [2<https://github.com/eXist-db/documentation/issues/385>].


And two xquery modules that are designed to work with github.


  1.
Github-xq [3<https://github.com/eXist-db/github-xq>]- Winona's excellent module, but due to restrictions on our data github is not an option
  2.
Tuttle [4<https://github.com/eeditiones/tuttle>] - I suppose I could self-host gitlab, but not sure excited about a nodejs dep.


So now I am left with a few questions


  1.
Is there a module for working with git I cannot locate?

  2.
If not, Why is there no longer a well maintained module for working with git or svn in eXist.
     *
Is there no community desire for this?
     *
 Is this an anti-pattern, or might there be a more preferred way to handle this?

  3.
If I were to try to do something myself, I would want to create an EXPath Package or would I be wanting to create an extension such the Example in extensions/modules/example [5<https://github.com/eXist-db/exist/tree/develop/extensions/modules/example>]?
     *
Or am I misunderstanding and these are similar? From my understanding the latter requires it being built and bundled with exist.

Best,
Matt



[0] https://github.com/shabanovd/eXgit/
[1] https://github.com/dariok/eXgit/tree/master
[2] https://github.com/eXist-db/documentation/issues/385
[3] https://github.com/eXist-db/github-xq
[4] https://github.com/eeditiones/tuttle
[5] https://github.com/eXist-db/exist/tree/develop/extensions/modules/example

Re: [Exist-open] apps from launcher not working on new install

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

Once again, thank you for this suggestion! Just to close this circle,
unfortunately, editing the conf.xml file did not solve the problem.

On Sun, Feb 16, 2025 at 4:14 AM Florian Schmitt <
ml-...@fl...> wrote:

> Hayim,
>
> it seems that in certain cases, the default apps aren't deployed
> correctly. If I remember correctly, I ran into a similar issue with a
> headless setup.
>
> Please try the following (assuming eXist is installed in /opt/existdb -
> adapt the paths according to your setup):
>
> First, check if there's a directory /opt/existdb/autodeploy containing the
> .xar files for eXide and so on.
>
> If the autodeploy directory seems fine, stop exist-db, and open
> /opt/existdb/etc/conf.xml in a text editor.
>
> Search for the following lines:
>
> <trigger class="org.exist.repo.AutoDeploymentTrigger">
>     <!-- parameter name="ignore-autodeploy-system-property" value="true"/ -->
>     <!-- parameter name="dir" value="${project.build.outputDirectory}/autodeploy"/ -->
> </trigger>
>
> Uncomment the second "parameter" element, and change the "value"
> attribute, setting the full path to the autodeploy directory. With exist
> installed in /opt/existdb, the third line should now be
>
> <parameter name="dir" value="/opt/existdb/autodeploy" />
>
> Now, restart exist-db and check the logs for messages regarding
> autodeployment. If the AutoDeploymentTrigger doesn't fire, you may have to
> uncomment the first parameter element, too.
>
> HTH
> Florian
>
> Am 14.02.25 um 16:42 schrieb Hayim Lapin:
>
> Hello,
> I just installed eXist 6.3 on an aws linux machine running on port *8081*.
> The database loads and I can log in as admin.
> All the default apps that appear on the launcher yield errors like:
> HTTP ERROR 404 Document /db/apps/eXide not found
>
> I have been able to use the package manager to load and run an app
> (TEI-Publisher), but other apps created by me and working in a docker
> instance generate the following again caused by being unable to access /db:
>
>> err:XPST0017 error found while loading .... for module:
>> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line
>> 84, column 13]
>
>
> There is another version of exist (4.7.1) running on port *8080*. Could
> this be the cause of the problem?
>
> Any suggestions about how to fix this?
> Best, HL
>
>
> _______________________________________________
> Exist-open mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>