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
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Ted H. <meg...@gm...> - 2024-06-18 00:41:04
|
Perhaps I didn't make myself clear in my last post. It appears the Jaxp function that I added to my xq code worked well enough to detect an error. The problem is I don't know what error I created. Here is my xquery: xquery version "3.0"; import module namespace validation="http://exist-db.org/xquery/validation"; let $schema := xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML_Schema.xsd') let $instance := xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML.xml') return (validation:clear-grammar-cache()) (validation:jaxp-report($instance, $schema)) Here is my instance: <html xmlns="http://www.TedTheSpeedlearner.com" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.TedTheSpeedlearner.com SVG_Ellipse_Webpage_XML_Schema.xsd"> <head> <title>SVG Ellipse</title> <link rel="stylesheet" type="text/css" href=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.css"/> <script language="javascript" src=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.js"/> </head> <body onload="Setup()"> <svg id="Image_Box"> <ellipse id="My_Ellipse"/> </svg> </body> </html> And here is my schema: <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:target=" http://www.TedTheSpeedlearner.com" targetNamespace=" http://www.TedTheSpeedlearner.com" elementFormDefault="qualified"> <complexType name="HeadType"> <sequence> <element name="head" type="target:TitleType"/> <element name="body" type="target:BodyType"/> </sequence> </complexType> <complexType name="TitleType"> <sequence> <element name="title" type="string"/> <element name="link" type="target:LinkType"/> <element name="script" type="target:ScriptType"/> </sequence> </complexType> <complexType name="LinkType"> <attribute name="rel" type="string"/> <attribute name="type" type="string"/> <attribute name="href" type="string"/> </complexType> <complexType name="ScriptType"> <attribute name="language" type="string"/> <attribute name="src" type="string"/> </complexType> <complexType name="BodyType"> <sequence> <element name="svg" type="target:SvgType"/> </sequence> <attribute name="onload" type="string"/> </complexType> <complexType name="SvgType"> <sequence> <element name="ellipse" type="target:EllipseType"/> </sequence> <attribute name="id" type="string"/> </complexType> <complexType name="EllipseType"> <attribute name="id" type="string"/> </complexType> <element name="html" type="target:HeadType"/> </schema> And what was the error? eXist stated that it expected a function, but it got an xs:integer in line 6 column 2. I can't determine what I did wrong. Can you assist me? On Tue, Jun 11, 2024 at 11:19 AM Florian Schmitt < ml-...@fl...> wrote: > Hi Ted, > > i'm not sure if it works with validation:jaxp-report, too, but i got a > simple example running with validation:jaxv-report. Schema and XML > instance are copied from the W3 Schools example: > > https://www.w3schools.com/xml/schema_intro.asp > > ------------------------------ > schema.xsd: > ------------------------------ > <?xml version="1.0"?> > <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> > > <xs:element name="note"> > <xs:complexType> > <xs:sequence> > <xs:element name="to" type="xs:string"/> > <xs:element name="from" type="xs:string"/> > <xs:element name="heading" type="xs:string"/> > <xs:element name="body" type="xs:string"/> > </xs:sequence> > </xs:complexType> > </xs:element> > > </xs:schema> > > ------------------------------ > note.xml: > ------------------------------ > <note> > <to>Tove</to> > <from>Jani</from> > <heading>Reminder</heading> > <body>Don't forget me this weekend!</body> > </note> > > ------------------------------ > schema-test.xq: > ------------------------------ > xquery version "3.0"; > import module namespace > validation="http://exist-db.org/xquery/validation"; > let $schema := xs:anyURI('/db/xmldata/schema.xsd') > let $instance := xs:anyURI('/db/xmldata/note.xml') > return > (validation:clear-grammar-cache(), validation:jaxv-report($instance, > $schema)) > > ------------------------------ > Output (with eXist-db 5.2.0 - sorry, currently no 6.xx available: > ------------------------------ > 0 > <report> > <status>valid</status> > <duration unit="msec">13</duration> > </report> > > HTH > Florian > > > Am 09.06.24 um 21:41 schrieb Ted Hickox: > > I have a small update. I made a couple of changes to my code: > > > > xquery version "3.0"; > > import module namespace > > validation="http://exist-db.org/xquery/validation > > <http://exist-db.org/xquery/validation>"; > > let $schema := > > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML_Schema.xsd') > > let $instance := > > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML.xml') > > return > > (validation:clear-grammar-cache()) > > (validation:jaxp-report($instance, $schema)) > > > > This fixed a bunch of problems. But when I ran the code, I got this > > information: > > > > image.png > > > > I still don't know what error I made. > > eption> > > > <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> > > <message>err:XPTY0004 Type error: expected function, got xs:integer > > [at line 6, column 2, source: > > /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> > > </exception> > > > > exception>exception> > > > <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> > > <message>err:XPTY0004 Type error: expected function, got xs:integer > > [at line 6, column 2, source: > > /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> > > </exception> > > > <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> > > <message>err:XPTY0004 Type error: expected function, got xs:integer > > [at line 6, column 2, source: > > /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> > > </exception> > > > > On Sun, Jun 9, 2024 at 1:58 PM Ted Hickox <meg...@gm... > > <mailto:meg...@gm...>> wrote: > > > > A few months ago I was informed that the function > > validation:validate-report had been depreciated and is no longer > > available in the eXist database. So someone suggested I use the > > validate:jaxp-report function. Shortly after I received this > > suggestion, I tried to use it. But it failed. Unfortunately my > > life became very busy and I had to abandon my project. Now that > > my life is a little calmer, I tried to play with this computer > > code again. And still something is not functioning correctly. > > I'm still not sure what I'm doing wrong. > > > > xquery version "3.0"; > > import module namespace > > validation="http://exist-db.org/xquery/validation > > <http://exist-db.org/xquery/validation>"; > > let $schema := > > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML_Schema.xsd') > > let $instance := > > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML.xml') > > return > > (validation:clear-grammar-cache(); > > validation:jaxp-report($instance as item(), $enable-grammar-cache > > as xs:boolean, $catalogs as item()*) as node()) > > > > > > > > _______________________________________________ > > 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: Joern T. <joe...@gm...> - 2024-06-17 10:52:19
|
Hi *, for those interested in using eXist-db with Fore to seamlessly process XML in the browser and connect your frontend via OpenAPI endpoints, this new app could be interesting. It hopefully simplifies the task to get started with Fore in eXist-db by packaging it and lets you create a barebones page quickly. It also features a very simplistic todo example to show interaction with endpoints. For those being around for a longer time XRX might still be a familiar term. eXist-db and Fore combined deliver this pattern in a modernized way by extending HTML with Web Components. on github - https://github.com/Jinntec/fore-exist. Feedback very welcome, Joern |
From: Florian S. <ml-...@fl...> - 2024-06-11 16:18:51
|
Hi Ted, i'm not sure if it works with validation:jaxp-report, too, but i got a simple example running with validation:jaxv-report. Schema and XML instance are copied from the W3 Schools example: https://www.w3schools.com/xml/schema_intro.asp ------------------------------ schema.xsd: ------------------------------ <?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="note"> <xs:complexType> <xs:sequence> <xs:element name="to" type="xs:string"/> <xs:element name="from" type="xs:string"/> <xs:element name="heading" type="xs:string"/> <xs:element name="body" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> ------------------------------ note.xml: ------------------------------ <note> <to>Tove</to> <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body> </note> ------------------------------ schema-test.xq: ------------------------------ xquery version "3.0"; import module namespace validation="http://exist-db.org/xquery/validation"; let $schema := xs:anyURI('/db/xmldata/schema.xsd') let $instance := xs:anyURI('/db/xmldata/note.xml') return (validation:clear-grammar-cache(), validation:jaxv-report($instance, $schema)) ------------------------------ Output (with eXist-db 5.2.0 - sorry, currently no 6.xx available: ------------------------------ 0 <report> <status>valid</status> <duration unit="msec">13</duration> </report> HTH Florian Am 09.06.24 um 21:41 schrieb Ted Hickox: > I have a small update. I made a couple of changes to my code: > > xquery version "3.0"; > import module namespace > validation="http://exist-db.org/xquery/validation > <http://exist-db.org/xquery/validation>"; > let $schema := > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML_Schema.xsd') > let $instance := > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML.xml') > return > (validation:clear-grammar-cache()) > (validation:jaxp-report($instance, $schema)) > > This fixed a bunch of problems. But when I ran the code, I got this > information: > > image.png > > I still don't know what error I made. > eption> > <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> > <message>err:XPTY0004 Type error: expected function, got xs:integer > [at line 6, column 2, source: > /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> > </exception> > > exception>exception> > <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> > <message>err:XPTY0004 Type error: expected function, got xs:integer > [at line 6, column 2, source: > /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> > </exception> > <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> > <message>err:XPTY0004 Type error: expected function, got xs:integer > [at line 6, column 2, source: > /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> > </exception> > > On Sun, Jun 9, 2024 at 1:58 PM Ted Hickox <meg...@gm... > <mailto:meg...@gm...>> wrote: > > A few months ago I was informed that the function > validation:validate-report had been depreciated and is no longer > available in the eXist database. So someone suggested I use the > validate:jaxp-report function. Shortly after I received this > suggestion, I tried to use it. But it failed. Unfortunately my > life became very busy and I had to abandon my project. Now that > my life is a little calmer, I tried to play with this computer > code again. And still something is not functioning correctly. > I'm still not sure what I'm doing wrong. > > xquery version "3.0"; > import module namespace > validation="http://exist-db.org/xquery/validation > <http://exist-db.org/xquery/validation>"; > let $schema := > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML_Schema.xsd') > let $instance := > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML.xml') > return > (validation:clear-grammar-cache(); > validation:jaxp-report($instance as item(), $enable-grammar-cache > as xs:boolean, $catalogs as item()*) as node()) > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
From: Ted H. <meg...@gm...> - 2024-06-09 19:42:04
|
I have a small update. I made a couple of changes to my code: xquery version "3.0"; import module namespace validation="http://exist-db.org/xquery/validation"; let $schema := xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML_Schema.xsd') let $instance := xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML.xml') return (validation:clear-grammar-cache()) (validation:jaxp-report($instance, $schema)) This fixed a bunch of problems. But when I ran the code, I got this information: [image: image.png] I still don't know what error I made. eption> <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> <message>err:XPTY0004 Type error: expected function, got xs:integer [at line 6, column 2, source: /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> </exception> exception>exception> <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> <message>err:XPTY0004 Type error: expected function, got xs:integer [at line 6, column 2, source: /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> </exception> <path>/db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq</path> <message>err:XPTY0004 Type error: expected function, got xs:integer [at line 6, column 2, source: /db/apps/HTML_Student/SVG_Ellipse_Webpage_XQuery_Validator.xq]</message> </exception> On Sun, Jun 9, 2024 at 1:58 PM Ted Hickox <meg...@gm...> wrote: > A few months ago I was informed that the function > validation:validate-report had been depreciated and is no longer available > in the eXist database. So someone suggested I use the validate:jaxp-report > function. Shortly after I received this suggestion, I tried to use it. > But it failed. Unfortunately my life became very busy and I had to abandon > my project. Now that my life is a little calmer, I tried to play with this > computer code again. And still something is not functioning correctly. > I'm still not sure what I'm doing wrong. > > xquery version "3.0"; > import module namespace validation="http://exist-db.org/xquery/validation > "; > let $schema := > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML_Schema.xsd') > let $instance := > xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML.xml') > return > (validation:clear-grammar-cache(); validation:jaxp-report($instance as > item(), $enable-grammar-cache as xs:boolean, $catalogs as item()*) as > node()) > |
From: Ted H. <meg...@gm...> - 2024-06-09 18:58:43
|
A few months ago I was informed that the function validation:validate-report had been depreciated and is no longer available in the eXist database. So someone suggested I use the validate:jaxp-report function. Shortly after I received this suggestion, I tried to use it. But it failed. Unfortunately my life became very busy and I had to abandon my project. Now that my life is a little calmer, I tried to play with this computer code again. And still something is not functioning correctly. I'm still not sure what I'm doing wrong. xquery version "3.0"; import module namespace validation="http://exist-db.org/xquery/validation"; let $schema := xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML_Schema.xsd') let $instance := xs:anyURI('/db/apps/HTML_Student/SVG_Ellipse_Webpage_XML.xml') return (validation:clear-grammar-cache(); validation:jaxp-report($instance as item(), $enable-grammar-cache as xs:boolean, $catalogs as item()*) as node()) |
From: Harris, B. T. (GSFC-5870) <ber...@na...> - 2024-06-06 13:18:17
|
I am occasionally getting the following exception: java.util.ConcurrentModificationException at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1221) at org.exist.xmldb.DatabaseImpl.getRpcClient(DatabaseImpl.java:318) at org.exist.xmldb.DatabaseImpl.getRemoteCollection(DatabaseImpl.java:241) at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:182) at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:171) at org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:235) at org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:201) Is xmldb supposed to be thread safe? If so, does that HashMap need to be changed to a ConcurrentHashMap or some other type of external synchronization added to HashMap? Thanks. Bernard Harris |
From: Jo C. <Jo....@ha...> - 2024-06-06 07:32:02
|
Hi all, The above jars show up in the lib directories in eXist-db 6.2.0 and earlier releases. The presence of jdom-2.0.6 suggests that the earlier versions are redundant. Is anyone aware of a reason not to remove the earlier jars and references to them in etc/*.xml? Cheers, -- Jo |
From: Dr. V. J. <vjv...@gm...> - 2024-06-04 15:29:59
|
Dear Support Team, I am using KIT Data Manager Base-repo services ( https://github.com/kit-data-manager/base-repo) which has PostgreSQL at the back end. It creates Digital Objects and these digital objects are stored in PostgreSQL. Now in Digital objects, we can store tei-xml files, normal xml files, images or some other defined format files, which it stores as a blob. In my project, I am storing tei-xml in these. But my problem is it can not read these files and give me only chapter 4 from file A of corpus B. So I need eXist DB and I can write Xquery and get only selected chapter or passage from the corpus but for setting it up, I have some doubts: First of all, it is duplicating the files and here we are talking about a huge number of files, using lsdf storage. Secondly, how to handle data updates? Base-repo can send a message like "base repo content changed" but in eXist DB, who will receive this message and after that, maybe it should initiate some triggers? Now I am not very new with eXist and already tried collections.conf for some indexing so please explain or write to me, in which direction I should focus. I am a bit lost at the moment. Thanks & Regards, Dr. Vandana Jha Data Exploitation Methods (DEM), Scientific Computing Center (SCC), Karlsruhe Institute of Technology (KIT) Hermann-von-Helmholtz-Platz 1 76344 Eggenstein-Leopoldshafen Karlsruhe, Germany. E-mail: van...@ki... <van...@ki...> http://www.scc.kit.edu On Tue, Mar 26, 2024 at 10:41 AM Dr. VANDANA JHA <vjv...@gm...> wrote: > Dear Support Team, > > I have a repository of TEI-XML files stored in PostgreSQL and my > requirement is to index this file so that it can be queried for the line > number and chapter number of a particular word in the document. > > I guess, I can populate that same repository contents in eXist-DB and then > index it. But as this PostgreSQL repository is a small part of a big > project and due to other more important requirement, I have to keep this > repository. > > So my question is, > Is it possible to set somewhere path to this PostgreSQL repository in > eXist-DB and then use these stored file and directory structure in eXist-DB > to index/work with them? So here I want to skip the process of storing > these files again in eXist-DB. This will serve two purpose for me. First > the data will not be duplicated at two places so it will save the effort in > data consistency. Second, this data will be updated may be later and always > I want the data to be read from my postgreSQL and eXist DB should be doing > read only task and not write into these files so it will be perfect for me, > if by setting path, it reads from the original repository itself. > > Any help in this regard, will be really appreciated. > > Thanks & Regards, > Dr. Vandana Jha > > Data Exploitation Methods (DEM), > Scientific Computing Center (SCC), > Karlsruhe Institute of Technology (KIT) > > Hermann-von-Helmholtz-Platz 1 > 76344 Eggenstein-Leopoldshafen > Karlsruhe, Germany. > E-mail: van...@ki... <van...@ki...> > http://www.scc.kit.edu > > |
From: Craig B. <cra...@ma...> - 2024-05-31 01:54:04
|
> On May 30, 2024, at 5:42 PM, Ralph Corrigan <ra...@ra...> wrote: > > Hi Joe, thanks for getting back to me. > Yes, we're currently using shared-resources - noted that this needs updating too! As for the deprecation message it's here: > https://exist-db.org/exist/apps/doc/templating#surround I've long since switched to the new templating library but I do use templates:surround and this is the first I've heard of its being deprecated. The PR here: https://github.com/eXist-db/templating/pull/17 labeled "Next major version" says, about 50 lines in, "Don't worry templates:surround is still... around." Which of course does make one worry since it clearly implies someone thinks there's something wrong with it. There is some language about "Embrace the top-down approach," but why one would do that is a mystery. I guess the good news is that at least one more major version will have templates:surround, and it's been almost a year since there were any commits to the project so there may be no hurry about getting ready for even that version, much less a future one that actually removes templates:surround. > > On 30/05/2024 21:32, Joe Wicentowski wrote: >> Hi Ralph, >> Are you using the templating module from the shared-resources package? Or are you using the newer HTML templating module? >> - shared-resources: https://github.com/eXist-db/shared-resources >> - templating: https://github.com/eXist-db/templating >> Also, could you please share the URL to the page you're looking at that mentions the deprecation? >> Thanks, >> Joe >> >> On Thu, May 30, 2024 at 12:25 PM Ralph Corrigan <ra...@ra...> wrote: >> Hi all, >> We've recently updated (long-overdue) our eXist instances, which has prompted me to check the latest documentation. I notice that the template:surround is deprecated, but I'm not clear about what it should be replaced with. >> Our current apps use templates:surround with pointers to templates/picktherelevantpage.html. Templates:surround is still declared in the updated shared resources templates.xql (assuming that has updated correctly) so there's no problem for now, but as we're building a new app at present it would be good to use whatever the new preferred method is. Any thoughts? >> Thanks >> Ralph >> _______________________________________________ >> 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 ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |
From: Ralph C. <ra...@ra...> - 2024-05-30 22:42:55
|
Hi Joe, thanks for getting back to me. Yes, we're currently using shared-resources - noted that this needs updating too! As for the deprecation message it's here: https://exist-db.org/exist/apps/doc/templating#surround Cheers Ralph On 30/05/2024 21:32, Joe Wicentowski wrote: > Hi Ralph, > > Are you using the templating module from the shared-resources package? > Or are you using the newer HTML templating module? > > - shared-resources: https://github.com/eXist-db/shared-resources > - templating: https://github.com/eXist-db/templating > > Also, could you please share the URL to the page you're looking at that > mentions the deprecation? > > Thanks, > Joe > > On Thu, May 30, 2024 at 12:25 PM Ralph Corrigan <ra...@ra...> > wrote: > >> Hi all, >> >> We've recently updated (long-overdue) our eXist instances, which has >> prompted me to check the latest documentation. I notice that the >> template:surround is deprecated, but I'm not clear about what it >> should be replaced with. >> >> Our current apps use templates:surround with pointers to >> templates/_picktherelevantpage_.html. Templates:surround is still >> declared in the updated shared resources templates.xql (assuming that >> has updated correctly) so there's no problem for now, but as we're >> building a new app at present it would be good to use whatever the new >> preferred method is. Any thoughts? >> >> Thanks >> >> Ralph _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open |
From: Joe W. <jo...@gm...> - 2024-05-30 20:33:09
|
Hi Ralph, Are you using the templating module from the shared-resources package? Or are you using the newer HTML templating module? - shared-resources: https://github.com/eXist-db/shared-resources - templating: https://github.com/eXist-db/templating Also, could you please share the URL to the page you're looking at that mentions the deprecation? Thanks, Joe On Thu, May 30, 2024 at 12:25 PM Ralph Corrigan <ra...@ra...> wrote: > Hi all, > > We've recently updated (long-overdue) our eXist instances, which has > prompted me to check the latest documentation. I notice that the > template:surround is deprecated, but I'm not clear about what it should be > replaced with. > > Our current apps use templates:surround with pointers to templates/ > *picktherelevantpage*.html. Templates:surround is still declared in the > updated shared resources templates.xql (assuming that has updated > correctly) so there's no problem for now, but as we're building a new app > at present it would be good to use whatever the new preferred method is. > Any thoughts? > > Thanks > > Ralph > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
From: David B. <dj...@gm...> - 2024-05-30 16:28:42
|
Dear eXist-db list, A light-weight script that initializes a new eXist-db app without relying on Node is available at https://github.com/Pittsburgh-NEH-Institute/eXistentializer. It achieves its relative ease of use by omitting many features supported by generator-exist, such as testing (limited support), CI (no support), and Docker (no support). Best, David On Thu, May 30, 2024 at 11:50 AM Joshua Schäuble <jos...@gm...> wrote: > Tldr: Just to add a +1 to this topic, I'm agreeing here, too. > > Long version: When the integrated app creation tool was removed 2y ago, > it took me hours to get the recommended npm package to run, repeatedly > getting stuck in NPMs dependency overhead hell. Once it finally ran without > any errors, I still ended up with a package that did not install in the > (then latest) eXist. I tried several times over the past years and so far I > never managed to produce a working app with this (fair enough, I'm rarely > asking for support, always thinking I'm the idiot). > > Sure, npm has been a standard for quite a while now and there are probably > good reasons not to use the old integrated legacy app creation tool - but > it's somewhat off putting for non-Node developers to download and run an > overhead of hundreds of megabytes of npm dependencies, just to produce a > comparable tiny app scaffold (that then won't even install). > > So I opted for the same workaround described here before: I installed a > legacy version of eXist just to create an app scaffold - and then > downloaded and installed it on the latest version (worrying it might be > insecure, but at least it runs). While this still works smoothly to this > date, it lead to me not using exist much for app development anymore, but > only as a database via the REST API. Maybe that's for the better anyways. > > -- end of long version > > > Nick Sincaglia <nsi...@nu...> schrieb am Do., 30. Mai 2024, > 15:48: > >> I agree. That app builder was pretty handy. We continue to run an old >> version of eXist-db just for this purpose. We will create new apps using >> this old version and download the XAR package and install it on the newer >> versions of eXist-db we run in production. >> >> Nick >> >> On 5/30/24 1:38 AM, Michael Pilarski wrote: >> >> Hi Don, >> >> please see Joe's answer to this topic at >> https://stackoverflow.com/a/70189542. >> >> Michael >> >> Am Do., 30. Mai 2024 um 01:43 Uhr schrieb John Reed <jr...@gm...>: >> >>> I believe that no longer is available with a later version because of >>> some kind of security problem. I would like that back. It was great to be >>> able to create an app without really thinking about it and just building on >>> top of what was there. I wish they would put it back in the later version. >>> >>> Sent from my iPhone >>> >>> On May 29, 2024, at 4:36 PM, Don Smith via Exist-open < >>> exi...@li...> wrote: >>> >>> >>> Hello everyone, >>> >>> I've just installed eXist 6.2.0 on Windows 11. >>> >>> * The DB is running >>> * I'm logged in as Admin (eXide shows "Logged in as Admin") >>> >>> In eXide, when I click on "Application" there is no "New Application" >>> option available. The only menu options I see are: >>> >>> * Download app >>> * Synchronize >>> * Live reload >>> >>> I assume that something has gone wrong in the install but ?? >>> >>> I've looked through the Packages that are available to install and don't >>> see anything there that looks like what I need. Is it possible the option >>> has moved to a different location in 6.0.2? Is there another way to >>> create a new application? >>> >>> Any help is appreciated as this appears to be a complete show stopper >>> (can't create new applications). >>> >>> Don >>> >>> _______________________________________________ >>> 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 lis...@li...https://lists.sourceforge.net/lists/listinfo/exist-open >> >> >> -- >> Nick Sincaglia >> President/Founder >> NueMeta, LLC >> Digital Media & Technology >> Phone: +1-...@nu... http://www.nuemeta.com >> Skype: nsincaglia >> >> _______________________________________________ >> 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: Joshua S. <jos...@gm...> - 2024-05-30 15:49:15
|
Tldr: Just to add a +1 to this topic, I'm agreeing here, too. Long version: When the integrated app creation tool was removed 2y ago, it took me hours to get the recommended npm package to run, repeatedly getting stuck in NPMs dependency overhead hell. Once it finally ran without any errors, I still ended up with a package that did not install in the (then latest) eXist. I tried several times over the past years and so far I never managed to produce a working app with this (fair enough, I'm rarely asking for support, always thinking I'm the idiot). Sure, npm has been a standard for quite a while now and there are probably good reasons not to use the old integrated legacy app creation tool - but it's somewhat off putting for non-Node developers to download and run an overhead of hundreds of megabytes of npm dependencies, just to produce a comparable tiny app scaffold (that then won't even install). So I opted for the same workaround described here before: I installed a legacy version of eXist just to create an app scaffold - and then downloaded and installed it on the latest version (worrying it might be insecure, but at least it runs). While this still works smoothly to this date, it lead to me not using exist much for app development anymore, but only as a database via the REST API. Maybe that's for the better anyways. -- end of long version Nick Sincaglia <nsi...@nu...> schrieb am Do., 30. Mai 2024, 15:48: > I agree. That app builder was pretty handy. We continue to run an old > version of eXist-db just for this purpose. We will create new apps using > this old version and download the XAR package and install it on the newer > versions of eXist-db we run in production. > > Nick > > On 5/30/24 1:38 AM, Michael Pilarski wrote: > > Hi Don, > > please see Joe's answer to this topic at > https://stackoverflow.com/a/70189542. > > Michael > > Am Do., 30. Mai 2024 um 01:43 Uhr schrieb John Reed <jr...@gm...>: > >> I believe that no longer is available with a later version because of >> some kind of security problem. I would like that back. It was great to be >> able to create an app without really thinking about it and just building on >> top of what was there. I wish they would put it back in the later version. >> >> Sent from my iPhone >> >> On May 29, 2024, at 4:36 PM, Don Smith via Exist-open < >> exi...@li...> wrote: >> >> >> Hello everyone, >> >> I've just installed eXist 6.2.0 on Windows 11. >> >> * The DB is running >> * I'm logged in as Admin (eXide shows "Logged in as Admin") >> >> In eXide, when I click on "Application" there is no "New Application" >> option available. The only menu options I see are: >> >> * Download app >> * Synchronize >> * Live reload >> >> I assume that something has gone wrong in the install but ?? >> >> I've looked through the Packages that are available to install and don't >> see anything there that looks like what I need. Is it possible the option >> has moved to a different location in 6.0.2? Is there another way to >> create a new application? >> >> Any help is appreciated as this appears to be a complete show stopper >> (can't create new applications). >> >> Don >> >> _______________________________________________ >> 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 lis...@li...https://lists.sourceforge.net/lists/listinfo/exist-open > > > -- > Nick Sincaglia > President/Founder > NueMeta, LLC > Digital Media & Technology > Phone: +1-...@nu... http://www.nuemeta.com > Skype: nsincaglia > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
From: Nick S. <nsi...@nu...> - 2024-05-30 13:47:47
|
I agree. That app builder was pretty handy. We continue to run an old version of eXist-db just for this purpose. We will create new apps using this old version and download the XAR package and install it on the newer versions of eXist-db we run in production. Nick On 5/30/24 1:38 AM, Michael Pilarski wrote: > Hi Don, > > please see Joe's answer to this topic at > https://stackoverflow.com/a/70189542. > > Michael > > Am Do., 30. Mai 2024 um 01:43 Uhr schrieb John Reed <jr...@gm...>: > > I believe that no longer is available with a later version because > of some kind of security problem. I would like that back. It was > great to be able to create an app without really thinking about it > and just building on top of what was there. I wish they would put > it back in the later version. > > Sent from my iPhone > >> On May 29, 2024, at 4:36 PM, Don Smith via Exist-open >> <exi...@li...> wrote: >> >> >> Hello everyone, >> >> I've just installed eXist 6.2.0 on Windows 11. >> >> * The DB is running >> * I'm logged in as Admin (eXide shows "Logged in as Admin") >> >> In eXide, when I click on "Application" there is no "New >> Application" option available. The only menu options I see are: >> >> * Download app >> * Synchronize >> * Live reload >> >> I assume that something has gone wrong in the install but ?? >> >> I've looked through the Packages that are available to install >> and don't see anything there that looks like what I need. Is it >> possible the option has moved to a different location in 6.0.2? >> Is there another way to create a new application? >> >> Any help is appreciated as this appears to be a complete show >> stopper (can't create new applications). >> >> Don >> >> _______________________________________________ >> 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 -- Nick Sincaglia President/Founder NueMeta, LLC Digital Media & Technology Phone: +1-630-303-7035 nsi...@nu... http://www.nuemeta.com Skype: nsincaglia |
From: Ralph C. <ra...@ra...> - 2024-05-30 10:23:26
|
Hi all, We've recently updated (long-overdue) our eXist instances, which has prompted me to check the latest documentation. I notice that the template:surround is deprecated, but I'm not clear about what it should be replaced with. Our current apps use templates:surround with pointers to templates/_picktherelevantpage_.html. Templates:surround is still declared in the updated shared resources templates.xql (assuming that has updated correctly) so there's no problem for now, but as we're building a new app at present it would be good to use whatever the new preferred method is. Any thoughts? Thanks Ralph |
From: Michael P. <mic...@gm...> - 2024-05-30 06:39:18
|
Hi Don, please see Joe's answer to this topic at https://stackoverflow.com/a/70189542. Michael Am Do., 30. Mai 2024 um 01:43 Uhr schrieb John Reed <jr...@gm...>: > I believe that no longer is available with a later version because of some > kind of security problem. I would like that back. It was great to be able > to create an app without really thinking about it and just building on top > of what was there. I wish they would put it back in the later version. > > Sent from my iPhone > > On May 29, 2024, at 4:36 PM, Don Smith via Exist-open < > exi...@li...> wrote: > > > Hello everyone, > > I've just installed eXist 6.2.0 on Windows 11. > > * The DB is running > * I'm logged in as Admin (eXide shows "Logged in as Admin") > > In eXide, when I click on "Application" there is no "New Application" > option available. The only menu options I see are: > > * Download app > * Synchronize > * Live reload > > I assume that something has gone wrong in the install but ?? > > I've looked through the Packages that are available to install and don't > see anything there that looks like what I need. Is it possible the option > has moved to a different location in 6.0.2? Is there another way to > create a new application? > > Any help is appreciated as this appears to be a complete show stopper > (can't create new applications). > > Don > > _______________________________________________ > 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: John R. <jr...@gm...> - 2024-05-29 23:42:16
|
I believe that no longer is available with a later version because of some kind of security problem. I would like that back. It was great to be able to create an app without really thinking about it and just building on top of what was there. I wish they would put it back in the later version. Sent from my iPhone > On May 29, 2024, at 4:36 PM, Don Smith via Exist-open <exi...@li...> wrote: > > > Hello everyone, > > I've just installed eXist 6.2.0 on Windows 11. > > * The DB is running > * I'm logged in as Admin (eXide shows "Logged in as Admin") > > In eXide, when I click on "Application" there is no "New Application" option available. The only menu options I see are: > > * Download app > * Synchronize > * Live reload > > I assume that something has gone wrong in the install but ?? > > I've looked through the Packages that are available to install and don't see anything there that looks like what I need. Is it possible the option has moved to a different location in 6.0.2? Is there another way to create a new application? > > Any help is appreciated as this appears to be a complete show stopper (can't create new applications). > > Don > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
From: Don S. <dsm...@ya...> - 2024-05-29 23:35:01
|
Hello everyone, I've just installed eXist 6.2.0 on Windows 11. * The DB is running* I'm logged in as Admin (eXide shows "Logged in as Admin") In eXide, when I click on "Application" there is no "New Application" option available. The only menu options I see are: * Download app* Synchronize* Live reload I assume that something has gone wrong in the install but ?? I've looked through the Packages that are available to install and don't see anything there that looks like what I need. Is it possible the option has moved to a different location in 6.0.2? Is there another way to create a new application? Any help is appreciated as this appears to be a complete show stopper (can't create new applications). Don |
From: Tony C. <t.c...@su...> - 2024-05-15 07:52:20
|
Dear Jean-Paul, Thanks, having read it twice that makes perfect sense. The file is available locally to a browser but (currently) is not accessible over the network, so I now understand what I have to fix. Kind regards, Tony From: Jean-Paul Rehr <re...@gm...> Sent: Tuesday, May 14, 2024 10:22 PM To: Corless, Tony (Comp Sci & Elec Eng) <t.c...@su...> Cc: exi...@li... Subject: Re: [Exist-open] Embedding PDF from file system in webpage Dear Tony, The fact that your file on your file server is accessible to eXist is not really material, and is a distraction from the root cause of the problem. Is your variable $document a URL where the PDF can be accessed via the web? If so, that link should work in a browser...so if you copy and paste it, the file shoud be available? If it is not, then the link is not correct, or your file server is not configured (with a proxy server) to serve files to the internet... eXist is only transmitting a link to the browser via the attribute src; it's the browser that acts upon the link that is in the attribute. Cheers, JPR On Tue, May 14, 2024 at 10:18 PM Tony Corless via Exist-open <exi...@li...<mailto:exi...@li...>> wrote: Apologies for bothering people, as the answer to this perhaps should be obvious to me. For a while I have been using a query, as below, to display PDF documents with some header information that is stored as XML data in eXist. To date, the PDFs have been small and stored in the eXist database or accessed from a remote server. Now I have some much larger PDF documents that ideally I will keep in the local file system rather than in the database. To achieve that I need to change the source in the <embed> below to access the document from the file system. While I assumed that would be trivial my attempts to date have failed. Any pointer to the correct approach is welcome, as clearly I have misunderstood something. (The file:exists function has confirmed that I have correct and accessible files in the file system, I can read these but have failed to render them as PDF.) xquery version "3.1"; declare option exist:serialize "method=html media-type=text/html"; (: declare variable $documentName := request:get-parameter("documentName",()); :) let $documentName :="1021-COP" let $xmlCollection := collection("/db/apps/controlledDocuments/data/current") let $document :=$xmlCollection[./document/documentName=$documentName]/document/documentLink return <html> <body> <h1>Some info about {$documentName}</h1> <embed src='{$document}' style="width:100%;height:90%;"></embed> </body> </html> Many thanks for any assistance. Tony Corless _______________________________________________ Exist-open mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open |
From: Erik S. <er...@xa...> - 2024-05-15 07:33:20
|
Call for papers, Declarative Amsterdam conference, 2024 The sixth edition of Declarative Amsterdam will take place on 7 and 8 November, 2024 at the Science Park, Amsterdam. It will be a hybrid conference with the opportunity to attend live or online, for both attendees and presenters. Declarative techniques are a style of computing that expresses the purpose of computation without describing its control flow. It allows you to focus on the ‘what’, rather than the ‘how’. Declarative Amsterdam will have presentations on past experiences, current trends and future perspectives in fields such as functional programming, declarative data modelling, databases, XML and related technologies, JSON, CSS, semantic web, data science, data visualization, grammars, parsing, and domain-specific languages. 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 20 and 45 minutes. Speakers can present in person, or prepare a video, and be available online for the question-and-answer session afterwards. Proposals should include a title, duration and summary (90 - 200 words), and may also include a full paper. Presenters have the option of submitting a full paper or slides, to be published on the Declarative Amsterdam website. For papers and topics from previous years, see the website: <https://declarative.amsterdam/> https://declarative.amsterdam/ Please submit your proposal at <https://declarative.amsterdam/cfp> https://declarative.amsterdam/cfp Timeline: Submission deadline: 31 July Acceptance: Beginning of September Videos, tutorials, papers submission: Beginning of October Conference: 7 and 8 November Regards, The Declarative Amsterdam organizing committee. |
From: Jean-Paul R. <re...@gm...> - 2024-05-14 21:22:07
|
Dear Tony, The fact that your file on your file server is accessible to eXist is not really material, and is a distraction from the root cause of the problem. Is your variable $document a URL where the PDF can be accessed via the web? If so, that link should work in a browser...so if you copy and paste it, the file shoud be available? If it is not, then the link is not correct, or your file server is not configured (with a proxy server) to serve files to the internet... eXist is only transmitting a link to the browser via the attribute src; it's the browser that acts upon the link that is in the attribute. Cheers, JPR On Tue, May 14, 2024 at 10:18 PM Tony Corless via Exist-open < exi...@li...> wrote: > Apologies for bothering people, as the answer to this perhaps should be > obvious to me. > > > > For a while I have been using a query, as below, to display PDF documents > with some header information that is stored as XML data in eXist. > > To date, the PDFs have been small and stored in the eXist database or > accessed from a remote server. > > > > Now I have some much larger PDF documents that ideally I will keep in the > local file system rather than in the database. > > To achieve that I need to change the source in the <embed> below to access > the document from the file system. > > > > While I assumed that would be trivial my attempts to date have failed. Any > pointer to the correct approach is welcome, as clearly I have misunderstood > something. > > > > (The file:exists function has confirmed that I have correct and accessible > files in the file system, I can read these but have failed to render them > as PDF.) > > > > > > xquery version "3.1"; > > declare option exist:serialize "method=html media-type=text/html"; > > (: declare variable $documentName := > request:get-parameter("documentName",()); :) > > > > let $documentName :="1021-COP" > > > > let $xmlCollection := > collection("/db/apps/controlledDocuments/data/current") > > let $document > :=$xmlCollection[./document/documentName=$documentName]/document/documentLink > > > > return > > <html> > > <body> > > <h1>Some info about {$documentName}</h1> > > <embed src='{$document}' > style="width:100%;height:90%;"></embed> > > </body> > > </html> > > > > > > Many thanks for any assistance. > > > > *Tony Corless* > > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
From: Claudius T. <cla...@gm...> - 2024-05-14 20:46:24
|
Separate fileserver (see https://caddyserver.com/) for those big PDFs. On Tue, 14 May 2024, 23:18 Tony Corless via Exist-open, < exi...@li...> wrote: > Apologies for bothering people, as the answer to this perhaps should be > obvious to me. > > > > For a while I have been using a query, as below, to display PDF documents > with some header information that is stored as XML data in eXist. > > To date, the PDFs have been small and stored in the eXist database or > accessed from a remote server. > > > > Now I have some much larger PDF documents that ideally I will keep in the > local file system rather than in the database. > > To achieve that I need to change the source in the <embed> below to access > the document from the file system. > > > > While I assumed that would be trivial my attempts to date have failed. Any > pointer to the correct approach is welcome, as clearly I have misunderstood > something. > > > > (The file:exists function has confirmed that I have correct and accessible > files in the file system, I can read these but have failed to render them > as PDF.) > > > > > > xquery version "3.1"; > > declare option exist:serialize "method=html media-type=text/html"; > > (: declare variable $documentName := > request:get-parameter("documentName",()); :) > > > > let $documentName :="1021-COP" > > > > let $xmlCollection := > collection("/db/apps/controlledDocuments/data/current") > > let $document > :=$xmlCollection[./document/documentName=$documentName]/document/documentLink > > > > return > > <html> > > <body> > > <h1>Some info about {$documentName}</h1> > > <embed src='{$document}' > style="width:100%;height:90%;"></embed> > > </body> > > </html> > > > > > > Many thanks for any assistance. > > > > *Tony Corless* > > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
From: Tony C. <t.c...@su...> - 2024-05-14 20:17:26
|
Apologies for bothering people, as the answer to this perhaps should be obvious to me. For a while I have been using a query, as below, to display PDF documents with some header information that is stored as XML data in eXist. To date, the PDFs have been small and stored in the eXist database or accessed from a remote server. Now I have some much larger PDF documents that ideally I will keep in the local file system rather than in the database. To achieve that I need to change the source in the <embed> below to access the document from the file system. While I assumed that would be trivial my attempts to date have failed. Any pointer to the correct approach is welcome, as clearly I have misunderstood something. (The file:exists function has confirmed that I have correct and accessible files in the file system, I can read these but have failed to render them as PDF.) xquery version "3.1"; declare option exist:serialize "method=html media-type=text/html"; (: declare variable $documentName := request:get-parameter("documentName",()); :) let $documentName :="1021-COP" let $xmlCollection := collection("/db/apps/controlledDocuments/data/current") let $document :=$xmlCollection[./document/documentName=$documentName]/document/documentLink return <html> <body> <h1>Some info about {$documentName}</h1> <embed src='{$document}' style="width:100%;height:90%;"></embed> </body> </html> Many thanks for any assistance. Tony Corless |
From: Jo C. <Jo....@ha...> - 2024-05-03 13:54:24
|
Hi all, As this release is now a bit more than a year old, some of the .jar files in the release are going stale, particularly in respect of CVE findings. Are there any plans in this respect? Best, -- Jo |
From: Joern T. <joe...@gm...> - 2024-04-17 08:24:32
|
Hi Joe, of course On Tue, Apr 16, 2024 at 7:12 PM Joe Wicentowski <jo...@gm...> wrote: > Hi Hank, > > I recently came across HTMX too and am also curious to hear if anyone has > been using it. In particular, I wonder about its possible integration with > Fore (cc/ Joern). > > Joe > > On Tue, Apr 16, 2024 at 1:01 PM Hank Ratzesberger via Exist-open < > exi...@li...> wrote: > >> Hello Exist (ential List) >> >> I've not been reading very closely, so sorry if I've missed this. I've >> been in the DevOps space for the last five years, but looking at web >> applications again. >> >> I don't recall if eXist has a HATEOS step/pipeline/transform but it seems >> that's all that would be necessary to easily support htmx browser side >> applications. These applications minimize JavaScript to only extending some >> elements with attributes hx-get, hx-post, etc., that expect html responses, >> and replace the content of the element or its parent. >> >> Anyone experimenting with this? >> >> https://htmx.org/ >> >> Best, >> Hank >> >> -- >> Hank R >> i/o werx company >> 831 252 0118 >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > |