Menu
▾
▴
exist-open — Open discussion
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(31) |
Nov
(25) |
Dec
(33) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(48) |
Feb
(62) |
Mar
(22) |
Apr
(29) |
May
(9) |
Jun
(45) |
Jul
(28) |
Aug
(41) |
Sep
(60) |
Oct
(96) |
Nov
(99) |
Dec
(70) |
| 2003 |
Jan
(98) |
Feb
(159) |
Mar
(164) |
Apr
(150) |
May
(143) |
Jun
(97) |
Jul
(184) |
Aug
(143) |
Sep
(207) |
Oct
(126) |
Nov
(159) |
Dec
(165) |
| 2004 |
Jan
(131) |
Feb
(229) |
Mar
(220) |
Apr
(212) |
May
(320) |
Jun
(223) |
Jul
(191) |
Aug
(390) |
Sep
(261) |
Oct
(229) |
Nov
(215) |
Dec
(184) |
| 2005 |
Jan
(221) |
Feb
(312) |
Mar
(336) |
Apr
(273) |
May
(359) |
Jun
(277) |
Jul
(303) |
Aug
(321) |
Sep
(256) |
Oct
(415) |
Nov
(428) |
Dec
(508) |
| 2006 |
Jan
(585) |
Feb
(419) |
Mar
(496) |
Apr
(296) |
May
(403) |
Jun
(404) |
Jul
(553) |
Aug
(296) |
Sep
(252) |
Oct
(416) |
Nov
(414) |
Dec
(245) |
| 2007 |
Jan
(354) |
Feb
(422) |
Mar
(389) |
Apr
(298) |
May
(397) |
Jun
(318) |
Jul
(315) |
Aug
(339) |
Sep
(253) |
Oct
(317) |
Nov
(350) |
Dec
(264) |
| 2008 |
Jan
(353) |
Feb
(313) |
Mar
(433) |
Apr
(383) |
May
(343) |
Jun
(355) |
Jul
(321) |
Aug
(338) |
Sep
(242) |
Oct
(206) |
Nov
(199) |
Dec
(279) |
| 2009 |
Jan
(327) |
Feb
(221) |
Mar
(280) |
Apr
(278) |
May
(237) |
Jun
(345) |
Jul
(322) |
Aug
(324) |
Sep
(676) |
Oct
(586) |
Nov
(735) |
Dec
(329) |
| 2010 |
Jan
(619) |
Feb
(424) |
Mar
(529) |
Apr
(241) |
May
(312) |
Jun
(554) |
Jul
(698) |
Aug
(576) |
Sep
(408) |
Oct
(268) |
Nov
(391) |
Dec
(426) |
| 2011 |
Jan
(629) |
Feb
(512) |
Mar
(465) |
Apr
(467) |
May
(475) |
Jun
(403) |
Jul
(426) |
Aug
(542) |
Sep
(418) |
Oct
(620) |
Nov
(614) |
Dec
(358) |
| 2012 |
Jan
(357) |
Feb
(466) |
Mar
(344) |
Apr
(215) |
May
(408) |
Jun
(375) |
Jul
(241) |
Aug
(260) |
Sep
(401) |
Oct
(461) |
Nov
(498) |
Dec
(294) |
| 2013 |
Jan
(453) |
Feb
(447) |
Mar
(434) |
Apr
(326) |
May
(295) |
Jun
(471) |
Jul
(463) |
Aug
(278) |
Sep
(525) |
Oct
(343) |
Nov
(389) |
Dec
(405) |
| 2014 |
Jan
(564) |
Feb
(324) |
Mar
(319) |
Apr
(319) |
May
(384) |
Jun
(259) |
Jul
(210) |
Aug
(219) |
Sep
(315) |
Oct
(478) |
Nov
(207) |
Dec
(316) |
| 2015 |
Jan
(222) |
Feb
(234) |
Mar
(201) |
Apr
(145) |
May
(367) |
Jun
(318) |
Jul
(195) |
Aug
(210) |
Sep
(234) |
Oct
(248) |
Nov
(217) |
Dec
(189) |
| 2016 |
Jan
(219) |
Feb
(177) |
Mar
(110) |
Apr
(91) |
May
(159) |
Jun
(124) |
Jul
(192) |
Aug
(119) |
Sep
(125) |
Oct
(64) |
Nov
(80) |
Dec
(68) |
| 2017 |
Jan
(156) |
Feb
(312) |
Mar
(386) |
Apr
(217) |
May
(89) |
Jun
(115) |
Jul
(79) |
Aug
(122) |
Sep
(100) |
Oct
(99) |
Nov
(129) |
Dec
(77) |
| 2018 |
Jan
(106) |
Feb
(78) |
Mar
(160) |
Apr
(73) |
May
(110) |
Jun
(160) |
Jul
(93) |
Aug
(92) |
Sep
(75) |
Oct
(147) |
Nov
(114) |
Dec
(97) |
| 2019 |
Jan
(141) |
Feb
(78) |
Mar
(158) |
Apr
(60) |
May
(123) |
Jun
(54) |
Jul
(44) |
Aug
(147) |
Sep
(117) |
Oct
(54) |
Nov
(74) |
Dec
(96) |
| 2020 |
Jan
(113) |
Feb
(125) |
Mar
(142) |
Apr
(57) |
May
(71) |
Jun
(99) |
Jul
(58) |
Aug
(81) |
Sep
(49) |
Oct
(50) |
Nov
(63) |
Dec
(37) |
| 2021 |
Jan
(37) |
Feb
(45) |
Mar
(39) |
Apr
(18) |
May
(14) |
Jun
(9) |
Jul
(44) |
Aug
(23) |
Sep
(13) |
Oct
(31) |
Nov
(13) |
Dec
(33) |
| 2022 |
Jan
(17) |
Feb
(8) |
Mar
(32) |
Apr
(7) |
May
(17) |
Jun
(7) |
Jul
(36) |
Aug
(29) |
Sep
(9) |
Oct
(20) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(30) |
Feb
(37) |
Mar
(23) |
Apr
(1) |
May
(14) |
Jun
(5) |
Jul
(3) |
Aug
(6) |
Sep
(5) |
Oct
(48) |
Nov
(4) |
Dec
(29) |
| 2024 |
Jan
(1) |
Feb
|
Mar
(21) |
Apr
(6) |
May
(16) |
Jun
(41) |
Jul
(11) |
Aug
(17) |
Sep
(16) |
Oct
(11) |
Nov
(3) |
Dec
(9) |
| 2025 |
Jan
(7) |
Feb
(7) |
Mar
(6) |
Apr
(6) |
May
(30) |
Jun
(8) |
Jul
(10) |
Aug
(4) |
Sep
(10) |
Oct
(32) |
Nov
(3) |
Dec
|
|
From: <gb...@xs...> - 2021-05-11 15:35:08
|
Hi Michael, Thanks, we checked the disk space: Filesystem Size Used Avail Use% Mounted on /dev/sda2 394G 266G 109G 72% / This should be sufficient, the problem must be somewhere else. Kind regards, Gerrit > On 11 May 2021, at 16:17, Michael Westbay <wes...@ja...> wrote: > > Hi Gerrit, > > Please check the amount of free disk space on the EXIST_HOME drive. One possibility is that the free space on the drive is below the threshold and it's gone into READ-ONLY mode. This happens to me occasionally when I have daily full backups happening to the same drive. > > Hope this helps. > > Take care. > > > 2021年5月11日(火) 23:12 Gerrit Boers <gb...@xs... <mailto:gb...@xs...>>: > Hi, > > We have strange problem with eXist-db 5.2 where it is no longer possible to open files with the Java client and oXygen XML editor. Storing data also does not work but retrieving does work. This happens after the server has been up for a while. > > Here’s the error message in the Java client: > > org.xmldb.api.base.XMLDBException: Failed to invoke method getDocumentData in class org.exist.xmlrpc.RpcConnection: java.nio.file.NoSuchFileException: /tmp/exist-db-temp-file-manager-4799381294643377191/exist-db-temp-1519535726255396432.tmp > at org.exist.xmldb.RemoteCollection.execute(RemoteCollection.java:127) > at org.exist.xmldb.AbstractRemoteResource.getRemoteContentIntoLocalFile(AbstractRemoteResource.java:278) > at org.exist.xmldb.AbstractRemoteResource.getExtendedContentInternal(AbstractRemoteResource.java:435) > at org.exist.xmldb.RemoteBinaryResource.getExtendedContent(RemoteBinaryResource.java:79) > at org.exist.xmldb.AbstractRemoteResource.getContent(AbstractRemoteResource.java:86) > at org.exist.client.QueryDialog.<init>(QueryDialog.java:137) > at org.exist.client.ClientFrame$TableMouseListener.mouseClicked(ClientFrame.java:1411) > at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:270) > at java.awt.Component.processMouseEvent(Component.java:6536) > at javax.swing.JComponent.processMouseEvent(JComponent.java:3324) > at java.awt.Component.processEvent(Component.java:6298) > at java.awt.Container.processEvent(Container.java:2236) > at java.awt.Component.dispatchEventImpl(Component.java:4889) > at java.awt.Container.dispatchEventImpl(Container.java:2294) > at java.awt.Component.dispatchEvent(Component.java:4711) > at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888) > at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4534) > at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466) > at java.awt.Container.dispatchEventImpl(Container.java:2280) > at java.awt.Window.dispatchEventImpl(Window.java:2746) > at java.awt.Component.dispatchEvent(Component.java:4711) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) > at java.awt.EventQueue.access$500(EventQueue.java:97) > at java.awt.EventQueue$3.run(EventQueue.java:709) > at java.awt.EventQueue$3.run(EventQueue.java:703) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) > at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:90) > at java.awt.EventQueue$4.run(EventQueue.java:731) > at java.awt.EventQueue$4.run(EventQueue.java:729) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) > at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) > at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) > Caused by: org.apache.xmlrpc.XmlRpcException: Failed to invoke method getDocumentData in class org.exist.xmlrpc.RpcConnection: java.nio.file.NoSuchFileException: /tmp/exist-db-temp-file-manager-4799381294643377191/exist-db-temp-1519535726255396432.tmp > at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:197) > at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:156) > at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143) > at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69) > at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56) > at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167) > at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158) > at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147) > at org.exist.xmldb.RemoteCollection.execute(RemoteCollection.java:125) > ... 38 more > > Does anybody have a clue what’s going on here? > > Kind regards, > > Gerrit Boers > > > > _______________________________________________ > 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> > > > -- > Michael Westbay > Writer/System Administrator > http://www.japanesebaseball.com/ <http://www.japanesebaseball.com/> |
|
From: Michael W. <wes...@ja...> - 2021-05-11 14:17:38
|
Hi Gerrit, Please check the amount of free disk space on the EXIST_HOME drive. One possibility is that the free space on the drive is below the threshold and it's gone into READ-ONLY mode. This happens to me occasionally when I have daily full backups happening to the same drive. Hope this helps. Take care. 2021年5月11日(火) 23:12 Gerrit Boers <gb...@xs...>: > Hi, > > We have strange problem with eXist-db 5.2 where it is no longer possible > to open files with the Java client and oXygen XML editor. Storing data also > does not work but retrieving does work. This happens after the server has > been up for a while. > > Here’s the error message in the Java client: > > org.xmldb.api.base.XMLDBException: Failed to invoke method getDocumentData > in class org.exist.xmlrpc.RpcConnection: java.nio.file.NoSuchFileException: > /tmp/exist-db-temp-file-manager-4799381294643377191/exist-db-temp-1519535726255396432.tmp > at > org.exist.xmldb.RemoteCollection.execute(RemoteCollection.java:127) > at > org.exist.xmldb.AbstractRemoteResource.getRemoteContentIntoLocalFile(AbstractRemoteResource.java:278) > at > org.exist.xmldb.AbstractRemoteResource.getExtendedContentInternal(AbstractRemoteResource.java:435) > at > org.exist.xmldb.RemoteBinaryResource.getExtendedContent(RemoteBinaryResource.java:79) > at > org.exist.xmldb.AbstractRemoteResource.getContent(AbstractRemoteResource.java:86) > at org.exist.client.QueryDialog.<init>(QueryDialog.java:137) > at > org.exist.client.ClientFrame$TableMouseListener.mouseClicked(ClientFrame.java:1411) > at > java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:270) > at java.awt.Component.processMouseEvent(Component.java:6536) > at javax.swing.JComponent.processMouseEvent(JComponent.java:3324) > at java.awt.Component.processEvent(Component.java:6298) > at java.awt.Container.processEvent(Container.java:2236) > at java.awt.Component.dispatchEventImpl(Component.java:4889) > at java.awt.Container.dispatchEventImpl(Container.java:2294) > at java.awt.Component.dispatchEvent(Component.java:4711) > at > java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888) > at > java.awt.LightweightDispatcher.processMouseEvent(Container.java:4534) > at > java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466) > at java.awt.Container.dispatchEventImpl(Container.java:2280) > at java.awt.Window.dispatchEventImpl(Window.java:2746) > at java.awt.Component.dispatchEvent(Component.java:4711) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) > at java.awt.EventQueue.access$500(EventQueue.java:97) > at java.awt.EventQueue$3.run(EventQueue.java:709) > at java.awt.EventQueue$3.run(EventQueue.java:703) > at java.security.AccessController.doPrivileged(Native Method) > at > java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) > at > java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:90) > at java.awt.EventQueue$4.run(EventQueue.java:731) > at java.awt.EventQueue$4.run(EventQueue.java:729) > at java.security.AccessController.doPrivileged(Native Method) > at > java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) > at > java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) > at > java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) > at > java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) > at > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) > at > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) > Caused by: org.apache.xmlrpc.XmlRpcException: Failed to invoke method > getDocumentData in class org.exist.xmlrpc.RpcConnection: > java.nio.file.NoSuchFileException: > /tmp/exist-db-temp-file-manager-4799381294643377191/exist-db-temp-1519535726255396432.tmp > at > org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:197) > at > org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:156) > at > org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143) > at > org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69) > at > org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56) > at > org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167) > at > org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158) > at > org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147) > at > org.exist.xmldb.RemoteCollection.execute(RemoteCollection.java:125) > ... 38 more > > Does anybody have a clue what’s going on here? > > Kind regards, > > Gerrit Boers > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Michael Westbay Writer/System Administrator http://www.japanesebaseball.com/ |
|
From: Gerrit B. <gb...@xs...> - 2021-05-11 14:11:56
|
Hi, We have strange problem with eXist-db 5.2 where it is no longer possible to open files with the Java client and oXygen XML editor. Storing data also does not work but retrieving does work. This happens after the server has been up for a while. Here’s the error message in the Java client: org.xmldb.api.base.XMLDBException: Failed to invoke method getDocumentData in class org.exist.xmlrpc.RpcConnection: java.nio.file.NoSuchFileException: /tmp/exist-db-temp-file-manager-4799381294643377191/exist-db-temp-1519535726255396432.tmp at org.exist.xmldb.RemoteCollection.execute(RemoteCollection.java:127) at org.exist.xmldb.AbstractRemoteResource.getRemoteContentIntoLocalFile(AbstractRemoteResource.java:278) at org.exist.xmldb.AbstractRemoteResource.getExtendedContentInternal(AbstractRemoteResource.java:435) at org.exist.xmldb.RemoteBinaryResource.getExtendedContent(RemoteBinaryResource.java:79) at org.exist.xmldb.AbstractRemoteResource.getContent(AbstractRemoteResource.java:86) at org.exist.client.QueryDialog.<init>(QueryDialog.java:137) at org.exist.client.ClientFrame$TableMouseListener.mouseClicked(ClientFrame.java:1411) at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:270) at java.awt.Component.processMouseEvent(Component.java:6536) at javax.swing.JComponent.processMouseEvent(JComponent.java:3324) at java.awt.Component.processEvent(Component.java:6298) at java.awt.Container.processEvent(Container.java:2236) at java.awt.Component.dispatchEventImpl(Component.java:4889) at java.awt.Container.dispatchEventImpl(Container.java:2294) at java.awt.Component.dispatchEvent(Component.java:4711) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4534) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466) at java.awt.Container.dispatchEventImpl(Container.java:2280) at java.awt.Window.dispatchEventImpl(Window.java:2746) at java.awt.Component.dispatchEvent(Component.java:4711) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) at java.awt.EventQueue.access$500(EventQueue.java:97) at java.awt.EventQueue$3.run(EventQueue.java:709) at java.awt.EventQueue$3.run(EventQueue.java:703) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:90) at java.awt.EventQueue$4.run(EventQueue.java:731) at java.awt.EventQueue$4.run(EventQueue.java:729) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) Caused by: org.apache.xmlrpc.XmlRpcException: Failed to invoke method getDocumentData in class org.exist.xmlrpc.RpcConnection: java.nio.file.NoSuchFileException: /tmp/exist-db-temp-file-manager-4799381294643377191/exist-db-temp-1519535726255396432.tmp at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:197) at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:156) at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143) at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69) at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158) at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147) at org.exist.xmldb.RemoteCollection.execute(RemoteCollection.java:125) ... 38 more Does anybody have a clue what’s going on here? Kind regards, Gerrit Boers |
|
From: Joe W. <jo...@gm...> - 2021-04-28 21:30:15
|
Hi Christian, You can download a nightly build of 5.3.0-SNAPSHOT via the link at https://exist-db.org/exist/apps/homepage/index.html#download. Joe On Wed, Apr 28, 2021 at 5:20 PM Christian Achter < chr...@ge...> wrote: > Thanks Nick and Jean-Paul. I think I will try this 5.3 update. > > But ... > > ... where do I get the 5.3.0 snapshot? I cannot find anything on > exist-db.org, only here on docker.com: > > > https://hub.docker.com/layers/existdb/existdb/5.3.0-SNAPSHOT/images/sha256-7192e3988189ff22d0ddc199888619564de457ae604a14eda5ed25eeb9270a3e?context=explore > > Does it mean I have to go with Docker to update to 5.3? Oh no, so far, I > always used the exist-installer-5.2.0.jar to install eXist-db. > > Thanks and kind regards > Christian > > > Am 28.04.21 um 21:26 schrieb Jean-Paul Rehr: > > Sorry, it seems my draft email sent off with a hotkey or something. > > As Nick says, this is one of the big bugs in 5.2. The instances I have > still in 5.2 I never rename collections from anywhere - I use remove, copy, > etc in code - just to avoid possible problems. And like Nick, I've moved > over a number of production instances to 5.3 snapshot without issue for > months now. > > JPR > > > > On Wed, Apr 28, 2021 at 8:50 PM Nick Sincaglia <nsi...@nu...> > wrote: > >> Christian, >> This is a known issue that eXist-db 5.3.0 SNAPSHOT fixes. We also >> experienced this same issue and it was recommended that we move to this >> newer version and we have not had any problems since doing so. >> >> Nick >> >> On 4/28/21 12:55 PM, Christian Achter wrote: >> >> Dear all, >> >> this happened to me now several times during the past half year, and on >> different machines. We are using eXist 5.2.0 on several machines (Ubuntu). >> >> Sometimes, when a user renames e.g. an existing directory/collection, the >> renaming works - somehow. The name is changed, but the content of the >> collection is not accessible anymore. Re-renaming the collection is not >> possible. Deleting the renamed collection is not possible. >> >> Creating a new collection with the old name is also not possible. eXist >> then reports that this collection already exists (also it was renamed). >> >> Our users use Oxygen XML Author to handle our XML files and collections. >> >> As an admin, I use the following tools to try to get rid of those >> collections: >> >> - WebDAV (via Oxygen XML Author) >> - eXide in the browser and the file manager you can access from there >> - Java Admin Client (bin/client.sh) >> >> All of those do not work. >> >> So in these cases, I have Schroedinger's collections: I can see them in >> the tools mentioned above but I not access them because they do not exist >> anymore. At the same time, I can not delete or replace them as they somehow >> still exist. >> >> Fun fact: I even had XML files I could not access via any of the tools >> above, but they could be accessed by XQuery scripts that were exactly >> reading these files. >> >> Usually, in these cases, I re-install eXist-db and restore a current >> backup. But I am pretty tired of this workaround. >> >> Is this a problem of indexing? How can it be solved? >> >> Thanks for all advise in advance. >> >> Christian >> >> >> _______________________________________________ >> Exist-open mailing lis...@li...://lists.sourceforge.net/lists/listinfo/exist-open >> >> >> -- >> Nick Sincaglia >> President/Founder >> NueMeta, LLC >> Digital Media & Technology >> Phone: +1-6...@nu... http://www.nuemeta.com >> Skype: nsincaglia >> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > > > _______________________________________________ > Exist-open mailing lis...@li...://lists.sourceforge.net/lists/listinfo/exist-open > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Christian A. <chr...@ge...> - 2021-04-28 21:20:12
|
Thanks Nick and Jean-Paul. I think I will try this 5.3 update. But ... ... where do I get the 5.3.0 snapshot? I cannot find anything on exist-db.org, only here on docker.com: https://hub.docker.com/layers/existdb/existdb/5.3.0-SNAPSHOT/images/sha256-7192e3988189ff22d0ddc199888619564de457ae604a14eda5ed25eeb9270a3e?context=explore Does it mean I have to go with Docker to update to 5.3? Oh no, so far, I always used the exist-installer-5.2.0.jar to install eXist-db. Thanks and kind regards Christian Am 28.04.21 um 21:26 schrieb Jean-Paul Rehr: > Sorry, it seems my draft email sent off with a hotkey or something. > > As Nick says, this is one of the big bugs in 5.2. The instances I have > still in 5.2 I never rename collections from anywhere - I use remove, > copy, etc in code - just to avoid possible problems. And like Nick, > I've moved over a number of production instances to 5.3 snapshot > without issue for months now. > > JPR > > > > On Wed, Apr 28, 2021 at 8:50 PM Nick Sincaglia <nsi...@nu... > <mailto:nsi...@nu...>> wrote: > > Christian, > This is a known issue that eXist-db 5.3.0 SNAPSHOT fixes. We > also experienced this same issue and it was recommended that we > move to this newer version and we have not had any problems since > doing so. > > Nick > > On 4/28/21 12:55 PM, Christian Achter wrote: >> >> Dear all, >> >> this happened to me now several times during the past half year, >> and on different machines. We are using eXist 5.2.0 on several >> machines (Ubuntu). >> >> Sometimes, when a user renames e.g. an existing >> directory/collection, the renaming works - somehow. The name is >> changed, but the content of the collection is not accessible >> anymore. Re-renaming the collection is not possible. Deleting the >> renamed collection is not possible. >> >> Creating a new collection with the old name is also not possible. >> eXist then reports that this collection already exists (also it >> was renamed). >> >> Our users use Oxygen XML Author to handle our XML files and >> collections. >> >> As an admin, I use the following tools to try to get rid of those >> collections: >> >> * WebDAV (via Oxygen XML Author) >> * eXide in the browser and the file manager you can access from >> there >> * Java Admin Client (bin/client.sh) >> >> All of those do not work. >> >> So in these cases, I have Schroedinger's collections: I can see >> them in the tools mentioned above but I not access them because >> they do not exist anymore. At the same time, I can not delete or >> replace them as they somehow still exist. >> >> Fun fact: I even had XML files I could not access via any of the >> tools above, but they could be accessed by XQuery scripts that >> were exactly reading these files. >> >> Usually, in these cases, I re-install eXist-db and restore a >> current backup. But I am pretty tired of this workaround. >> >> Is this a problem of indexing? How can it be solved? >> >> Thanks for all advise in advance. >> >> 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> > > -- > Nick Sincaglia > President/Founder > NueMeta, LLC > Digital Media & Technology > Phone: +1-630-303-7035 > nsi...@nu... <mailto:nsi...@nu...> > http://www.nuemeta.com <http://www.nuemeta.com> > Skype: nsincaglia > > _______________________________________________ > Exist-open mailing list > Exi...@li... > <mailto:Exi...@li...> > https://lists.sourceforge.net/lists/listinfo/exist-open > <https://lists.sourceforge.net/lists/listinfo/exist-open> > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Nick S. <nsi...@nu...> - 2021-04-28 21:06:19
|
Christian, I believe this issues happens when you are using WebDAV. I don't believe it happens when you use xmlrpc. We use Oxygen and connect over xmlrpc but we also connect using applications such as CrossFTP and Panic! Transmit using WebDAV. I believe it was us using WebDAV when renaming folders that corrupted them. Nick On 4/28/21 3:53 PM, Christian Achter wrote: > Dear Olaf, > > thanks for your response. No, I cannot reproduce this. The problem > occurs just sometimes. > > The last incidence already happened some time ago but I might be able > to find the right log file. > > Kind regards > Christian > > > Am 28.04.21 um 20:39 schrieb Olaf Schreck: >> Christian, >> >>> Sometimes, when a user renames e.g. an existing >>> directory/collection, the renaming works - somehow. The name is >>> changed, but the content of the collection is not accessible >>> anymore. Re-renaming the collection is not possible. Deleting the >>> renamed collection is not possible. >>> >>> Creating a new collection with the old name is also not possible. >>> eXist then reports that this collection already exists (also it was >>> renamed). >> Something is not right.. >> >> - Can you reproduce this at will? Or does it "just happen" sometimes? >> - Can you identify the incident time and check or post logs (maybe >> identified >> by the name of the problematic collection)? >> $EXIST_HOME/logs/exist.log >> and $EXIST_HOME/logs/*.request.log would be interesting. >> >> >> Olaf >> >> >> _______________________________________________ >> 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 -- Nick Sincaglia President/Founder NueMeta, LLC Digital Media & Technology Phone: +1-630-303-7035 nsi...@nu... http://www.nuemeta.com Skype: nsincaglia |
|
From: Christian A. <chr...@ge...> - 2021-04-28 20:54:09
|
Dear Olaf, thanks for your response. No, I cannot reproduce this. The problem occurs just sometimes. The last incidence already happened some time ago but I might be able to find the right log file. Kind regards Christian Am 28.04.21 um 20:39 schrieb Olaf Schreck: > Christian, > >> Sometimes, when a user renames e.g. an existing >> directory/collection, the renaming works - somehow. The name is >> changed, but the content of the collection is not accessible >> anymore. Re-renaming the collection is not possible. Deleting the >> renamed collection is not possible. >> >> Creating a new collection with the old name is also not possible. >> eXist then reports that this collection already exists (also it was >> renamed). > Something is not right.. > > - Can you reproduce this at will? Or does it "just happen" sometimes? > - Can you identify the incident time and check or post logs (maybe identified > by the name of the problematic collection)? $EXIST_HOME/logs/exist.log > and $EXIST_HOME/logs/*.request.log would be interesting. > > > Olaf > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Joe W. <jo...@gm...> - 2021-04-28 20:25:56
|
Hi all, In preparation for the closure of Bintray on May 1, 2021 (this Saturday)[^1], the eXist-db binaries hosted on Bintray since ~2015 have been copied to GitHub. They are now all available at: https://github.com/eXist-db/exist/releases All known links within the eXist-db community's reach have been updated. If you have any eXist-related processes that rely on bintray URLs, please update them to use the new location for these. Joe [^1]: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ |
|
From: Jean-Paul R. <re...@gm...> - 2021-04-28 19:32:09
|
I believe this is the issue https://github.com/eXist-db/exist/pull/3314, although the bug (a related bugs) has been reported so many times I'm not sure which pulls to cite. On Wed, Apr 28, 2021 at 9:26 PM Jean-Paul Rehr <re...@gm...> wrote: > Sorry, it seems my draft email sent off with a hotkey or something. > > As Nick says, this is one of the big bugs in 5.2. The instances I have > still in 5.2 I never rename collections from anywhere - I use remove, copy, > etc in code - just to avoid possible problems. And like Nick, I've moved > over a number of production instances to 5.3 snapshot without issue for > months now. > > JPR > > > > On Wed, Apr 28, 2021 at 8:50 PM Nick Sincaglia <nsi...@nu...> > wrote: > >> Christian, >> This is a known issue that eXist-db 5.3.0 SNAPSHOT fixes. We also >> experienced this same issue and it was recommended that we move to this >> newer version and we have not had any problems since doing so. >> >> Nick >> >> On 4/28/21 12:55 PM, Christian Achter wrote: >> >> Dear all, >> >> this happened to me now several times during the past half year, and on >> different machines. We are using eXist 5.2.0 on several machines (Ubuntu). >> >> Sometimes, when a user renames e.g. an existing directory/collection, the >> renaming works - somehow. The name is changed, but the content of the >> collection is not accessible anymore. Re-renaming the collection is not >> possible. Deleting the renamed collection is not possible. >> >> Creating a new collection with the old name is also not possible. eXist >> then reports that this collection already exists (also it was renamed). >> >> Our users use Oxygen XML Author to handle our XML files and collections. >> >> As an admin, I use the following tools to try to get rid of those >> collections: >> >> - WebDAV (via Oxygen XML Author) >> - eXide in the browser and the file manager you can access from there >> - Java Admin Client (bin/client.sh) >> >> All of those do not work. >> >> So in these cases, I have Schroedinger's collections: I can see them in >> the tools mentioned above but I not access them because they do not exist >> anymore. At the same time, I can not delete or replace them as they somehow >> still exist. >> >> Fun fact: I even had XML files I could not access via any of the tools >> above, but they could be accessed by XQuery scripts that were exactly >> reading these files. >> >> Usually, in these cases, I re-install eXist-db and restore a current >> backup. But I am pretty tired of this workaround. >> >> Is this a problem of indexing? How can it be solved? >> >> Thanks for all advise in advance. >> >> Christian >> >> >> _______________________________________________ >> Exist-open mailing lis...@li...://lists.sourceforge.net/lists/listinfo/exist-open >> >> >> -- >> Nick Sincaglia >> President/Founder >> NueMeta, LLC >> Digital Media & Technology >> Phone: +1-6...@nu... http://www.nuemeta.com >> Skype: nsincaglia >> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > |
|
From: Jean-Paul R. <re...@gm...> - 2021-04-28 19:26:41
|
Sorry, it seems my draft email sent off with a hotkey or something. As Nick says, this is one of the big bugs in 5.2. The instances I have still in 5.2 I never rename collections from anywhere - I use remove, copy, etc in code - just to avoid possible problems. And like Nick, I've moved over a number of production instances to 5.3 snapshot without issue for months now. JPR On Wed, Apr 28, 2021 at 8:50 PM Nick Sincaglia <nsi...@nu...> wrote: > Christian, > This is a known issue that eXist-db 5.3.0 SNAPSHOT fixes. We also > experienced this same issue and it was recommended that we move to this > newer version and we have not had any problems since doing so. > > Nick > > On 4/28/21 12:55 PM, Christian Achter wrote: > > Dear all, > > this happened to me now several times during the past half year, and on > different machines. We are using eXist 5.2.0 on several machines (Ubuntu). > > Sometimes, when a user renames e.g. an existing directory/collection, the > renaming works - somehow. The name is changed, but the content of the > collection is not accessible anymore. Re-renaming the collection is not > possible. Deleting the renamed collection is not possible. > > Creating a new collection with the old name is also not possible. eXist > then reports that this collection already exists (also it was renamed). > > Our users use Oxygen XML Author to handle our XML files and collections. > > As an admin, I use the following tools to try to get rid of those > collections: > > - WebDAV (via Oxygen XML Author) > - eXide in the browser and the file manager you can access from there > - Java Admin Client (bin/client.sh) > > All of those do not work. > > So in these cases, I have Schroedinger's collections: I can see them in > the tools mentioned above but I not access them because they do not exist > anymore. At the same time, I can not delete or replace them as they somehow > still exist. > > Fun fact: I even had XML files I could not access via any of the tools > above, but they could be accessed by XQuery scripts that were exactly > reading these files. > > Usually, in these cases, I re-install eXist-db and restore a current > backup. But I am pretty tired of this workaround. > > Is this a problem of indexing? How can it be solved? > > Thanks for all advise in advance. > > Christian > > > _______________________________________________ > Exist-open mailing lis...@li...://lists.sourceforge.net/lists/listinfo/exist-open > > > -- > Nick Sincaglia > President/Founder > NueMeta, LLC > Digital Media & Technology > Phone: +1-6...@nu... http://www.nuemeta.com > Skype: nsincaglia > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Olaf S. <ol...@ex...> - 2021-04-28 18:55:30
|
Christian, > Sometimes, when a user renames e.g. an existing > directory/collection, the renaming works - somehow. The name is > changed, but the content of the collection is not accessible > anymore. Re-renaming the collection is not possible. Deleting the > renamed collection is not possible. > > Creating a new collection with the old name is also not possible. > eXist then reports that this collection already exists (also it was > renamed). Something is not right.. - Can you reproduce this at will? Or does it "just happen" sometimes? - Can you identify the incident time and check or post logs (maybe identified by the name of the problematic collection)? $EXIST_HOME/logs/exist.log and $EXIST_HOME/logs/*.request.log would be interesting. Olaf |
|
From: Nick S. <nsi...@nu...> - 2021-04-28 18:49:13
|
Christian, This is a known issue that eXist-db 5.3.0 SNAPSHOT fixes. We also experienced this same issue and it was recommended that we move to this newer version and we have not had any problems since doing so. Nick On 4/28/21 12:55 PM, Christian Achter wrote: > > Dear all, > > this happened to me now several times during the past half year, and > on different machines. We are using eXist 5.2.0 on several machines > (Ubuntu). > > Sometimes, when a user renames e.g. an existing directory/collection, > the renaming works - somehow. The name is changed, but the content of > the collection is not accessible anymore. Re-renaming the collection > is not possible. Deleting the renamed collection is not possible. > > Creating a new collection with the old name is also not possible. > eXist then reports that this collection already exists (also it was > renamed). > > Our users use Oxygen XML Author to handle our XML files and collections. > > As an admin, I use the following tools to try to get rid of those > collections: > > * WebDAV (via Oxygen XML Author) > * eXide in the browser and the file manager you can access from there > * Java Admin Client (bin/client.sh) > > All of those do not work. > > So in these cases, I have Schroedinger's collections: I can see them > in the tools mentioned above but I not access them because they do not > exist anymore. At the same time, I can not delete or replace them as > they somehow still exist. > > Fun fact: I even had XML files I could not access via any of the tools > above, but they could be accessed by XQuery scripts that were exactly > reading these files. > > Usually, in these cases, I re-install eXist-db and restore a current > backup. But I am pretty tired of this workaround. > > Is this a problem of indexing? How can it be solved? > > Thanks for all advise in advance. > > Christian > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open -- Nick Sincaglia President/Founder NueMeta, LLC Digital Media & Technology Phone: +1-630-303-7035 nsi...@nu... http://www.nuemeta.com Skype: nsincaglia |
|
From: Jean-Paul R. <re...@gm...> - 2021-04-28 18:44:34
|
This is On Wed, Apr 28, 2021 at 8:15 PM Christian Achter < chr...@ge...> wrote: > Dear all, > > this happened to me now several times during the past half year, and on > different machines. We are using eXist 5.2.0 on several machines (Ubuntu). > > Sometimes, when a user renames e.g. an existing directory/collection, the > renaming works - somehow. The name is changed, but the content of the > collection is not accessible anymore. Re-renaming the collection is not > possible. Deleting the renamed collection is not possible. > > Creating a new collection with the old name is also not possible. eXist > then reports that this collection already exists (also it was renamed). > > Our users use Oxygen XML Author to handle our XML files and collections. > > As an admin, I use the following tools to try to get rid of those > collections: > > - WebDAV (via Oxygen XML Author) > - eXide in the browser and the file manager you can access from there > - Java Admin Client (bin/client.sh) > > All of those do not work. > > So in these cases, I have Schroedinger's collections: I can see them in > the tools mentioned above but I not access them because they do not exist > anymore. At the same time, I can not delete or replace them as they somehow > still exist. > > Fun fact: I even had XML files I could not access via any of the tools > above, but they could be accessed by XQuery scripts that were exactly > reading these files. > > Usually, in these cases, I re-install eXist-db and restore a current > backup. But I am pretty tired of this workaround. > > Is this a problem of indexing? How can it be solved? > > Thanks for all advise in advance. > > Christian > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Roy W. <gar...@ya...> - 2021-04-28 18:32:53
|
May or may not be relevant but I have found that Oxygen only reflects collection/file changes on refresh. It doesn’t automatically track state.
Sent from Yahoo Mail for iPhone
On Wednesday, April 28, 2021, 7:15 pm, Christian Achter <chr...@ge...> wrote:
Dear all,
this happened to me now several times during the past half year, and on different machines. We are using eXist 5.2.0 on several machines (Ubuntu).
Sometimes, when a user renames e.g. an existing directory/collection, the renaming works - somehow. The name is changed, but the content of the collection is not accessible anymore. Re-renaming the collection is not possible. Deleting the renamed collection is not possible.
Creating a new collection with the old name is also not possible. eXist then reports that this collection already exists (also it was renamed).
Our users use Oxygen XML Author to handle our XML files and collections.
As an admin, I use the following tools to try to get rid of those collections:
- WebDAV (via Oxygen XML Author)
- eXide in the browser and the file manager you can access from there
- Java Admin Client (bin/client.sh)
All of those do not work.
So in these cases, I have Schroedinger's collections: I can see them in the tools mentioned above but I not access them because they do not exist anymore. At the same time, I can not delete or replace them as they somehow still exist.
Fun fact: I even had XML files I could not access via any of the tools above, but they could be accessed by XQuery scripts that were exactly reading these files.
Usually, in these cases, I re-install eXist-db and restore a current backup. But I am pretty tired of this workaround.
Is this a problem of indexing? How can it be solved?
Thanks for all advise in advance.
Christian
_______________________________________________
Exist-open mailing list
Exi...@li...
https://lists.sourceforge.net/lists/listinfo/exist-open
|
|
From: Christian A. <chr...@ge...> - 2021-04-28 18:14:21
|
Dear all, this happened to me now several times during the past half year, and on different machines. We are using eXist 5.2.0 on several machines (Ubuntu). Sometimes, when a user renames e.g. an existing directory/collection, the renaming works - somehow. The name is changed, but the content of the collection is not accessible anymore. Re-renaming the collection is not possible. Deleting the renamed collection is not possible. Creating a new collection with the old name is also not possible. eXist then reports that this collection already exists (also it was renamed). Our users use Oxygen XML Author to handle our XML files and collections. As an admin, I use the following tools to try to get rid of those collections: * WebDAV (via Oxygen XML Author) * eXide in the browser and the file manager you can access from there * Java Admin Client (bin/client.sh) All of those do not work. So in these cases, I have Schroedinger's collections: I can see them in the tools mentioned above but I not access them because they do not exist anymore. At the same time, I can not delete or replace them as they somehow still exist. Fun fact: I even had XML files I could not access via any of the tools above, but they could be accessed by XQuery scripts that were exactly reading these files. Usually, in these cases, I re-install eXist-db and restore a current backup. But I am pretty tired of this workaround. Is this a problem of indexing? How can it be solved? Thanks for all advise in advance. Christian |
|
From: Torsten S. <sch...@ha...> - 2021-04-25 20:07:20
|
Dear community, we run a (rather old but that might not be of any interest) exist installation for some of our digital editions and other databases. Now we encounter the problem that some of these pages are protected by a password if you try to access the them. Others can be accessed without password. I don't remember to have applied any protection and I don't know how to remove it in order to allow for free access to these pages (or limit the protection to the ones which really need it). Does anyone of you have an idea how to solve this problem? Mit besten Grüßen, Torsten -- Torsten Schassan - Abteilung Handschriften und Sondersammlungen / Digitale Editionen Herzog August Bibliothek, D-38299 Wolfenbuettel, Tel.: +49 5331 808-130 Fax -165 Handschriftendatenbank: http://diglib.hab.de/?db=mss |
|
From: Dannes W. <da...@ex...> - 2021-04-20 15:19:46
|
Hi, I had a similar issue, fortunately I was able to trace down the cause: [BUG] TemporaryFileManager should not rely on created directories in /tmp [linux] · Issue #3826 · eXist-db/exist (github.com) <https://github.com/eXist-db/exist/issues/3826> regards Dannes On Mon, Feb 1, 2021 at 10:24 AM Ihe Onwuka <ihe...@gm...> wrote: > I had to unexpectedly switch laptops last week and have lost my exide > "bookmark". > > I am running exist 5.2 on Amazon EC2. Now > > ...:8080/exist/apps/dashboard/index.html gives me a blank Launcher screen. > > and :8080/exist/apps/eXide/index.html gives me > <exception> > <path>/db/apps/eXide/modules/view.xql</path> > <message>exerr:ERROR An IO exception occurred: Could not load cache for > class: org.exist.util.io.FileFilterInputStreamCache [at line 44, column 14] > </message> > </exception> > > Can anybody help. > > > > > > > > > > > > > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
|
From: Dannes W. <da...@ex...> - 2021-04-18 18:43:40
|
Hi, It is a good and valid question :-) At this moment we are looking for an alternative, which is a bit more difficult than expected. We will announce a change, the correct links will added to the project page. cheers Dannes -- eXist-db Native XML Database http://www.exist-db.org > On 12 Apr 2021, at 13:01 , Kuukka-Härmä Riina <Rii...@fi...> wrote: > > Hi, > > Maybe a bit stupid question, but where in future newer eXist-db releases can be downloaded? > > I checked current published version distribution (https://bintray.com/existdb/releases/exist/5.2.0 <https://bintray.com/existdb/releases/exist/5.2.0>), and there is information that Bintray will be deprecated 1st of May 2021, and if I have understood https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ <https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/> correctly, after 1st of May the eXist-db distribution package is no longer available. > > Best Regards, Riina Kuukka-Härmä > > _______________________________________________ > 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> |
|
From: Kuukka-Härmä R. <Rii...@fi...> - 2021-04-12 11:01:52
|
Hi, Maybe a bit stupid question, but where in future newer eXist-db releases can be downloaded? I checked current published version distribution (https://bintray.com/existdb/releases/exist/5.2.0), and there is information that Bintray will be deprecated 1st of May 2021, and if I have understood https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ correctly, after 1st of May the eXist-db distribution package is no longer available. Best Regards, Riina Kuukka-Härmä |
|
From: Christian W. <cwi...@gm...> - 2021-04-05 02:39:11
|
Dear Joe, eXist users, One more data point on this situation. Since I could not get the crypto module to work on the latest 5.3.0 snapshot, this morning I reverted to the 5.2.0 release by restoring the most recent backup taken from the application running on 5.3.0 to an empty instance of 5.2.0. Since the backup contained the 5.3.0 version of the crypto module (installed through the package manager) and I selected to overwrite newer applications and rebuild the expath repository, I ended up running this version on the 5.2.0 instance. With this setup, I can confirm that the workflow outlined below (that is: pushing to GitHub and using webhooks to update the production server) does work again. All the best, Christian On 29/03/2021 09.14, Christian Wittern wrote: > > Dear Joe, > > Yes the workflow is cool and lets me concentrate on the task. > > Here is more background: I moved to the latest snapshot by restoring a > backup made from the version of my application that was running on > 5.2.0. This include all required stuff and previously was enough to > get it running, when I did this for example on a new version of > 5.2.0. After doing the restore this time, my code was throwing > errors, which led me to update the whole toolchain of shared > resources, eXide etc. to the latest version. At that point, I was > also offered to upgrade the crypto package to 5.3.0 from the package > manager. Initially I declined to do so, because I remembered vaguely > that there was some care required. But in the end I tried this, and > also the stand alone package you pointed me to. The module fails to > load in all cases (i.e. from eXide, oXygen and when run) with this > error message: > > exerr:ERROR error found while loading module ghx: Error while loading > module : error found while loading module crypto: Unable to > instantiate module from EXPathrepository: > org.expath.exist.crypto.ExistExpathCryptoModule > > (ghx is my alias for the github-xq module). > > The expathrepo folder does contain the 6.0.0RC1 version of the crypto > module, so it seems the initial installation was successful. > > Does this tell you anything? I am pretty much out of my depth here. > > All the best, > > Christian > > On 28/03/2021 23.36, Joe Wicentowski wrote: >> Hi Christian, >> >> What a cool publishing workflow. >> >> When you say “this doesn’t solve the problem”, do you mean that you >> tested the pre-built package and it didn’t work? Can you provide more >> details about what went wrong? >> >> Thanks, >> Joe >> >> On Sun, Mar 28, 2021 at 1:13 AM Christian Wittern <cwi...@gm... >> <mailto:cwi...@gm...>> wrote: >> >> Dear Joe, >> >> Thanks for the heads up. Unfortunately this does not solve the >> problem for me. >> >> I am depending on the crypto module for github webhooks via >> Winona Salesky's excellent github-xq module. I usually develop on >> a local server, then push the changes to the github repository >> and have the webhook deliver it to the production server. So far >> this was excellent to quickly deliver bugfixes etc, but I can't >> use it that way at the moment :-( >> >> Christian >> >> P.S. Yes, I know I should not use the 5.3.0 SNAPSHOT in >> production, it started as a test that (otherwise) turned out so >> well that I decided to go with it. Until I discovered the crypto >> problem.... CW >> >> On 28/03/2021 11.13, Joe Wicentowski wrote: >>> Hi Christian, >>> >>> Juri gave us a promising update on Olaf's work on the crypto >>> module in last week's Community Call, including a link to a >>> pre-built xar that can be used for testing with eXist 5.x. The >>> link to the notes from each call can be found linked from >>> https://github.com/eXist-db/exist#open-community-calls >>> <https://github.com/eXist-db/exist#open-community-calls>. >>> >>> I'm curious, which crypto functions are critical for your work? >>> >>> Joe >>> >>> On Sat, Mar 27, 2021 at 9:40 PM Christian Wittern >>> <cwi...@gm... <mailto:cwi...@gm...>> wrote: >>> >>> Dear Joe, >>> >>> While trying out the most recent snapshot (in order to take >>> advantage of the fixed bug re astral CJK characters), I >>> realized that there is a problem with the crypto module and >>> then remembered this post from a few months ago. My question >>> now is: >>> >>> Is there a way I can work around these problems and use the >>> crypto module right now? >>> >>> Is anybody working on this? I certainly would appreciate >>> this being resolved... >>> >>> All the best, >>> >>> Christian >>> >>> On 01/12/2020 04.49, Joe Wicentowski wrote: >>>> Hi all, >>>> >>>> Following up on today's Community Call, users of the eXist >>>> Crypto Module should be warned about problems in the >>>> current release of the package, 5.3.0: >>>> >>>> https://github.com/eXist-db/crypto-exist-java-lib/issues/33 >>>> <https://github.com/eXist-db/crypto-exist-java-lib/issues/33> >>>> >>>> The problems and next steps are described in the issue. >>>> >>>> Joe >>>> >>>> >>>> _______________________________________________ >>>> 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... >>> <mailto:Exi...@li...> >>> https://lists.sourceforge.net/lists/listinfo/exist-open >>> <https://lists.sourceforge.net/lists/listinfo/exist-open> >>> >> -- >> Sent from my iPhone |
|
From: Ari N. <ari...@gm...> - 2021-04-01 06:18:05
|
Hi Gary, You don't actually save anything before the pipeline is finished, unless $debug is set. The manifest listing the XSLTs is first read into a sequence. That sequence is then used in a recursive function for the actual transforms, one XSLT at a time, for as long as there is an XSLT left in the sequence. The output from one recursion is used as the input to the next. Plus, since I may have to feed steps with parameters, there's stuff in there to handle parameters set in the manifest. You can test it using the XSLT-pipelines example repo at https://github.com/sgmlguru/xslt-pipelines. The example works both in XProc on the file system and in eXist using XQuery. Oh, and I spoke about the pipelined XSLT approach at Balisage last year: https://www.balisage.net/Proceedings/vol25/html/Nordstrom01/BalisageVol25-Nordstrom01.html. Best, /Ari On 2021-04-01 01:27, Gary Kopp wrote: > > Thanks for the suggestion, Ari. Let’s see if I understand your > approach, now that I’ve looked at your code. It seems the interface > between pipeline steps is a temporary document stored in the database > in one step, and read in the next step using an explicit URI. Am I > seeing that right? > > --Gary > > *From:* Ari Nordström <ari...@gm...> > *Sent:* Wednesday, March 31, 2021 4:31 PM > *To:* Gary Kopp <ge...@ru...> > *Cc:* exist-open <exi...@li...> > *Subject:* Re: [Exist-open] XProc (Calabash) Status? > > Hi, > > I think Norm is busy with work and real life, but I know the Calabash > XProc 3.0 version is in the works. You should look into Morgana XProc > for XProc 3.0 support in the meantime. > > As for running a sequence of XQueries with one providing the input to > the next, I assume you'd want to do it in an eXist context? If so, > XProc remains a rather painful option as it's not well supported. > > I'd go with an XQ wrapper instead. I did something very similar to run > XSLT stylesheets in sequence in eXist. I had done it in XProc and > Calabash on the file system but getting XProc to work in eXist proved > to be too much of a pain so I reimplemented the pipeline in XQ instead. > > My XProc and XQuery are both on GitHub: > https://github.com/sgmlguru/xproc-batch > <https://github.com/sgmlguru/xproc-batch> > > It should be fairly uncomplicated to modify the XQuery to run XQueries > instead. > > Best, > > /Ari > > On Wed, 31 Mar 2021, 21:38 Gary Kopp, <ge...@ru... > <mailto:ge...@ru...>> wrote: > > The last update to xquery-xproc-xmlcalabash-module was about a > year ago. The README itemizes some current limitations. I would > like to know if the following limitations are still applicable, > and if so can you suggest any workarounds: > > “Function signature will change soon to accept XML for /pipeline/, > /output/, as well as specify input/output/parameter ports and > options... for now it's primitive” > > |“p:xquery| has no context with eXist, this is a big limitation, > but there are several ways around this” > > I’m new to XProc, and have a lot of studying and experimentation > to do. All I really want to accomplish is to link multiple XQuery > scripts together so that the XML generated in one script is used > as input in a FLWOR in the next script, without explicitly > creating temporary documents in the database. I’m _/assuming/_ > that is possible with XProc, but please correct me if I’m wrong > and I’ll abandon this line of attack. Thanks! > > --Gary Kopp > > _______________________________________________ > 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> > |
|
From: Gary K. <ge...@ru...> - 2021-03-31 23:28:29
|
Thanks for the suggestion, Ari. Let’s see if I understand your approach, now that I’ve looked at your code. It seems the interface between pipeline steps is a temporary document stored in the database in one step, and read in the next step using an explicit URI. Am I seeing that right? --Gary From: Ari Nordström <ari...@gm...> Sent: Wednesday, March 31, 2021 4:31 PM To: Gary Kopp <ge...@ru...> Cc: exist-open <exi...@li...> Subject: Re: [Exist-open] XProc (Calabash) Status? Hi, I think Norm is busy with work and real life, but I know the Calabash XProc 3.0 version is in the works. You should look into Morgana XProc for XProc 3.0 support in the meantime. As for running a sequence of XQueries with one providing the input to the next, I assume you'd want to do it in an eXist context? If so, XProc remains a rather painful option as it's not well supported. I'd go with an XQ wrapper instead. I did something very similar to run XSLT stylesheets in sequence in eXist. I had done it in XProc and Calabash on the file system but getting XProc to work in eXist proved to be too much of a pain so I reimplemented the pipeline in XQ instead. My XProc and XQuery are both on GitHub: https://github.com/sgmlguru/xproc-batch It should be fairly uncomplicated to modify the XQuery to run XQueries instead. Best, /Ari On Wed, 31 Mar 2021, 21:38 Gary Kopp, <ge...@ru... <mailto:ge...@ru...> > wrote: The last update to xquery-xproc-xmlcalabash-module was about a year ago. The README itemizes some current limitations. I would like to know if the following limitations are still applicable, and if so can you suggest any workarounds: “Function signature will change soon to accept XML for pipeline, output, as well as specify input/output/parameter ports and options... for now it's primitive” “p:xquery has no context with eXist, this is a big limitation, but there are several ways around this” I’m new to XProc, and have a lot of studying and experimentation to do. All I really want to accomplish is to link multiple XQuery scripts together so that the XML generated in one script is used as input in a FLWOR in the next script, without explicitly creating temporary documents in the database. I’m _assuming_ that is possible with XProc, but please correct me if I’m wrong and I’ll abandon this line of attack. Thanks! --Gary Kopp _______________________________________________ Exist-open mailing list Exi...@li... <mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Ari N. <ari...@gm...> - 2021-03-31 22:30:55
|
Hi, I think Norm is busy with work and real life, but I know the Calabash XProc 3.0 version is in the works. You should look into Morgana XProc for XProc 3.0 support in the meantime. As for running a sequence of XQueries with one providing the input to the next, I assume you'd want to do it in an eXist context? If so, XProc remains a rather painful option as it's not well supported. I'd go with an XQ wrapper instead. I did something very similar to run XSLT stylesheets in sequence in eXist. I had done it in XProc and Calabash on the file system but getting XProc to work in eXist proved to be too much of a pain so I reimplemented the pipeline in XQ instead. My XProc and XQuery are both on GitHub: https://github.com/sgmlguru/xproc-batch It should be fairly uncomplicated to modify the XQuery to run XQueries instead. Best, /Ari On Wed, 31 Mar 2021, 21:38 Gary Kopp, <ge...@ru...> wrote: > The last update to xquery-xproc-xmlcalabash-module was about a year ago. > The README itemizes some current limitations. I would like to know if the > following limitations are still applicable, and if so can you suggest any > workarounds: > > > > “Function signature will change soon to accept XML for *pipeline*, > *output*, as well as specify input/output/parameter ports and options... > for now it's primitive” > > > > “p:xquery has no context with eXist, this is a big limitation, but there > are several ways around this” > > > > I’m new to XProc, and have a lot of studying and experimentation to do. > All I really want to accomplish is to link multiple XQuery scripts together > so that the XML generated in one script is used as input in a FLWOR in the > next script, without explicitly creating temporary documents in the > database. I’m _*assuming*_ that is possible with XProc, but please > correct me if I’m wrong and I’ll abandon this line of attack. Thanks! > > > > --Gary Kopp > > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Gary K. <ge...@ru...> - 2021-03-31 19:37:40
|
The last update to xquery-xproc-xmlcalabash-module was about a year ago. The README itemizes some current limitations. I would like to know if the following limitations are still applicable, and if so can you suggest any workarounds: "Function signature will change soon to accept XML for pipeline, output, as well as specify input/output/parameter ports and options... for now it's primitive" "p:xquery has no context with eXist, this is a big limitation, but there are several ways around this" I'm new to XProc, and have a lot of studying and experimentation to do. All I really want to accomplish is to link multiple XQuery scripts together so that the XML generated in one script is used as input in a FLWOR in the next script, without explicitly creating temporary documents in the database. I'm _assuming_ that is possible with XProc, but please correct me if I'm wrong and I'll abandon this line of attack. Thanks! --Gary Kopp |
|
From: Finian O'B. <fin...@gm...> - 2021-03-30 12:05:37
|
Joern, I agree with your observations - I've always thought XML/XQuery/XSLT/eXist/RestXQ/XForms provided a really elegant development solution. That over the course of almost a decade I converted from simple eXist/HTML to eXist/Orbeon, then to eXist/betterForm and finally back to a "homebrew" eXist/Orbeon setup is, I think, a token of my commitment! And I appreciate what you say about the heaviness of both betterForm and Orbeon, which is why I suggested looking at alternatives. Thank you for the links to your work on Fore - I will look at it more carefully. I thought you had stopped work on it, because I had been following links from the old betterForm pages. More power to your elbow. Finian On Tue, 2021-03-30 at 12:35 +0200, Joern Turner wrote: > Finian, > > On Sun, Mar 28, 2021 at 10:01 AM Finian O'Boyle < > fin...@gm...> wrote: > > Hi Gary, > > > > All of my applications within eXist use XForms. I developed them > > using betterForm, but when support for it was removed from eXist, I > > converted them all to Orbeon using the Community Edition. I chose > > it because it implements W3C XForms standard and because it > > supports a wide range of form elements, but most importantly it is > > under current maintenance. I run eXist 5.2.0 and Orbeon 19.2 CE, > > but do so in a way in which they both run independently within the > > same servlet container - in my case I use eXist's Jetty, but it is > > also possible to use Tomcat. > > > > Orbeon and eXist work together to render XForms by using cross- > > context communication within the servlet container: the Orbeon > > developers call this separate deployment. Requests to eXist for an > > XForms page are intercepted by a servlet filter within eXist's > > context and are passed to Orbeon. The XForms/XHTML markup is > > transformed into an XHTML web page with links to supporting > > JavaScript and CSS. This page is returned to the browser from > > eXist, and the JavaScript/CSS requests are serviced by the servlet > > filter. > > > > Configuring this scenario requires a small number of changes within > > both eXist and Orbeon. To summarise them for eXist you need to: > > > > 1. Amend web.xml to add a servlet filter and mappings to intercept > > XForms pages > > 2. Copy orbeon-xforms-filter.jar to eXist's /lib directory > > 3. Disable betterFORM globally if it is included in your version of > > eXist > > > > For Orbeon you need to: > > > > 1. Download the latest version of Orbeon CE and place orbeon.war in > > the servlet container > > 2. Disable the Orbeon Form Runner login service defined within > > web.xml > > 3. Create properties-local.xml to configure Orbeon to accept > > requests from eXist > > > > When I set it up I created a page that fits into the standard eXist > > documentation explaining in detail how to effect these changes. I > > can let you have that if you're interested. > > > > > A lot of setup right? And it was similar with betterFORM which had > quite the same architecture as Orbeon. Also here the problems start > as the provided (generated) JS, CSS code for understandable reasons > has to commit to a certain client-side framework and provide a > complete set of controls. The conceptual mapping from abstract UI > control in XForms to real-world controls caused another complexity. > Which is all fine and good as long as you don't need that special > control that's not provided or not in the form you'd like. All in all > the architectures of Orbeon and betterFORM are quite heavy though > very powerful. But they come to a significant cost in terms of > knowledge and maintenance. > > > Having said all of that, if I were starting from scratch I would > > consider the alternatives to XForms. Although I have found > > eXist/XForms very flexible and easy to use, it seems to me to be > > something of an edge-case these days. I'm sure people here would > > have ideas as to more modern technologies. > XForms and eXist-db of course fit extremely well as you're dealing > with XML through the whole stack without any mapping whatsoever. That > in itself is IMO a big selling point. > As for the 'more modern' technologies - the XForms architecture is > still outstanding in the area of form processing IMHO but it could be > dedusted ;) Fore is an attempt to do that purely client-side (but > with server-side validation support) in native browser technologies > plus XPath/XQuery 3 > Yep - it's beta > Joern > > Finian > > > > On Sat, 2021-03-27 at 18:52 -0600, Gary Kopp wrote: > > > While I’m an experienced Java programmer, I am new to eXist, > > > XQuery, and XForms. I wish to create an eXist XForms web > > > application and right now I need a little guidance on where to > > > start. I’ve installed the eXist demo apps, which includes an > > > XForms restxq application. Of course it doesn’t work out of the > > > box because no XForms processors are installed, neither > > > betterform nor XSLTForms. Which should I install – or rather, > > > which currently works? Betterform is no longer included with the > > > eXist distribution. It is available for download from Sourceforge > > > as betterform-install-5.0rc5.jar but I can’t find any actual > > > instructions for installation/configuration. Should I bother with > > > it? As far as XSLTForms goes, I wanted to see a sample of a > > > client-side page, and the documentation provides a link to > > > hello.xml for this, but that page doesn’t seem to exist anywhere. > > > Any help here? > > > > > > While I’m at, I guess I could consider Orbeon Forms (community > > > edition). It deprecated eXist support, but I’m guessing it’s > > > still in the code. Any success/failure stories to share? > > > > > > Thanks in advance from a newbie. > > > > > > --Gary Kopp > > > > > > _______________________________________________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 > > |
602 messages has been excluded from this view by a project administrator.
