exist-open — Open discussion

Re: [Exist-open] Help with a new installation

[<ml-...@fl...>]

Hayim,

just some general ideas - which system user is running the installation 
process? Has that user write permissions for the data folder? Can you 
rule out disk space issues?

Sadly, i don't have specific experience with AWS instances...

HTH
Florian


Am 15.07.2022 um 20:05 schrieb Hayim Lapin:
> Dear all,
> I wonder if members of the list could help with installation problems. I 
> am installing the exist to an aws instance running redhat (why? I don't 
> actually know)
> When I run the set up jar the process runs through installation and then 
> at startup gives the error report below.
> Any suggestions as to what I am doing wrong?
> 
> Many thanks
> HL
> 
> [ Starting processing ]
> Starting process Setting data dir... (1/2)
> Starting process Setting admin password... (2/2)
> eXist version 6.0.1 (51506fc97a9e5bb55fdea71fc76def2c9d402886), 
> Copyright (C) 2001-2022 The eXist-db Project
> eXist-db comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; for details read the license file.
> 
> Connecting to database...
> java.io.IOException: Database is read-only
...

> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

[Exist-open] Help with a new installation

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

Dear all,
I wonder if members of the list could help with installation problems. I am
installing the exist to an aws instance running redhat (why? I don't
actually know)
When I run the set up jar the process runs through installation and then at
startup gives the error report below.
Any suggestions as to what I am doing wrong?

Many thanks
HL

[ Starting processing ]
Starting process Setting data dir... (1/2)
Starting process Setting admin password... (2/2)
eXist version 6.0.1 (51506fc97a9e5bb55fdea71fc76def2c9d402886), Copyright
(C) 2001-2022 The eXist-db Project
eXist-db comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; for details read the license file.

Connecting to database...
java.io.IOException: Database is read-only
        at
org.exist.storage.NativeBroker.saveCollection(NativeBroker.java:1837)
        at
org.exist.storage.NativeBroker.createCollection(NativeBroker.java:782)
        at
org.exist.storage.NativeBroker.getOrCreateCollectionExplicit_rootCollection(NativeBroker.java:731)
        at
org.exist.storage.NativeBroker.getOrCreateCollectionExplicit(NativeBroker.java:675)
        at
org.exist.storage.NativeBroker.getOrCreateCollectionExplicit(NativeBroker.java:708)
        at
org.exist.storage.NativeBroker.getOrCreateCollection(NativeBroker.java:618)
        at
org.exist.storage.BrokerPool.initialiseSystemCollection(BrokerPool.java:744)
        at
org.exist.storage.BrokerPool.initialiseSystemCollections(BrokerPool.java:769)
        at org.exist.storage.BrokerPool._initialize(BrokerPool.java:616)
        at org.exist.storage.BrokerPool.initialize(BrokerPool.java:451)
        at org.exist.storage.BrokerPools.configure(BrokerPools.java:177)
        at org.exist.storage.BrokerPools.configure(BrokerPools.java:131)
        at org.exist.xmldb.DatabaseImpl.configure(DatabaseImpl.java:125)
        at
org.exist.xmldb.DatabaseImpl.getLocalCollection(DatabaseImpl.java:194)
        at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:180)
        at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:171)
        at
org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:235)
        at
org.exist.client.InteractiveClient.connect(InteractiveClient.java:314)
        at
org.exist.client.InteractiveClient.connectToDatabase(InteractiveClient.java:2151)
        at
org.exist.client.InteractiveClient.run(InteractiveClient.java:2253)
        at
org.exist.client.InteractiveClient.main(InteractiveClient.java:251)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.exist.start.Main.invokeMain(Main.java:153)
        at org.exist.start.Main.runEx(Main.java:292)
        at org.exist.start.Main.run(Main.java:158)
        at org.exist.start.Main.main(Main.java:95)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.codehaus.mojo.appassembler.booter.AppassemblerBooter.executeMain(AppassemblerBooter.java:257)
        at
org.codehaus.mojo.appassembler.booter.AppassemblerBooter.main(AppassemblerBooter.java:77)
Connection to database failed; message: configuration error: Initialisation
of system collections failed: Database is read-only
org.xmldb.api.base.XMLDBException: configuration error: Initialisation of
system collections failed: Database is read-only
        at org.exist.xmldb.DatabaseImpl.configure(DatabaseImpl.java:131)
        at
org.exist.xmldb.DatabaseImpl.getLocalCollection(DatabaseImpl.java:194)
        at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:180)
        at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:171)
        at
org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:235)
        at
org.exist.client.InteractiveClient.connect(InteractiveClient.java:314)
        at
org.exist.client.InteractiveClient.connectToDatabase(InteractiveClient.java:2151)
        at
org.exist.client.InteractiveClient.run(InteractiveClient.java:2253)
        at
org.exist.client.InteractiveClient.main(InteractiveClient.java:251)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.exist.start.Main.invokeMain(Main.java:153)
        at org.exist.start.Main.runEx(Main.java:292)
        at org.exist.start.Main.run(Main.java:158)
        at org.exist.start.Main.main(Main.java:95)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.codehaus.mojo.appassembler.booter.AppassemblerBooter.executeMain(AppassemblerBooter.java:257)
        at
org.codehaus.mojo.appassembler.booter.AppassemblerBooter.main(AppassemblerBooter.java:77)
Caused by: org.exist.EXistException: Initialisation of system collections
failed: Database is read-only
        at
org.exist.storage.BrokerPool.initialiseSystemCollection(BrokerPool.java:756)
        at
org.exist.storage.BrokerPool.initialiseSystemCollections(BrokerPool.java:769)
        at org.exist.storage.BrokerPool._initialize(BrokerPool.java:616)
        at org.exist.storage.BrokerPool.initialize(BrokerPool.java:451)
        at org.exist.storage.BrokerPools.configure(BrokerPools.java:177)
        at org.exist.storage.BrokerPools.configure(BrokerPools.java:131)
        at org.exist.xmldb.DatabaseImpl.configure(DatabaseImpl.java:125)
        ... 22 more
Caused by: java.io.IOException: Database is read-only
        at
org.exist.storage.NativeBroker.saveCollection(NativeBroker.java:1837)
        at
org.exist.storage.NativeBroker.createCollection(NativeBroker.java:782)
        at
org.exist.storage.NativeBroker.getOrCreateCollectionExplicit_rootCollection(NativeBroker.java:731)
        at
org.exist.storage.NativeBroker.getOrCreateCollectionExplicit(NativeBroker.java:675)
        at
org.exist.storage.NativeBroker.getOrCreateCollectionExplicit(NativeBroker.java:708)
        at
org.exist.storage.NativeBroker.getOrCreateCollection(NativeBroker.java:618)
        at
org.exist.storage.BrokerPool.initialiseSystemCollection(BrokerPool.java:744)
        ... 28 more
------------------------
Process execution failed

Re: [Exist-open] Reverse Proxy - Login issue

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

Terry,

sounds like you’ve hit issue #73 (https://github.com/eXist-db/dashboard/issues/73; see also https://github.com/eXist-db/dashboard/issues/166 ). Those issue threads contain some approaches to make the dashboard login available in reverse proxy environments. Maybe they are helpful in your case, too.

Greetings
Florian


Von: Terry Chilvers <tc...@ca...>
Gesendet: Mittwoch, 13. Juli 2022 18:17
An: eXist open Mailinglist <exi...@li...>
Betreff: [Exist-open] Reverse Proxy - Login issue

Hi,
We are migrating several eXist-db apps (eXist-db v2.2) to a new server running version 6. There’s a few XQuery issues that we’ve managed to fix but we are stuck on a problem with reverse proxy so hope someone can help.
We are running on Ubuntu 20.04LTS, and apache server for the reverse proxy. The reverse proxy works for most links we have tried but there’s a problem for one app that needs the user to be logged in. At present there is no login screen, this is an app for a limited audience so people have logged in via. the eXist-db dashboard but we want to do this through the reverse proxy.

Is there a way of using the reverse proxy to access the dashboard login, or should we write a login form for this application?
Any advice appreciated.

Thanks
Terry

