From: Wolfgang M. <wol...@ex...> - 2019-02-20 10:30:37
|
Dear Christian, > "Exception while reading lucene index directory: Lock obtain timed out“ > Please make sure there’s no eXist process running anymore and manually remove the .lock files from webapp/WEB-INF/data/lucene and range. Wolfgang |
From: Dominic L. <dom...@gm...> - 2019-08-07 09:42:47
|
Dear All, After attempting to restore of some files to the production server all requests now return the same java.nio.file.NoSuchFileException error: 2019-08-07 09:32:26,967 [qtp337777621-30] WARN (HttpChannel.java [handleException]:584) - /exist/apps/84000-reading-room/ java.nio.file.NoSuchFileException: /opt/eXist-4.7.0/./webapp/WEB-INF/data/blob/71cd0d980914b99260d916f07e8ac17e1ca361b368cdb8f11aa42a3fa9e936e2 I have tried restoring the entire database but it didn't help. There is probably some documentation but this is the production server so I'm a little panicky right now. Any pointers on how to get service running again would be appreciated. Thanks, Dominic |
From: Ihe O. <ihe...@gm...> - 2020-06-02 10:11:11
|
In eXide - collection("/db/apps/pathToXSDs" )//xs:extension[@base eq "someType"]/ancestor::xs:complexType/@name Tells me how many query results were returned but doesn't show them. If I wrap the @name in a call to string I get the results displayed in eXide but should that be necessary? Asking for forbearance here due to rustiness of my Xquery |
From: Peter S. <st...@we...> - 2020-06-02 11:07:50
Attachments:
signature.asc
|
Hi, I guess the problem is that you cannot directly output attribute nodes. In fact, the „direct output“ in eXide outputs the error message "Error SENR0001: attribute ’name' has no parent element“. Although I’ve been hit by this issue myself, I think eXide should not behave differently than other processors? Best Peter > Am 02.06.2020 um 12:10 schrieb Ihe Onwuka <ihe...@gm...>: > > In eXide - > > collection("/db/apps/pathToXSDs" )//xs:extension[@base eq "someType"]/ancestor::xs:complexType/@name > > Tells me how many query results were returned but doesn't show them. If I wrap the @name in a call to string I get the results displayed in eXide but should that be necessary? > > Asking for forbearance here due to rustiness of my Xquery > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
From: Jean-Paul R. <re...@gm...> - 2020-06-02 11:21:08
|
This isn't an issue with eXide - the same result appears in Oxygen (because the "parent element error" noted by Peter is produced from eXist). Why the attribute node isn't returned is something perhaps one of the engineers can explain... As it goes, unless I am absolutely sure of the content type, I use /data(@myattribute) to output the value. On the other hand, if simply testing or transforming the value, one can reference the attribute without explicitly extracting the value. Cheers, JPR On Tue, Jun 2, 2020 at 1:08 PM Peter Stadler <st...@we...> wrote: > Hi, > > I guess the problem is that you cannot directly output attribute nodes. In > fact, the „direct output“ in eXide outputs the error message "Error > SENR0001: attribute ’name' has no parent element“. > Although I’ve been hit by this issue myself, I think eXide should not > behave differently than other processors? > > Best > Peter > > > Am 02.06.2020 um 12:10 schrieb Ihe Onwuka <ihe...@gm...>: > > > > In eXide - > > > > collection("/db/apps/pathToXSDs" )//xs:extension[@base eq > "someType"]/ancestor::xs:complexType/@name > > > > Tells me how many query results were returned but doesn't show them. If > I wrap the @name in a call to string I get the results displayed in eXide > but should that be necessary? > > > > Asking for forbearance here due to rustiness of my Xquery > > _______________________________________________ > > 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 > |
From: Joe W. <jo...@gm...> - 2020-06-02 22:31:41
|
This is actually a bug with util:expand that prevents eXide from properly displaying attributes despite adaptive serialization's ability to output attribute nodes. See https://github.com/eXist-db/exist/issues/1562#issuecomment-332227118. On Tue, Jun 2, 2020 at 7:21 AM Jean-Paul Rehr <re...@gm...> wrote: > This isn't an issue with eXide - the same result appears in Oxygen > (because the "parent element error" noted by Peter is produced from eXist). > > Why the attribute node isn't returned is something perhaps one of the > engineers can explain... > > As it goes, unless I am absolutely sure of the content type, I use > /data(@myattribute) to output the value. On the other hand, if simply > testing or transforming the value, one can reference the attribute without > explicitly extracting the value. > > Cheers, > JPR > > On Tue, Jun 2, 2020 at 1:08 PM Peter Stadler < > st...@we...> wrote: > >> Hi, >> >> I guess the problem is that you cannot directly output attribute nodes. >> In fact, the „direct output“ in eXide outputs the error message "Error >> SENR0001: attribute ’name' has no parent element“. >> Although I’ve been hit by this issue myself, I think eXide should not >> behave differently than other processors? >> >> Best >> Peter >> >> > Am 02.06.2020 um 12:10 schrieb Ihe Onwuka <ihe...@gm...>: >> > >> > In eXide - >> > >> > collection("/db/apps/pathToXSDs" )//xs:extension[@base eq >> "someType"]/ancestor::xs:complexType/@name >> > >> > Tells me how many query results were returned but doesn't show them. >> If I wrap the @name in a call to string I get the results displayed in >> eXide but should that be necessary? >> > >> > Asking for forbearance here due to rustiness of my Xquery >> > _______________________________________________ >> > 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 mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |