exist-open — Open discussion

Re: [Exist-open] HTTP Header Vary: User-Agent

[Olaf S. <ol...@ex...>]

Matthias,

> since i recently worked towards a cache in front of existdb, i wonder why
> there is the value "User-Agent" added to a Vary header i cannot control from
> Xquery.

Been there, seen that.  We saw the same issue with a caching proxy in front
of eXist-db, resulting in multiple cached copies of the same resource because
of Vary: user-agent.

I think this was solved by editing $EXIST_HOME/etc/jetty/jetty-gzip.xml and
removing or commenting out the section "<Set name=excludedAgentPatterns>..."

The only reason for having this in the Jetty config is to support MSIE 6,
which could not handle gzip compression.  Given that MSIE 6 is >20 years old,
I don't see a real need to support it.

And the benefit is: "Vary: user-agent" gone.

Disclaimer: If memory serves correctly.

Olaf

[Exist-open] HTTP Header Vary: User-Agent

[Mathias G. <go...@su...>]

Hi existdb community,

since i recently worked towards a cache in front of existdb, i wonder 
why there is the value "User-Agent" added to a Vary header i cannot 
control from Xquery. Using the response module to insert a Vary header 
(my hope was, i can just override with), gives me a duplicate header 
what is worse, because it might confuses clients. I investigated on the 
issue and identified the gzip compression lib added to the jetty config. 
And that is confusing me, because i dont see any relation by the gzip 
compression to a User-Agent Vary…

Maybe i am on a good track and we can agree on a change here? One could 
also argue, that XQuery-MVC-users should be able to control the final 
response. For the REST- and RESTXQ-Interface, i also dont see any reason…

Also i noticed that you configured existdb.org different, so the header 
is not present. There are some ways fixing this issue, so let us discuss 
about the default setting.

best,
Mathias


setup:

    *docker run -p 8080:8080 existdb/existdb:6.4.1*

    *curl localhost:8080/exist/rest/db -l -v -o /dev/null*
    * Host localhost:8080 was resolved.
    * IPv6: ::1
    * IPv4: 127.0.0.1
       % Total    % Received % Xferd  Average Speed   Time    Time  
      Time  Current
                                      Dload  Upload   Total  Spent   
    Left  Speed
       0     0    0     0    0     0      0      0 --:--:-- --:--:--
    --:--:--     0*   Trying [::1]:8080...
    * Connected to localhost (::1) port 8080
    * using HTTP/1.x
     > GET /exist/rest/db HTTP/1.1
     > Host: localhost:8080
     > User-Agent: curl/8.15.0
     > Accept: */*
     >
    * Request completely sent off
    < HTTP/1.1 200 OK
    < Date: Mon, 30 Mar 2026 07:29:02 GMT
    < Content-Type: application/xml; charset=UTF-8
    < Last-Modified: Mon, 30 Mar 2026 07:28:04 GMT
    < Created: Mon, 30 Mar 2026 07:28:04 GMT
    *< Vary: Accept-Encoding, User-Agent*
    < Transfer-Encoding: chunked
    < Server: Jetty(9.4.58.v20250814)
    <
    { [485 bytes data]
    100   480    0   480    0     0   102k      0 --:--:-- --:--:--
    --:--:--  117k
    * Connection #0 to host localhost left intact

    *curl localhost:8080/exist/apps/fundocs/ -l -v -o /dev/null*
    * Host localhost:8080 was resolved.
    * IPv6: ::1
    * IPv4: 127.0.0.1
       % Total    % Received % Xferd  Average Speed   Time    Time  
      Time  Current
                                      Dload  Upload   Total  Spent   
    Left  Speed
       0     0    0     0    0     0      0      0 --:--:-- --:--:--
    --:--:--     0*   Trying [::1]:8080...
    * Connected to localhost (::1) port 8080
    * using HTTP/1.x
     > GET /exist/apps/fundocs/ HTTP/1.1
     > Host: localhost:8080
     > User-Agent: curl/8.15.0
     > Accept: */*
     >
    * Request completely sent off
    < HTTP/1.1 200 OK
    < Date: Mon, 30 Mar 2026 07:28:23 GMT
    < Last-Modified: Mon, 30 Mar 2026 07:28:11 GMT
    < Created: Mon, 30 Mar 2026 07:28:11 GMT
    < X-XQuery-Cached: false
    < Content-Type: text/html;charset=utf-8
    *< Vary: Accept-Encoding, User-Agent*
    < Transfer-Encoding: chunked
    < Server: Jetty(9.4.58.v20250814)
    <
    { [11443 bytes data]
    100 11437    0 11437    0     0  33554      0 --:--:-- --:--:--
    --:--:-- 33638
    * Connection #0 to host localhost left intact

Re: [Exist-open] sql: java.sql.sqlexception: unsupported feature: getmetadata java for oracle ojdbc8

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

Hi,

> On 16 Mar 2026, at 14:37, Willem van der Westhuizen <wi...@kw...> wrote:
> 
> 2. Previously we used a stored procedure that we called, but that is now failing. We noted that there is an exist/oracle module which is disabled by default. But uncommenting this did not work. It will be very useful to get that active if possible. We are happy to contribute to someone updating it.

I also saw that the module was disabled by default, due to some legal issues for older versions of the jar file. I did re-enabled it.

In the 6.x.x branch I made a fix, I saw that the code was depending on an older exist  version (v5). I made the module compile but there is no way for me to test.

regards

Dannes

Re: [Exist-open] eXist-db version 6.4.1 was released

[Craig B. <cra...@ma...>]

> On Mar 11, 2026, at 6:24 AM, Juri Leino <ju...@ex...> wrote:
> 
> We are glad to announce that exist-db version 6.4.1 is now released and available o
> 

Thanks to all who worked to make this happen.  

I do have one nit to pick.  On macOS the situation is the same as in previous releases in that the app is not notarized so it is difficult to open the first time, and each release of macOS makes that more difficult.  The app does appear to be signed with an Apple Developer ID:

% codesign -dv --verbose /Volumes/eXist-db/eXist-db.app
Executable=/Volumes/eXist-db/eXist-db.app/Contents/MacOS/eXist-JavaAppLauncher
Identifier=org.exist.start.Main
Format=app bundle with Mach-O universal (x86_64 arm64)
CodeDirectory v=20500 size=704 flags=0x10000(runtime) hashes=11+7 location=embedded
Signature size=9070
Authority=Developer ID Application: eXist Solutions GmbH (TK5UZLQZR2)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=Mar 5, 2026 at 4:16:44 PM
Info.plist entries=25
TeamIdentifier=TK5UZLQZR2
Runtime Version=14.4.0
Sealed Resources version=2 rules=13 files=468
Internal requirements count=1 size=180

but it is either not notarized or the notarization ticket is not stapled to the package:

% stapler validate /Volumes/eXist-db/eXist-db.app
Processing: /Volumes/eXist-db/eXist-db.app
eXist-db.app does not have a ticket stapled to it.

I know I'm asking developers to jump through more hoops, but that seems to me preferable to asking users to ignore scary security warnings.

 

________________________________________
Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Re: [Exist-open] sql: java.sql.sqlexception: unsupported feature: getmetadata java for oracle ojdbc8

[Willem v. d. W. <wi...@kw...>]

Hi Dannes,

Thank you for responding. We upgraded from 3.3.3 to 6.2, and that is 
when the oracle connections gave us problems. We cannot seem to get the 
connection pool working, and we get the error in two cases:

1. When we do any statement other than select, it returns the error. We 
created a workaround, which traps the error when its not a select query, 
but the logs are cluttered with the error.

2026-03-16 15:31:33,156 [qtp942804532-2925] WARN (LogFunction.java 
[writeLog]:202) - (Line: 54 
/db/kwantu-resource/modules/notificationModule.xqm) $url 
"https://epwprs.dpw.gov.za/"
2026-03-16 15:31:33,252 [qtp942804532-2848] ERROR (ExecuteFunction.java 
[eval]:192) - sql:execute() Caught SQLException "Unsupported feature: 
getMetaData" for SQL: "UPDATE COL_XMLSOURCE SET UPDATEDDATETIME = 
TO_DATE(SYSDATE, 'yyyy/mm/dd'), MIGRATEDFLAG='Pending', PROCESSUUID = 
'3ef916eb-3114-4ffe-89c2-fb37fa5cb012', XML_FILENAME = 
'867b79cd-9b4b-4458-bb79-cd9b4b74587e.xml' WHERE COMPANYID='3' AND 
PROFILEID='152864' AND APPLICATIONID='EPWPRS' AND COMPONENTID=17 AND 
SEQ= 5.643704E6"
java.sql.SQLException: Unsupported feature: getMetaData
         at 
oracle.jdbc.driver.ArrayDataResultSet.getMetaData(ArrayDataResultSet.java:1080) 
~[ojdbc8.jar:19.24.0.0.0]
         at 
org.exist.xquery.modules.sql.ExecuteFunction.resultAsElement(ExecuteFunction.java:300) 
~[exist-sql-6.2.0.jar:6.2.0]
         at 
org.exist.xquery.modules.sql.ExecuteFunction.eval(ExecuteFunction.java:189) 
~[exist-sql-6.2.0.jar:6.2.0]
         at org.exist.xquery.BasicFunction.eval(BasicFunction.java:73) 
~[exist-core-6.2.0.jar:6.2.0]
         at 
org.exist.xquery.InternalFunctionCall.eval(InternalFunctionCall.java:62) 
~[exist-core-6.2.0.jar:6.2.0]
         at org.exist.xquery.LetExpr.eval(LetExpr.java:98) 
~[exist-core-6.2.0.jar:6.2.0]
         at 
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:98) 
~[exist-core-6.2.0.jar:6.2.0]
         at 