--
Terry Chilvers
HSPS Infrastructure, Development and Operations Team Manager
Human, Social, and Political Science (HSPS), University of Cambridge.
IT Helpdesk: hel...@hs...<mailto:hel...@hs...>
Phone: 01223 (7)62842

[Exist-open] Reverse Proxy - Login issue

[Terry C. <tc...@ca...>]

Hi,
We are migrating several eXist-db apps (eXist-db v2.2) to a new server running version 6. There's a few XQuery issues that we've managed to fix but we are stuck on a problem with reverse proxy so hope someone can help.
We are running on Ubuntu 20.04LTS, and apache server for the reverse proxy. The reverse proxy works for most links we have tried but there's a problem for one app that needs the user to be logged in. At present there is no login screen, this is an app for a limited audience so people have logged in via. the eXist-db dashboard but we want to do this through the reverse proxy.

Is there a way of using the reverse proxy to access the dashboard login, or should we write a login form for this application?
Any advice appreciated.

Thanks
Terry

--
Terry Chilvers
HSPS Infrastructure, Development and Operations Team Manager
Human, Social, and Political Science (HSPS), University of Cambridge.
IT Helpdesk: hel...@hs...<mailto:hel...@hs...>
Phone: 01223 (7)62842

[Exist-open] Request for feedback: “Community Code Review and Merge Policy for the exist-db/exist Git Repository”

[Dario K. <dar...@tu...>]

**

*Dear eXist-db User,*

*

At the latest Community Call (Monday, July 11th 2022), we considered a 
proposal put forward to revise the “Community Code Review and Merge 
Policyfor the exist-db/exist Git Repository”.


Typically on a day-by-day basis the exist-db/exist repository has a 
volunteer team of between 1 to 4 people who are able to review and merge 
PRs (Pull Requests). We are very grateful to those volunteers who 
perform this involved work on a best effort basis in their spare time. 
Fortunately there is an increasing number of contributions to the 
project, but unfortunately this is outpacing the ability of our 
volunteers. We have 50+ open PRs at this moment!


The new policy proposal can be found at 
https://docs.google.com/document/d/1Y-f8P-p0VW6cmJSQrfGp4786qsMNW51qMp8h4Fh76-Y/edit?usp=sharing 
<https://docs.google.com/document/d/1Y-f8P-p0VW6cmJSQrfGp4786qsMNW51qMp8h4Fh76-Y/edit?usp=sharing>


Whilst this mostly concerns those directly contributing to the eXist-db 
Database Java Code Base, should you feel strongly about the topic, then 
we welcome your constructive feedback on the proposal. Should you feel 
uncomfortable with some aspect of the proposed policy, please make an 
alternative suggestion for that aspect.


All feedback must be submitted by Saturday, 16th July 2022 at 00:00 UTC. 
Feedback will be collated by Dario Kampkasparand should be emailed to: 
dar...@tu...


For reference a copy of this announcement can be found here: 
https://docs.google.com/document/d/1XSs4naogq0v8ah4fs319hTVMxsu34BBZJKaeyyAsFoE/edit?usp=sharing 
<https://docs.google.com/document/d/1XSs4naogq0v8ah4fs319hTVMxsu34BBZJKaeyyAsFoE/edit?usp=sharing>


Kind Regards.

Dario

*

-- 
Dario Kampkaspar
Leitung ZEiD – Zentrum für digitale Editionen

Technische Universtität Darmstadt
Universitäts- und Landesbibliothek
Magdalenenstr. 8
64289 Darmstadt

+49 6151 16-76292
+49 1512 9121599

Re: [Exist-open] sql:execute() without types

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

We do the following when we don't need the full shebang:

inside a <data> element we return

             $sql-result/* except $sql-result/(sql:row|sql:stack-trace),

             for $row in $sql-result/sql:row

           return

             <row>

             {

               for $column in $row/sql:*

               return

                 element {local-name($column)} {string($column)}

             }

             </row>

Good enough in most cases. You could tidy it up further by escaping 
$column names that are not XML compliant.

-p

On 10/07/2022 11:07, Adam Retter wrote:
> I am afraid not. You would be welcome to add a config option for the
> module or function to control this though...
>
> On Sun, 10 Jul 2022 at 01:16, Len Schultz<le...@wi...>  wrote:
>> Hello,
>>
>> For size reasons and the fact that I don’t need to know the types, I’d like to have sql:execute return results which don’t have type attributes.  Is this possible?
>>
>> --len
>>
>> _______________________________________________
>> 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 75G, 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] sql:execute() without types

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

I am afraid not. You would be welcome to add a config option for the
module or function to control this though...

On Sun, 10 Jul 2022 at 01:16, Len Schultz <le...@wi...> wrote:
>
> Hello,
>
> For size reasons and the fact that I don’t need to know the types, I’d like to have sql:execute return results which don’t have type attributes.  Is this possible?
>
> --len
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open



-- 
Adam Retter

eXist Core Developer
{ United Kingdom }
ad...@ex...

[Exist-open] sql:execute() without types

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

Hello,

For size reasons and the fact that I don’t need to know the types, I’d like to have sql:execute return results which don’t have type attributes.  Is this possible?

--len

Re: [Exist-open] exist-db.org is down

[Lars W. <la...@ex...>]

Hi Christian,

Juri just fixed it. Sorry for the inconvinience.

best regards

Lars


__
Lars Windauer
eXist Solutions GmbH

phone: + 49 30 83 22 5550
mobile: +49 170 587 1300
skype: windauer

Company Registration: HRB 713975, Amtsgericht Freiburg. Director: Wolfgang Meier.

> On 6. Jul 2022, at 14:25, Christian Wittern <cwi...@gm...> wrote:
> 
> Dear Wolfgang,
> 
> Thank you for looking into this.  I can see the website now, but the package manager still is not able to connect.
> 
> All the best,
> 
> Christian
> 
> On 06/07/2022 16.21, Wolfgang Meier wrote:
>> It should be up again now.
>> 
>> Best,
>> 
>> Wolfgang
>> 
>> 
>> 
>> Dear eXist users,
>> 
>> It seems that the exist-db.org website, together with the package
>> repository is down.  Here is hoping for a swift revival.
>> 
>> All the best,
>> 
>> Christian
>> 
>> 
>> 
>> _______________________________________________
>> 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

[Exist-open] Function call stack is empty, but XQueryContext.functionEnd() was called.

[Mike J. <Mik...@br...>]

Hello

I'm updating an app running on 5.x so that it works on 6.x. The app is working after updating the namespace for the templates, but I am now getting the following warnings appearing in the logs:

"(XQueryContext.java [functionEnd]:2396) - Function call stack is empty, but XQueryContext.functionEnd() was called. This could indicate a concurrency issue (shared XQueryContext?)"

It only appears when searching the documents and I get 12 warnings, no matter how many results are returned. 
I basically construct the XQuery based on form inputs and execute with util:eval. I'm having trouble replicating the issue by running similar queries in eXide directly.

Has anyone come across this before? Any obvious things I've missed?

I'm running eXist on an M1 Mac via the DMG installer.


Cheers
Mike

[Exist-open] Deprecation of templates:surround?

[Mike J. <Mik...@br...>]

Hello

I'm looking for some guidance. :-) I'm updating an app, currently running on 5.x, to make sure that it runs on 6.x. The only change needed to get it running was switching the templating namespace to 'http://exist-db.org/xquery/html-templating'. Great!

However, in the templating documentation (http://exist-db.org/exist/apps/doc/templating.xml), I can see that 'templates:surround' has been marked as 'deprecated'. What is the now recommended approach? The ''templates:surround' method is still used in the getting started docs for application development: http://exist-db.org/exist/apps/doc/development-starter

Thanks
Mike

Re: [Exist-open] exist-db.org is down

[Christian W. <cwi...@gm...>]

Dear Wolfgang,

Thank you for looking into this.  I can see the website now, but the 
package manager still is not able to connect.

All the best,

Christian

On 06/07/2022 16.21, Wolfgang Meier wrote:
> It should be up again now.
>
> Best,
>
> Wolfgang
>
>
>
>     Dear eXist users,
>
>     It seems that the exist-db.org <http://exist-db.org> website,
>     together with the package
>     repository is down.  Here is hoping for a swift revival.
>
>     All the best,
>
>     Christian
>
>
>
>     _______________________________________________
>     Exist-open mailing list
>     Exi...@li...
>     https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] exist-db.org is down

[Stephan M. <ste...@ru...>]

Dear Wolfgang,

http://exist-db.org/exist/apps/public-repo/public/shared-resources-0.9.1.xar <http://exist-db.org/exist/apps/public-repo/public/shared-resources-0.9.1.xar> throws an error…
Maybe related?

Best
Steph

> Am 06.07.2022 um 09:21 schrieb Wolfgang Meier <wol...@ex...>:
> 
> It should be up again now.
> 
> Best,
> 
> Wolfgang
> 
> 
> 
> Dear eXist users,
> 
> It seems that the exist-db.org <http://exist-db.org/> website, together with the package 
> repository is down.  Here is hoping for a swift revival.
> 
> All the best,
> 
> Christian
> 
> 
> 
> _______________________________________________
> 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] exist-db.org is down

[Wolfgang M. <wol...@ex...>]

It should be up again now.

Best,

Wolfgang



Dear eXist users,
>
> It seems that the exist-db.org website, together with the package
> repository is down.  Here is hoping for a swift revival.
>
> All the best,
>
> Christian
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] exist-db.org is down

[Christian W. <cwi...@gm...>]

Dear eXist users,

It seems that the exist-db.org website, together with the package 
repository is down.  Here is hoping for a swift revival.

All the best,

Christian

[Exist-open] Control content type of saved XML-specific resource

[Radu C. <rad...@sy...>]

Hi,

There is a discussion thread here about someone saving from Oxygen XML 
Editor a ".tmx" file and the file getting saved as binary on the Exist 
server side:

https://www.oxygenxml.com/forum/post66176.html#p66176

Could someone who knows more about the Exist API and content types help 
on the thread?

Regards,

Radu

Radu Coravu
Oxygen XML Editor

Re: [Exist-open] Remove XML declaration from static HTML?

[Ross M. <ros...@gm...>]

Disregard this message, the problem is in my JavaScript code, not the server

Ross

Sent from my iPhone

> On Jun 10, 2022, at 06:50, Ross Merrifield <ros...@gm...> wrote:
> 
> I am trying to serve a static HTML file in my project, but CSS (Bootstrap 5) is broken in the browser. I notice that eXist is inserting an XML declaration at the top of the document when returning to the browser, and removes my <!DOCTYPE html> element. It also won’t let me save the file unless is parses as valid XML. I changed the content-type of the file, and It is properly setting the content-type to text/html in the response to the browser though.
> 
> Is there a way I can make eXist not treat this file as XML or otherwise omit the declaration? I did some searching, but have only found a way to omit declaration on XQuery output, not a static file.
> 
> I am using eXist 6.0.1
> 
> Thanks,
> 
> Ross

[Exist-open] Remove XML declaration from static HTML?

[Ross M. <ros...@gm...>]

I am trying to serve a static HTML file in my project, but CSS (Bootstrap 5) is broken in the browser. I notice that eXist is inserting an XML declaration at the top of the document when returning to the browser, and removes my <!DOCTYPE html> element. It also won’t let me save the file unless is parses as valid XML. I changed the content-type of the file, and It is properly setting the content-type to text/html in the response to the browser though.

Is there a way I can make eXist not treat this file as XML or otherwise omit the declaration? I did some searching, but have only found a way to omit declaration on XQuery output, not a static file.

I am using eXist 6.0.1

Thanks,

Ross

Re: [Exist-open] Java Admin Client - Credentials from file system?

[<ml-...@fl...>]

Dannes,

i'm sorry - i've found that it was a problem of the db i've used, it was 
quite old (4.7.1) and it wasn't in a consistent state. After migrating 
to 6.0.1, there are no issues any more.

Florian


Am 04.06.2022 um 16:06 schrieb Dannes Wessels:
> Can you elaborate how large these files are? XML or binary?  Which exist version? What issues do you see?
> 
> IMO there should no real limitation on the document size…
> 
> D.
> 
>> On 24 May 2022, at 11:52, Florian Schmitt <mai...@fl...> wrote:
>>
>> In the meanwhile, i've tested using curl with HTTP PUT. This seems to work nicely for smaller files, but i encounter problems with bigger XML resources. Thus, ant may be a better solution.

Re: [Exist-open] Java Admin Client - Credentials from file system?

[<ml-...@fl...>]

Hi Adam,

for now, i've decided to put the credentials into the client.properties 
file. This works fine and allows for reading the credentials from the 
file system, but the user is restricted to just one set of credentials.

Maybe, it would be a useful feature to add a command line option for 
custom client.properties files. There's already an option to point the 
Java Admin Client to a different conf.xml file to access different 
databases, but not to a different properties file. I'll take a look at 
the source code, maybe i manage to create a PR to implement this.

Florian


Am 24.05.2022 um 23:35 schrieb Adam Retter:
> AFAIK the command line args are the only way at the moment. I would be 
> happy to see a PR that improves that though
> 
> On Tue, 24 May 2022, 11:52 Florian Schmitt, 
> <mai...@fl... 
> <mailto:mai...@fl...>> wrote:
> 
>     Hi all,
> 
>     is there a different way to provide authentication credentials to the
>     Java Admin Client other than the command line parameters, e.g. read
>     the user credentials from the file system? My use case is writing a
>     bash script to import some resources into eXist using the Java Admin
>     Client. Currently, the only way to authenticate seems to be using the
>     command line parameters -u and -P, providing the db user credentials
>     in clear text in the bash script. This is quite ugly. Other tools,
>     e.g. cUrl, allow for using .netrc files with appropriate access
>     rights. Is something similar available fot the command line client?
>     What's the best practice for this use case?
> 
>     Thanks in advance!
>     Florian
> 
> 
>     _______________________________________________
>     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] Java Admin Client - Credentials from file system?

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

Can you elaborate how large these files are? XML or binary?  Which exist version? What issues do you see?

IMO there should no real limitation on the document size…

D.

> On 24 May 2022, at 11:52, Florian Schmitt <mai...@fl...> wrote:
> 
> In the meanwhile, i've tested using curl with HTTP PUT. This seems to work nicely for smaller files, but i encounter problems with bigger XML resources. Thus, ant may be a better solution.

[Exist-open] Call for Presentations - Declarative Amsterdam 2022

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

Following the last three years' successful editions of Declarative Amsterdam, we are preparing a new edition to take place on 7 and 8 November 2022 at CWI, Science Park, Amsterdam.

We anticipate by November that we will be able to hold the conference on-site, but we are planning to broadcast and interact on-line as well.

The first day will feature tutorials, combining presentations and hands-on sessions to give an introduction to specific topics.

The second day is a symposium, and will consist of shorter presentations. Speakers can discuss new ideas, frameworks, applications of declarative methods, and best practices.


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.5 and 2.5 hours, and preferably include hands-on sessions for participants. Presentations on the second day can be between 30 and 45 minutes. We plan to create the possibility of online presentation via video.

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

Please submit your proposals here: <https://declarative.amsterdam/submit?model=da-call-for-presentations>  https://declarative.amsterdam/submit?model=da-call-for-presentations


Timeline


Submission deadline: 31 July

Acceptance: Middle of September

Conference: 7 and 8 November.

For papers and topics from previous years, see the website: <http://declarative.amsterdam/>  http://declarative.amsterdam/


A Declarative Challenge


This year, we also feature a declarative challenge! The challenge is: Create a (small) application that makes use of invisible XML. See <https://declarative.amsterdam/show?page=da-challenge>  the web page for full details.


Declarative Amsterdam 2021 presentation videos, slides, papers


The submitted papers, presentation videos, and slides from last year's edition are online: see the links on <https://declarative.amsterdam/program-2021>  Declarative Amsterdam 2021 to the respective papers.

 

All the best,

Declarative Amsterdam 2022 organising committee

  <https://lh5.googleusercontent.com/IgdjbCrChJUsNGHdZpDgwM2bqP_ZSRc1_PHmIXS2BhbZ2-KAN1x8PiohX7ZeR4ADPSBugpk59OxR0NuFXIWoCzkUhvVzPURomFRx0y-xAElAHLQ6Z88XQzpff_0h2qYDrKeDwQfe7xNHovs8Wg> 

[Exist-open] Running eXist-db in debug mode in IntelliJ IDEA

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

I had looked for instructions on running exits in debug mode and was unsuccessful.  I then took a look at my local IntelliJ IDEA and saw Java Admin Client in the run configurations.  So here is a very quick how to on running eXist-db in debug mode.


Select the run configuration ‘Local Jetty Server’



Click on the debug icon



Click in the sidebar of the source code where the line numbers are and a red dot shall appear.  That is a breakpoint.  Go through your actions in eXist-db until one of the breakpoints is tripped.

Re: [Exist-open] Java Admin Client - Credentials from file system?

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

AFAIK the command line args are the only way at the moment. I would be
happy to see a PR that improves that though

On Tue, 24 May 2022, 11:52 Florian Schmitt, <
mai...@fl...> wrote:

> Hi all,
>
> is there a different way to provide authentication credentials to the
> Java Admin Client other than the command line parameters, e.g. read
> the user credentials from the file system? My use case is writing a
> bash script to import some resources into eXist using the Java Admin
> Client. Currently, the only way to authenticate seems to be using the
> command line parameters -u and -P, providing the db user credentials
> in clear text in the bash script. This is quite ugly. Other tools,
> e.g. cUrl, allow for using .netrc files with appropriate access
> rights. Is something similar available fot the command line client?
> What's the best practice for this use case?
>
> Thanks in advance!
> Florian
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] Ignore processing instructions in indexing

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

Hi Stefan,

How strange. This definitely sounds like a bug. Would you please open a bug
report at https://github.com/eXist-db/exist/issues/new/choose and, if
possible, supply an XQSuite test to help the developers reproduce
the problem?

Thanks,
Joe

On Mon, May 16, 2022 at 4:20 AM Stefan Dumont <du...@bb...> wrote:

> Hi Dannes,
>
> here is the index configuration:
>
> https://gist.github.com/StefanDumont/0ab72c24e069f2231ac28bf8cff0b90e
>
> Everything works fine exept that obviously text in an Oxygen Processing
> Instruction is indexed and found by ft:query(). Checking again the
> problem, I also found out, that the problem occurs only, when I use a
> wildcard in ft:query() (with XML syntax). When I search for the specific
> word ("Natural" vs "Natur*") there is no search result (i.e. correct
> behaviour).
>
> Thanks
>
> Stefan
>
> Am 15.05.2022 um 18:29 schrieb Dannes Wessels:
> > Hi,
> >
> > Please could you share your index configuration?
> >
> > Cheers
> >
> > Dannes
> >
> >> On 11 May 2022, at 20:36, Stefan Dumont <du...@bb...> wrote:
> >>
> >> Hi all,
> >>
> >> since we're using Oxygen XML Author for editing our TEI-XML, the
> editors also use the possibility to comment (temporarily) the edited text.
> Oxygen stores these comments as XML Processing Instructions (PI) in the
> TEI-XML. Of course, we don't want to show them. But by indexing text with
> the lucene index these PIs are also indexed and therefore will be find by
> ft:query(). Is there a way to ignore them for indexing like other elements?
> I didn't find a way ...
> >>
> >> Thanks for hints & kind regards
> >>
> >> Stefan
> >>
> >> --
> >> Berlin-Brandenburgische Akademie der Wissenschaften
> >> TELOTA - Digital Humanities
> >> Jägerstraße 22/23
> >> 10117 Berlin
> >>
> >> Tel.: 030 / 20 370 -492
> >> du...@bb...
> >> http://www.bbaw.de/die-akademie/mitarbeiter/dumont
> >> http://www.bbaw.de/telota
> >>
> >>
> >> _______________________________________________
> >> Exist-open mailing list
> >> Exi...@li...
> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>
> --
> Berlin-Brandenburgische Akademie der Wissenschaften
> TELOTA - Digital Humanities
> Jägerstraße 22/23
> 10117 Berlin
>
> Tel.: 030 / 20 370 -492
> du...@bb...
> http://www.bbaw.de/die-akademie/mitarbeiter/dumont
> http://www.bbaw.de/telota
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>