org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:71) 
~[exist-core-6.2.0.jar:6.2.0]
         at org.exist.xquery.PathExpr.eval(PathExpr.java:280) 
~[exist-core-6.2.0.jar:6.2.0]

2. Previously we used a stored procedure that we called, but that is now 
failing. We noted that there is an exist/oracle module which is disabled 
by default. But uncommenting this did not work. It will be very useful 
to get that active if possible. We are happy to contribute to someone 
updating it.

Regards

Willem

On 2026/03/13 21:58, Dannes Wessels wrote:
> Hi Willem,
>
>
>> Is there somewhere that we can find a way to resolve this problem 
>> with exist 6.
>>
>> existdb oracle sqlexception "unsupported feature: getmetadata" for 
>> sql: java.sql.sqlexception: unsupported feature: getmetadata java
>
>
> There are a few questions….
>
>   * Is there a stack trace in the log file?
>   * Can you share a part of the relevant query?
>   * Which SQL database are you using? Oracle… which version?
>
>
> regards
>
> Dannes
>
>

Re: [Exist-open] sql: java.sql.sqlexception: unsupported feature: getmetadata java for oracle ojdbc8

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

Hi Willem,


> Is there somewhere that we can find a way to resolve this problem with exist 6.
> 
> existdb oracle sqlexception "unsupported feature: getmetadata" for sql: java.sql.sqlexception: unsupported feature: getmetadata java


There are a few questions….

Is there a stack trace in the log file?
Can you share a part of the relevant query?
Which SQL database are you using? Oracle… which version?

regards

Dannes

[Exist-open] eXist-db version 6.4.1 was released

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

We are glad to announce that exist-db version *6.4.1* is now released 
and available on docker 
<https://hub.docker.com/layers/existdb/existdb/6.4.1/images/sha256-f82f792af432edbd0ab240c6b3d9bf84fae00eb5fa9eb718411c3c0f81492e66>, 
brew <https://formulae.brew.sh/cask/exist-db>, GitHub 
<https://github.com/eXist-db/exist/releases/tag/eXist-6.4.1> and Maven 
Central <https://central.sonatype.com/artifact/org.exist-db/exist>
It fixes a couple of small issues and updates key dependencies to their 
latest compatible versions.
For details you can have a look at the release notes on exist-db.org 
<https://exist-db.org/exist/apps/wiki/blogs/eXist/eXistdb641>

Special thanks to Nico Verwer for his contributions

We plan the next release to start with a :seven:

--

Juri Leino,
Release Technician

[Exist-open] sql: java.sql.sqlexception: unsupported feature: getmetadata java for oracle ojdbc8

[Willem v. d. W. <wi...@kw...>]

Hi,

Is there somewhere that we can find a way to resolve this problem with 
exist 6.

existdb oracle sqlexception "unsupported feature: getmetadata" for sql: 
java.sql.sqlexception: unsupported feature: getmetadata java

-- 
Willem van der Westhuizen
+27 82 9200718

Re: [Exist-open] 400% CPU, no running threads/queries

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

Hi, Michael
Thanks for your answer.
The problem of high cpu is after the reindex. I can see that on the logs.
Probably there is some more verbose log level that can help me. Need to find it.

Thanks you

Alberto Simões

Sent from [Proton Mail](https://proton.me/mail/home) for Android.

-------- Original Message --------
On Friday, 12/12/25 at 23:51 Michael Westbay <wes...@ja...> wrote:

> Hi Alberto,
>
> It sounds like it may be reindexing. If you abruptly stopped the container without everything shutting down gracefully, reindexing everything will automatically start when you bring it back up.
>
> Do you have multiple GB of XML documents and many indexes? If so, reindexing could take quite a while.
>
> To gracefully stop eXist, log into the container's shell and run the bin/shutdown.sh script before shutting down the container. I don't use containers, but it seems to me that there is shut down script that can trigger that in Docker's setting file.
>
> Hope this helps.
>
> Take care.
>
> 2025年12月13日(土) 6:00 Alberto Simões <am...@zb...>:
>
>> On Friday, December 12th, 2025 at 10:22, Alberto Simões <am...@zb...> wrote:
>>
>>> On Friday, December 12th, 2025 at 09:55, Juri Leino ju...@ex... wrote:
>>>
>>> > That sounds alarming. Especially, when monex does not show any activity.
>>> > I have seen instances running on all available CPU cores with a lot of
>>> > active brokers.
>>> >
>>> > What you should see, however, is monex reporting the same CPU usage.
>>> > Is that the case?
>>> >
>>> > Under "System Information"
>>> >
>>> > -> System CPU Load:
>>> >
>>> > -> Process CPU Load:
>>>
>>>
>>> From monex, everything looks calm.
>>> System CPU Load: 0.646755
>>> Process CPU Load: 0.575614
>>>
>>> Only at the top I have the " Running Queries 1 " but nothing more shows.
>>>
>>> As a sidenote, I am running inside a docker image, in case that helps debugging.
>>
>> If I stop the container and restart, load looks normal for a little time... and gets up again...
>>
>> Btw, is there a way to gracelly stop jetty when running inside docker?
>>
>> Thanks
>>
>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>
> --
>
> Michael Westbay
> Writer/System Administrator
> http://www.japanesebaseball.com/

Re: [Exist-open] 400% CPU, no running threads/queries

[Michael W. <wes...@ja...>]

Hi Alberto,

It sounds like it may be reindexing. If you abruptly stopped the container
without everything shutting down gracefully, reindexing everything will
automatically start when you bring it back up.

Do you have multiple GB of XML documents and many indexes? If so,
reindexing could take quite a while.

To gracefully stop eXist, log into the container's shell and run the
bin/shutdown.sh script before shutting down the container. I don't use
containers, but it seems to me that there is shut down script that can
trigger that in Docker's setting file.

 Hope this helps.

Take care.

2025年12月13日(土) 6:00 Alberto Simões <am...@zb...>:

> On Friday, December 12th, 2025 at 10:22, Alberto Simões <am...@zb...>
> wrote:
>
> > On Friday, December 12th, 2025 at 09:55, Juri Leino
> ju...@ex... wrote:
> >
> > > That sounds alarming. Especially, when monex does not show any
> activity.
> > > I have seen instances running on all available CPU cores with a lot of
> > > active brokers.
> > >
> > > What you should see, however, is monex reporting the same CPU usage.
> > > Is that the case?
> > >
> > > Under "System Information"
> > >
> > > -> System CPU Load:
> > >
> > > -> Process CPU Load:
> >
> >
> > From monex, everything looks calm.
> > System CPU Load: 0.646755
> > Process CPU Load: 0.575614
> >
> > Only at the top I have the " Running Queries 1 " but nothing more shows.
> >
> > As a sidenote, I am running inside a docker image, in case that helps
> debugging.
>
> If I stop the container and restart, load looks normal for a little
> time... and gets up again...
>
> Btw, is there a way to gracelly stop jetty when running inside docker?
>
> Thanks
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>


-- 
Michael Westbay
Writer/System Administrator
http://www.japanesebaseball.com/

Re: [Exist-open] 400% CPU, no running threads/queries

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

On Friday, December 12th, 2025 at 10:22, Alberto Simões <am...@zb...> wrote:

> On Friday, December 12th, 2025 at 09:55, Juri Leino ju...@ex... wrote:
> 
> > That sounds alarming. Especially, when monex does not show any activity.
> > I have seen instances running on all available CPU cores with a lot of
> > active brokers.
> > 
> > What you should see, however, is monex reporting the same CPU usage.
> > Is that the case?
> > 
> > Under "System Information"
> > 
> > -> System CPU Load:
> > 
> > -> Process CPU Load:
> 
> 
> From monex, everything looks calm.
> System CPU Load: 0.646755
> Process CPU Load: 0.575614
> 
> Only at the top I have the " Running Queries 1 " but nothing more shows.
> 
> As a sidenote, I am running inside a docker image, in case that helps debugging.

If I stop the container and restart, load looks normal for a little time... and gets up again...

Btw, is there a way to gracelly stop jetty when running inside docker?

Thanks

Re: [Exist-open] Opening a file in eXide without browsing

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

> Looking to the readme, it is exactly the tool I was planning to implement, so I will try to use it.
>
> My only complain is nodejs... it takes so damn space :-)
I would say that 149 kB unpacked size is OK.
The repo + dependencies is much more in development, but that does not 
count.
> Thank you for your work and share.
<3

Don't forget to like and subscribe :)

Re: [Exist-open] Opening a file in eXide without browsing

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

On Friday, December 12th, 2025 at 10:20, Juri Leino <ju...@ex...> wrote:

> On 12.12.25 11:07,
>
> Alberto Simões
>
> wrote:
>
> > xst looks like exactly what I am trying to implement in python to help my tasks. What is it exactly? Any link?
>
> Here are two links :)
>
> on npm: https://www.npmjs.com/package/@existdb/xst
>
> on github: https://github.com/eXist-db/xst
>
> If you have questions regarding xst I am happy to help. Even if you
> decide not to use it I woudl like to learn why :)

Looking to the readme, it is exactly the tool I was planning to implement, so I will try to use it.

My only complain is nodejs... it takes so damn space :-)

Thank you for your work and share.

Re: [Exist-open] Opening a file in eXide without browsing

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

On 12.12.25 11:07, Alberto Simões wrote:

> xst looks like exactly what I am trying to implement in python to help my tasks. What is it exactly? Any link?
Here are two links :)

on npm: https://www.npmjs.com/package/@existdb/xst

on github: https://github.com/eXist-db/xst

I am developing it, so I am certainly biased. Also, at the moment you 
need to have NodeJS v20+ installed in order to run it.

For me it is the go to tool for administering eXist-db instances in 
various versions and different platforms.
It is also used in production setups to automate package installation / 
updates.

I run it locally to communicate with a Zoo of servers (locally, over 
VPN- or SSH-tunnels). Connections are managed either by .env files or 
configuration files.

If you have questions regarding xst I am happy to help. Even if you 
decide not to use it I woudl like to learn why :)

Bye,

Juri

Re: [Exist-open] Opening a file in eXide without browsing

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

Hi, Juri

xst looks like exactly what I am trying to implement in python to help my tasks. What is it exactly? Any link?

Thank you



Alberto Simões


On Friday, December 12th, 2025 at 09:43, Juri Leino <ju...@ex...> wrote:

> Hi Alberto!
> 
> On 09.12.25 22:11,
> 
> Alberto Simões
> 
> wrote:
> 
> > On Tuesday, December 9th, 2025 at 20:37, Alberto Simões am...@zb... wrote:
> > 
> > > Probably this is something available in a later exist version (if that is the case, just let me know). But, is there a way to open a file in eXide without browsing the collection?
> 
> Yes, eXide accepts a search parameter "open"
> Example:
> http://localhost:8888/exist/apps/eXide/index.html?open=/db/apps/dashboard/repo.xml
> 
> > > It happens that I have more than 120K files in a folder, and even filtering, crashes eXide completely :-(
> 
> 
> The File>Manage dialog is be able to handle collections with that many
> 
> child resources at least in recent versions of eXide (latest is 3.5.4).
> 
> > nded up writing a small python3 script to edit the file, as it seems the index was broken because of an invalid document ID. Nevertheless, having a direct way to open a file when you know the name would be great :-)
> 
> Have you considered to use xst's edit command for that?
> 
> xst edit /db/apps/dashboard/repo.xml --editor vim
> 
> 
> Cheers,
> 
> Juri
> 
> 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] 400% CPU, no running threads/queries

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

On Friday, December 12th, 2025 at 09:55, Juri Leino <ju...@ex...> wrote:
> That sounds alarming. Especially, when monex does not show any activity.
> I have seen instances running on all available CPU cores with a lot of
> active brokers.
> 
> What you should see, however, is monex reporting the same CPU usage.
> Is that the case?
> 
> Under "System Information"
> 
> -> System CPU Load:
> 
> -> Process CPU Load:

>From monex, everything looks calm.
System CPU Load: 	0.646755
Process CPU Load: 	0.575614

Only at the top I have the " Running Queries 1 " but nothing more shows.

As a sidenote, I am running inside a docker image, in case that helps debugging.

Thank you in advance. I have my collaborators complaining :-(
Alberto

Re: [Exist-open] 400% CPU, no running threads/queries

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

Hi

On 11.12.25 12:24, Alberto Simões wrote:
> Since recently my exist-db instance is always with CPU usage above 200%, getting easily to 400% or 600%.
>
> 2788459 root      20   0   10,6g   6,6g   3180 S 405,3  28,3     50,22 java
>
> Looking to MONEX there is no activity...
>
> How can I debug this issue?
> I am running 6.4.0

That sounds alarming. Especially, when monex does not show any activity.
I have seen instances running on all available CPU cores with a lot of 
active brokers.

What you _should_ see, however, is monex reporting the same CPU usage. 
Is that the case?

Under "System Information"

-> System CPU Load:
-> Process CPU Load:

  Cheers,

Juri

Re: [Exist-open] Opening a file in eXide without browsing

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

Hi Alberto!

On 09.12.25 22:11, Alberto Simões wrote:
> On Tuesday, December 9th, 2025 at 20:37, Alberto Simões <am...@zb...> wrote:
>
>> Probably this is something available in a later exist version (if that is the case, just let me know). But, is there a way to open a file in eXide without browsing the collection?
Yes, eXide accepts a search parameter "open"
Example:
http://localhost:8888/exist/apps/eXide/index.html?open=/db/apps/dashboard/repo.xml 

>> It happens that I have more than 120K files in a folder, and even filtering, crashes eXide completely :-(

The File>Manage dialog is be able to handle collections with that many 
child resources at least in recent versions of eXide (latest is 3.5.4).

> nded up writing a small python3 script to edit the file, as it seems the index was broken because of an invalid document ID. Nevertheless, having a direct way to open a file when you know the name would be great :-)
Have you considered to use xst's edit command for that?

xst edit /db/apps/dashboard/repo.xml --editor vim


Cheers,

Juri

Re: [Exist-open] Opening a file in eXide without browsing

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

Hi Alberto,

You can directly open a file in eXide using this URL pattern:


https://exist-db.org/exist/apps/eXide/index.html?open=/db/apps/demo/index.html

... as seen on https://exist-db.org/exist/apps/demo/index.html.

If you're thinking of a command within the eXide GUI to paste a resource's
path to open it in an editor, that doesn't yet exist, but I agree it would
be a nice feature!

Joe

On Thu, Dec 11, 2025 at 3:57 AM Alberto Simões <am...@zb...> wrote:

>
> On Tuesday, December 9th, 2025 at 20:37, Alberto Simões <am...@zb...>
> wrote:
>
> > Hi
> >
> > Probably this is something available in a later exist version (if that
> is the case, just let me know). But, is there a way to open a file in eXide
> without browsing the collection?
> >
> > It happens that I have more than 120K files in a folder, and even
> filtering, crashes eXide completely :-(
>
> Ended up writing a small python3 script to edit the file, as it seems the
> index was broken because of an invalid document ID. Nevertheless, having a
> direct way to open a file when you know the name would be great :-)
>
> THanks
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] Opening a file in eXide without browsing

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

Hi!

I discovered this nice feature using previous versions of eXide some 
years ago. Not sure if the parameters of urls related to you eXide 
instance have changed, but you can search 'source code' in the following 
demo page:

https://www.exist-db.org/exist/apps/demo/examples/templating/templates.html

Cheers,

--

Guillaume

[Exist-open] 400% CPU, no running threads/queries

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

Hi

Since recently my exist-db instance is always with CPU usage above 200%, getting easily to 400% or 600%.

2788459 root      20   0   10,6g   6,6g   3180 S 405,3  28,3     50,22 java

Looking to MONEX there is no activity...

How can I debug this issue?
I am running 6.4.0

Thanks



Alberto Simões

Re: [Exist-open] Opening a file in eXide without browsing

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

Hi Alberto,

there's already a direct way to open a file in eXide when path and resource name are known: Take the base URL of eXide (e.g. "https://exist-db.org/exist/apps/eXide/index.html" and append "?open=/db/path/to/your/resource.xml". Example:

http://www.exist-db.org/exist/apps/eXide/index.html?open=/db/apps/demo/examples/urlrewriting/index.html 

I'm not sure if there's a documentation for those URL parameters anywhere (I didn't find one). It seems that eXide accepts two URL parameters: open and snip, see https://github.com/eXist-db/eXide/blob/4fd7caf4c99e2a44120092323e44b0637adaaf5b/src/eXide.js#L40 - open will try to open the requested resources, while snip will show the snippet as new document.

Cheers,
Florian




> -----Ursprüngliche Nachricht-----
> Von: Alberto Simões <am...@zb...>
> Gesendet: Dienstag, 9. Dezember 2025 22:12
> An: exi...@li...
> Betreff: Re: [Exist-open] Opening a file in eXide without browsing
> 
> 
> On Tuesday, December 9th, 2025 at 20:37, Alberto Simões <am...@zb...>
> wrote:
> 
> > Hi
> >
> > Probably this is something available in a later exist version (if that is the case,
> just let me know). But, is there a way to open a file in eXide without browsing the
> collection?
> >
> > It happens that I have more than 120K files in a folder, and even filtering,
> crashes eXide completely :-(
> 
> Ended up writing a small python3 script to edit the file, as it seems the index was
> broken because of an invalid document ID. Nevertheless, having a direct way to
> open a file when you know the name would be great :-)
> 
> THanks
> 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] Opening a file in eXide without browsing

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

On Tuesday, December 9th, 2025 at 20:37, Alberto Simões <am...@zb...> wrote:

> Hi
> 
> Probably this is something available in a later exist version (if that is the case, just let me know). But, is there a way to open a file in eXide without browsing the collection?
> 
> It happens that I have more than 120K files in a folder, and even filtering, crashes eXide completely :-(

Ended up writing a small python3 script to edit the file, as it seems the index was broken because of an invalid document ID. Nevertheless, having a direct way to open a file when you know the name would be great :-)

THanks

[Exist-open] Opening a file in eXide without browsing

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

Hi

Probably this is something available in a later exist version (if that is the case, just let me know). But, is there a way to open a file in eXide without browsing the collection?

It happens that I have more than 120K files in a folder, and even filtering, crashes eXide completely :-(

Thank you


Alberto Simões

Re: [Exist-open] xmldb:collection-available not reporting existence of collection named "Å"

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

hi,

Just to be sure, what eXist version are you using?

Cheers

Dannes

> On 5 Nov 2025, at 09:34, Henrik Nielsen <hen...@gm...> wrote:
> 
> Any help would be much appreciated,