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
|
Nov
|
Dec
|
|
From: Hayim L. <hl...@um...> - 2025-02-17 15:59:41
|
Thanks! I will definitely try this.
On Sun, Feb 16, 2025 at 4:14 AM Florian Schmitt <
ml-...@fl...> wrote:
> Hayim,
>
> it seems that in certain cases, the default apps aren't deployed
> correctly. If I remember correctly, I ran into a similar issue with a
> headless setup.
>
> Please try the following (assuming eXist is installed in /opt/existdb -
> adapt the paths according to your setup):
>
> First, check if there's a directory /opt/existdb/autodeploy containing the
> .xar files for eXide and so on.
>
> If the autodeploy directory seems fine, stop exist-db, and open
> /opt/existdb/etc/conf.xml in a text editor.
>
> Search for the following lines:
>
> <trigger class="org.exist.repo.AutoDeploymentTrigger">
> <!-- parameter name="ignore-autodeploy-system-property" value="true"/ -->
> <!-- parameter name="dir" value="${project.build.outputDirectory}/autodeploy"/ -->
> </trigger>
>
> Uncomment the second "parameter" element, and change the "value"
> attribute, setting the full path to the autodeploy directory. With exist
> installed in /opt/existdb, the third line should now be
>
> <parameter name="dir" value="/opt/existdb/autodeploy" />
>
> Now, restart exist-db and check the logs for messages regarding
> autodeployment. If the AutoDeploymentTrigger doesn't fire, you may have to
> uncomment the first parameter element, too.
>
> HTH
> Florian
>
> Am 14.02.25 um 16:42 schrieb Hayim Lapin:
>
> Hello,
> I just installed eXist 6.3 on an aws linux machine running on port *8081*.
> The database loads and I can log in as admin.
> All the default apps that appear on the launcher yield errors like:
> HTTP ERROR 404 Document /db/apps/eXide not found
>
> I have been able to use the package manager to load and run an app
> (TEI-Publisher), but other apps created by me and working in a docker
> instance generate the following again caused by being unable to access /db:
>
>> err:XPST0017 error found while loading .... for module:
>> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line
>> 84, column 13]
>
>
> There is another version of exist (4.7.1) running on port *8080*. Could
> this be the cause of the problem?
>
> Any suggestions about how to fix this?
> Best, HL
>
>
> _______________________________________________
> 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
>
|
|
From: Florian S. <ml-...@fl...> - 2025-02-15 19:43:39
|
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hayim,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">it seems that in certain cases, the
default apps aren't deployed correctly. If I remember correctly, I
ran into a similar issue with a headless setup.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Please try the following (assuming
eXist is installed in /opt/existdb - adapt the paths according to
your setup):<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">First, check if there's a directory
/opt/existdb/autodeploy containing the .xar files for eXide and so
on.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"></div>
<div class="moz-cite-prefix">If the autodeploy directory seems fine,
stop exist-db, and open /opt/existdb/etc/conf.xml in a text
editor.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Search for the following lines:</div>
<pre class="moz-cite-prefix"><trigger class="org.exist.repo.AutoDeploymentTrigger">
<!-- parameter name="ignore-autodeploy-system-property" value="true"/ -->
<!-- parameter name="dir" value="${project.build.outputDirectory}/autodeploy"/ -->
</trigger>
</pre>
<div class="moz-cite-prefix">Uncomment the second "parameter"
element, and change the "value" attribute, setting the full path
to the autodeploy directory. With exist installed in /opt/existdb,
the third line should now be <br>
</div>
<pre class="moz-cite-prefix"><parameter name="dir" value="/opt/existdb/autodeploy" /></pre>
<div class="moz-cite-prefix">Now, restart exist-db and check the
logs for messages regarding autodeployment. If the
AutoDeploymentTrigger doesn't fire, you may have to uncomment the
first parameter element, too.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">HTH</div>
<div class="moz-cite-prefix">Florian<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 14.02.25 um 16:42 schrieb Hayim
Lapin:<br>
</div>
<blockquote type="cite"
cite="mid:CAE=1_O_Y4moZDk=FA4...@ma...">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div>Hello,</div>
<div>I just installed eXist 6.3 on an aws linux machine
running on port <b>8081</b>.</div>
<div>The database loads and I can log in as admin. </div>
<div>All the default apps that appear on the launcher
yield errors like:</div>
<div>HTTP ERROR 404 Document /db/apps/eXide not found</div>
<div><br>
</div>
<div>I have been able to use the package manager to load and
run an app (TEI-Publisher), but other apps created by me and
working in a docker instance generate the following again
caused by being unable to access /db:</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">err:XPST0017
error found while loading .... for module:
/db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql
[at line 84, column 13]</blockquote>
<div><br>
</div>
<div>There is another version of exist (4.7.1) running on port
<b>8080</b>. Could this be the cause of the problem?</div>
<div><br>
</div>
<div>Any suggestions about how to fix this?</div>
<div>Best, HL </div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
Exist-open mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Exi...@li...">Exi...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/exist-open">https://lists.sourceforge.net/lists/listinfo/exist-open</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>
|
|
From: Hayim L. <hl...@um...> - 2025-02-14 16:10:19
|
Sorry -- figured it out. Needed to restart *again* On Fri, Feb 14, 2025 at 10:42 AM Hayim Lapin <hl...@um...> wrote: > Hello, > I just installed eXist 6.3 on an aws linux machine running on port *8081*. > The database loads and I can log in as admin. > All the default apps that appear on the launcher yield errors like: > HTTP ERROR 404 Document /db/apps/eXide not found > > I have been able to use the package manager to load and run an app > (TEI-Publisher), but other apps created by me and working in a docker > instance generate the following again caused by being unable to access /db: > >> err:XPST0017 error found while loading .... for module: >> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line >> 84, column 13] > > > There is another version of exist (4.7.1) running on port *8080*. Could > this be the cause of the problem? > > Any suggestions about how to fix this? > Best, HL > |
|
From: Hayim L. <hl...@um...> - 2025-02-14 16:07:13
|
Sorry to sound like a complete idiot, but in fact the errors still exist (I in error tested the local docker instance ...) On Fri, Feb 14, 2025 at 10:42 AM Hayim Lapin <hl...@um...> wrote: > Hello, > I just installed eXist 6.3 on an aws linux machine running on port *8081*. > The database loads and I can log in as admin. > All the default apps that appear on the launcher yield errors like: > HTTP ERROR 404 Document /db/apps/eXide not found > > I have been able to use the package manager to load and run an app > (TEI-Publisher), but other apps created by me and working in a docker > instance generate the following again caused by being unable to access /db: > >> err:XPST0017 error found while loading .... for module: >> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line >> 84, column 13] > > > There is another version of exist (4.7.1) running on port *8080*. Could > this be the cause of the problem? > > Any suggestions about how to fix this? > Best, HL > |
|
From: Hayim L. <hl...@um...> - 2025-02-14 15:42:44
|
Hello, I just installed eXist 6.3 on an aws linux machine running on port *8081*. The database loads and I can log in as admin. All the default apps that appear on the launcher yield errors like: HTTP ERROR 404 Document /db/apps/eXide not found I have been able to use the package manager to load and run an app (TEI-Publisher), but other apps created by me and working in a docker instance generate the following again caused by being unable to access /db: > err:XPST0017 error found while loading .... for module: > /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line > 84, column 13] There is another version of exist (4.7.1) running on port *8080*. Could this be the cause of the problem? Any suggestions about how to fix this? Best, HL |
|
From: Craig B. <cra...@ma...> - 2025-02-01 12:51:45
|
> On Jan 31, 2025, at 3:04 PM, Craig Berry via Exist-open <exi...@li...> wrote:
>
>
> -----
> Cannot compile xquery: exerr:ERROR error found while loading module console: Cannot find module class from EXPath repository: org.exist.console.xquery.ConsoleModule
> -----
Still don't know why it was necessary, but I solved this by uninstalling and reinstalling Monex.
________________________________________
Craig A. Berry
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
|
|
From: Craig B. <cra...@ma...> - 2025-01-31 21:05:15
|
I tried eXist 6.3.0 but cannot use it be because things I depend on use modules with location hints and I get the XQST0059 error as described here: https://github.com/eXist-db/exist/issues/5530 So, I thought, since 6.2.0 and 6.3.0 are binary compatible, I'd just downgrade to 6.2.0 and keep the same data directory and be back where I was. I did that but now it can't find the console module using an import statement that's worked for years. This XQuery: ----- xquery version "3.1"; import module namespace console="http://exist-db.org/xquery/console" at "java:org.exist.console.xquery.ConsoleModule"; let $x := console:log('got here') return $x ----- throws this error: ----- Cannot compile xquery: err:XPST0081 Invalid qname console:log. No namespace defined for prefix console. QName is invalid: INVALID_PREFIX [at line 3, column 11] ----- If I remove the location hint I then get: ----- Cannot compile xquery: exerr:ERROR error found while loading module console: Cannot find module class from EXPath repository: org.exist.console.xquery.ConsoleModule ----- The most relevant bits of the stack dump in the log seem to be: Caused by: java.lang.ClassNotFoundException: org.exist.console.xquery.ConsoleModule at java.net.URLClassLoader.findClass(URLClassLoader.java:445) ~[?:?] at java.lang.ClassLoader.loadClass(ClassLoader.java:592) ~[?:?] at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] at java.lang.Class.forName0(Native Method) ~[?:?] at java.lang.Class.forName(Class.java:467) ~[?:?] at org.exist.repo.ExistRepository.getModule(ExistRepository.java:169) ~[exist-core-6.2.0.jar:6.2.0] at org.exist.repo.ExistRepository.resolveJavaModule(ExistRepository.java:155) ~[exist-core-6.2.0.jar:6.2.0] at org.exist.xquery.XQueryContext.resolveInEXPathRepository(XQueryContext.java:579) ~[exist-core-6.2.0.jar:6.2.0] Is there a way to (re)acquire the console module in eXist 6.2.0? This is on Java 17, Mac OS X 15.3 x86_64. ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |
|
From: Murray, G. <gre...@pt...> - 2025-01-09 04:48:04
|
Hello, I’m attempting to create my first RESTXQ web application. I’m unable to figure out how to make use of static files such as images, CSS, and JavaScript files in a RESTXQ context in eXist. Where should such files reside on the filesystem, and how are they referenced in relative URLs? For example, let’s say I’ve got my XQuery modules in /db/apps/my-app/ in which controller.xqm acts as the MVC controller and contains RESTXQ resource functions. Meanwhile the directory /db/apps/my-app/css/ contains CSS files. Other XQuery modules contain MVC views that return HTML to the browser. When including a CSS file in the HTML <head>, what path should be used to refer to a CSS file? I was assuming that something like <link type="text/css" rel="stylesheet" href="css/my.css"/> would suffice, since it is relative to the location of controller.xqm, but that seems to be incorrect. Thanks, Greg |
|
From: Craig B. <cra...@ma...> - 2025-01-08 17:10:49
|
> On Jan 8, 2025, at 9:03 AM, Joe Wicentowski <jo...@GM...> wrote: > > Hi Craig, > > Occasionally the exist-db.org server experiences heavy load and becomes unavailable for a short time. We have a monitoring service that reports such outages and their resolutions. (I believe the one you experienced has now been resolved.) Outages are sent to the eXist-db.org Slack's #integrations channel. > > The monitoring service provides a public status page that you can check if you're ever wondering the current status: > > https://exist-db.betteruptime.com/ That's good to know, thanks. According to that all exist.org services were down for 5 hours yesterday, which squares with what I observed. ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |
|
From: Joe W. <jo...@gm...> - 2025-01-08 16:31:46
|
Hi Demian, Yes, your URL is the landing page for the public-repo app. The link Craig referenced is one of the app's API endpoints. Joe On Wed, Jan 8, 2025 at 11:01 AM Demian Hauptle <dem...@gm...> wrote: > shouldn't it be https://exist-db.org/exist/apps/public-repo/? > > *Demian Hauptle* > *Mobile & Whatsapp: +27 71 462 6937* > dem...@gm... > LinkedIn <http://za.linkedin.com/in/demianhauptle/> > > > > > On Wed, 8 Jan 2025 at 16:53, Craig Berry via Exist-open < > exi...@li...> wrote: > >> I'm currently get 503, service unavailable from < >> https://exist-db.org/exist/apps/public-repo/find>. Is this a known >> problem? >> >> ________________________________________ >> Craig A. Berry >> >> "... getting out of a sonnet is much more >> difficult than getting in." >> Brad Leithauser >> >> >> >> _______________________________________________ >> 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: Demian H. <dem...@gm...> - 2025-01-08 15:18:37
|
shouldn't it be https://exist-db.org/exist/apps/public-repo/? *Demian Hauptle* *Mobile & Whatsapp: +27 71 462 6937* dem...@gm... LinkedIn <http://za.linkedin.com/in/demianhauptle/> On Wed, 8 Jan 2025 at 16:53, Craig Berry via Exist-open < exi...@li...> wrote: > I'm currently get 503, service unavailable from < > https://exist-db.org/exist/apps/public-repo/find>. Is this a known > problem? > > ________________________________________ > Craig A. Berry > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Joe W. <jo...@gm...> - 2025-01-08 15:04:06
|
Hi Craig, Occasionally the exist-db.org server experiences heavy load and becomes unavailable for a short time. We have a monitoring service that reports such outages and their resolutions. (I believe the one you experienced has now been resolved.) Outages are sent to the eXist-db.org Slack's #integrations channel. The monitoring service provides a public status page that you can check if you're ever wondering the current status: https://exist-db.betteruptime.com/ Joe On Wed, Jan 8, 2025 at 9:53 AM Craig Berry via Exist-open < exi...@li...> wrote: > I'm currently get 503, service unavailable from < > https://exist-db.org/exist/apps/public-repo/find>. Is this a known > problem? > > ________________________________________ > Craig A. Berry > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Craig B. <cra...@ma...> - 2025-01-07 15:21:09
|
I'm currently get 503, service unavailable from <https://exist-db.org/exist/apps/public-repo/find>. Is this a known problem? ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |
|
From: Irene V. <ire...@pa...> - 2024-12-12 11:24:22
|
Thank you very much, it was this! In the meantime I was also suggested to look at this https://github.com/eXist-db/documentation/issues/385, so I copy it here in case it may be helpful to others too. Thanks again, Irene > On 11.12.2024 11:17 CET Dannes Wessels <di...@ex...> wrote: > > > > Hi, > > I think you need to register the jar in EXIST_HOME/etc/launcher.xml > > Cheers > > Dannes > > > > > On 4 Dec 2024, at 12:55, Irene Vagionakis <ire...@pa...bh> wrote: > > > > > > > Hi there! > > > > I am trying to add a custom Lucene analyzer that behaves like the WhitespaceAnalyzer concerning tokenization and (lack of) stemming, but that is also case-insensitive (basically the same of https://sourceforge.net/p/exist/mailman/message/35188378/). > > > > I followed what suggested in the post thread above, that is writing the custom analyzer, compiling its class as JAR and saving it in $EXIST_HOME/lib/user, but it is not working. I tried also putting it in the same folder of the other Lucene JAR files, but the same. > > > > Since both my Java/Lucene and eXist-db knowledge are quite poor, I am struggling to figure out whether the problem concerns my code or has to do with eXist-db itself. > > > > This is my custom analyzer code: > > > > package org.custom; > > import org.apache.lucene.analysis.Analyzer; > > import org.apache.lucene.analysis.TokenStream; > > import org.apache.lucene.analysis.core.LowerCaseFilter; > > import org.apache.lucene.analysis.core.WhitespaceTokenizer; > > public class CaseInsensitiveWhitespaceAnalyzer extends Analyzer { > > @Override > > protected TokenStreamComponents createComponents(String fieldName) { > > final WhitespaceTokenizer source = new WhitespaceTokenizer(); > > final TokenStream filter = new LowerCaseFilter(source); > > return new TokenStreamComponents(source, filter); > > } > > } > > > > And this is how I reference to it in collection.xconf: > > <analyzer id="custom" class="org.custom.CaseInsensitiveWhitespaceAnalyzer"/> > > > > I also tested the analyzer outside eXist-db with the following and it returned the expected tokens: > > > > import org.apache.lucene.analysis.Analyzer; > > import org.apache.lucene.analysis.TokenStream; > > import org.apache.lucene.analysis.tokenattributes.CharTermAttribute; > > import org.custom.CaseInsensitiveWhitespaceAnalyzer; > > import java.io.IOException; > > import java.io.StringReader; > > public class TestAnalyzer { > > public static void main(String[] args) throws IOException { > > String text = "Lucene is a Simple1 123 5% _test - Yet Powerful - Java Based Search Library. I love IT!"; > > Analyzer analyzer = new CaseInsensitiveWhitespaceAnalyzer(); > > try (TokenStream tokenStream = analyzer.tokenStream("field", new StringReader(text))) { > > CharTermAttribute charTermAttribute = tokenStream.addAttribute(CharTermAttribute.class); > > tokenStream.reset(); > > while (tokenStream.incrementToken()) { > > System.out.println(charTermAttribute.toString()); > > } > > tokenStream.end(); > > } > > } > > } > > > > What am I doing wrong? Any suggestions/hints will be highly appreciated :) > > > > Thanks, > > Irene > > _______________________________________________ > > Exist-open mailing list > > Exi...@li... > > https://lists.sourceforge.net/lists/listinfo/exist-open > > > |
|
From: Dannes W. <di...@ex...> - 2024-12-11 10:26:05
|
Hi, I think you need to register the jar in EXIST_HOME/etc/launcher.xml Cheers Dannes > On 4 Dec 2024, at 12:55, Irene Vagionakis <ire...@pa...bh> wrote: > > > Hi there! > > I am trying to add a custom Lucene analyzer that behaves like the WhitespaceAnalyzer concerning tokenization and (lack of) stemming, but that is also case-insensitive (basically the same of https://sourceforge.net/p/exist/mailman/message/35188378/). > > I followed what suggested in the post thread above, that is writing the custom analyzer, compiling its class as JAR and saving it in $EXIST_HOME/lib/user, but it is not working. I tried also putting it in the same folder of the other Lucene JAR files, but the same. > > Since both my Java/Lucene and eXist-db knowledge are quite poor, I am struggling to figure out whether the problem concerns my code or has to do with eXist-db itself. > > This is my custom analyzer code: > > package org.custom; > import org.apache.lucene.analysis.Analyzer; > import org.apache.lucene.analysis.TokenStream; > import org.apache.lucene.analysis.core.LowerCaseFilter; > import org.apache.lucene.analysis.core.WhitespaceTokenizer; > public class CaseInsensitiveWhitespaceAnalyzer extends Analyzer { > @Override > protected TokenStreamComponents createComponents(String fieldName) { > final WhitespaceTokenizer source = new WhitespaceTokenizer(); > final TokenStream filter = new LowerCaseFilter(source); > return new TokenStreamComponents(source, filter); > } > } > > And this is how I reference to it in collection.xconf: > <analyzer id="custom" class="org.custom.CaseInsensitiveWhitespaceAnalyzer"/> > > I also tested the analyzer outside eXist-db with the following and it returned the expected tokens: > > import org.apache.lucene.analysis.Analyzer; > import org.apache.lucene.analysis.TokenStream; > import org.apache.lucene.analysis.tokenattributes.CharTermAttribute; > import org.custom.CaseInsensitiveWhitespaceAnalyzer; > import java.io.IOException; > import java.io.StringReader; > public class TestAnalyzer { > public static void main(String[] args) throws IOException { > String text = "Lucene is a Simple1 123 5% _test - Yet Powerful - Java Based Search Library. I love IT!"; > Analyzer analyzer = new CaseInsensitiveWhitespaceAnalyzer(); > try (TokenStream tokenStream = analyzer.tokenStream("field", new StringReader(text))) { > CharTermAttribute charTermAttribute = tokenStream.addAttribute(CharTermAttribute.class); > tokenStream.reset(); > while (tokenStream.incrementToken()) { > System.out.println(charTermAttribute.toString()); > } > tokenStream.end(); > } > } > } > > What am I doing wrong? Any suggestions/hints will be highly appreciated :) > > Thanks, > Irene > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Adam R. <ad...@ex...> - 2024-12-06 14:50:56
|
Hi Eduard, Sorry to hear that this is causing you stress. I can also sympathise with the technical issues you have raised. I already addressed some of those in the past in FusionDB. If you might be interested in Elemental, or you think I might be able to help you, please don't hesitate to get in touch with me - ad...@ev... Kindest regards, and best wishes, Adam. On Fri, 6 Dec 2024 at 09:54, Eduard Drenth <ed...@fr...> wrote: > Dear all, > > For our institution this all strengthens the feeling we need to reconsider > the use of exist-db, we already felt that need because of performance, old > java versions and libs, long standing issues, one highly complex monolithic > solution for both database and app development, no jakarta ee compatible > war, no atomic transactions, poor support for multiuser editing, etc. > > I value Xml and exist-db a lot, don't get me wrong, but our institution > needs to make future proof choices, and I wonder whether sticking with > exist-db is a good choice in that respect. > > Regards, > Eduard > > > > Eduard Drenth, Software Architekt > > > ed...@fr... > > > Doelestrjitte 8 > > 8911 DX Ljouwert > (058) 213 14 14 > > +31 62 094 34 28 > https://www.fryske-akademy.nl/ > https://frysker.nl/ > https://frisian.eu/ > > gpg: > https://keyserver.ubuntu.com/pks/lookup?search=eduard+drenth&fingerprint=on&op=index > ------------------------------ > *From:* Adam Retter <ad...@ex...> > *Sent:* Monday, November 4, 2024 11:57 PM > *To:* Craig Berry <cra...@ma...> > *Cc:* exi...@li... <exi...@li...> > *Subject:* Re: [Exist-open] Exist DB Community Changes > > Thanks for the email Craig. Whilst I am deeply surprised and upset about > what has happened, I am also sorry that it is effecting the eXist-db users > such as yourself that I have worked so hard for and care about. > > I appreciate you crunching and highlighting the numbers. For those who > appreciate stats, a couple more for you: > > 1. As you say commits aren't everything. I also produced the last 22 > consecutive releases of eXist-db. > Since 2017, of the 52 releases, I produced 75% of them. I did this unpaid. > My company Evolved Binary also at its own expense maintains a lot of the > technical infrastructure that is required to produce and publish releases > of eXist-db. > See - https://github.com/eXist-db/exist/releases > > 2. From your list of contributors. 8 of the other named people > contributing to eXist-db were directed by me and paid for solely by my > company Evolved Binary. There is also 1 more who was partially funded by my > company. Removing me from the eXist-db project will also remove those other > contributors too. > > 3. I undertook a 1 year solo project from 2017 to 2018 to fix locking and > data corruption issues. It's not perfect still, but it was much improved. > That code base is was what became eXist-db 5. > > https://evolvedbinary.com/technical-reports/exist-db/locking-and-cache-improvements/locking-and-cache-improvements-20180205.pdf > > https://evolvedbinary.com/technical-reports/exist-db/asymmetrical-locking/asymmetrical-locking-20180205.pdf > > 4. I migrated eXist-db through 3 major versions of Java. To Java 6, then > Java 8, and then again later to Java 17. I did this unpaid. > > 5. I migrated eXist-db's code base from SourceForge (and Subversion) to > GitHub (and Git), which is why we have a comprehensive and intact source > history and can still see who has done what and when. I did this unpaid. > Speaking of which, you can also download CSV files from the graphs of > contributors on GitHub going back to 2003 here - > https://github.com/eXist-db/exist/graphs/contributors. GitHub's own > graphs are quite revealing! > Out of sheer personal curiosity, I crunched some data myself. Considering > only the top four contributors (as I didn't have time to crunch all the > data available), I produced a little graph from the CSV data (attached). > One could perhaps make the argument hat I have been the core contributor > and maintainer of eXist-db since about 2015. > > Regards the future of eXist-db, I have some plans. Feel free to reach out > to me - ad...@ev.... > > > [image: Screenshot 2024-11-04 at 23.48.08.png] > > On Mon, 4 Nov 2024 at 09:59, Craig Berry via Exist-open < > exi...@li...> wrote: > > As someone who has had cordial and helpful interactions with both Adam and > with some of the eXist Solutions folks for several years, this state of > affairs really saddens me. As someone who maintains a project that depends > on eXist, it also really concerns me about the future of eXist. > > I've had the somewhat vague impression that Adam has done the lion's share > of the work to maintain eXist for quite some time, and I wanted to make > that impression less vague, so I did some digging. The git logs below show > that in the current develop branch the number of non-merge commits in the > last five years totals 3115, or 2261 after weeding out dependabot commits. > That's followed by a list showing the number of non-merge commits per > committer in descending order by commit count. > > With 1266 commits, Adam produced 56% of all the human-produced commits in > that period, 4.5 times as many as the next most-prolific human contributor. > I realize commit counts are somewhat of a rough-and-ready placeholder for > contribution and they surely overstate some things and understate others. > One of the things they understate is producing releases, and it seems like > Adam has done most of those in recent years too. > > I want to emphasize that I really appreciate the work of *all* the > contributors, and I'm merely pointing out that the already somewhat anemic > pace of eXist development appears to have taken a very serious blow given > that its one really prolific contributor is being locked out. Is there a > plan to address this? Should folks be looking for an alternative to eXist? > > % git describe > eXist-6.2.0-1595-ge8b4798931 > % git log --no-merges --pretty=format:"%an" --since=2019-11-01 | wc -l > 3115 > % git log --no-merges --pretty=format:"%an" --since=2019-11-01 \ > | perl -ne 'chomp; $au{$_}++; END {for my $x (sort { $au{$b} <=> $au{$a} } > keys %au ) {print qq/$au{$x}\t$x\n/}};' > 1266 Adam Retter > 638 dependabot[bot] > 277 Dannes Wessels > 253 Juri Leino > 216 dependabot-preview[bot] > 152 Alan Paxton > 69 Patrick Reinhart > 54 Christopher McGeorge > 27 Joe Wicentowski > 26 mamroure > 19 marmoure > 17 Radek Hubner > 17 duncdrum > 17 Gabriele Tomassetti > 16 Wolfgang Meier > 12 Adrian Hamm > 10 Duncan Paterson > 9 Lars Windauer > 6 Stanislav Jordanov > 5 Nico Verwer > 1 Stefan Hynek > 1 markhall82 > 1 lujie > 1 Otmar Humbel > 1 stephan makowski > 1 naveen > 1 hoijui > 1 ch...@ev... > 1 Alberto Simões > 1 Steven > > > > On Nov 2, 2024, at 6:11 AM, Adam Retter <ad...@ex...> wrote: > > > > > > For those that are interested in hearing the truth, please feel free to > contact me directly. Or if you wish you can read the public responses from > myself, and other eXist-db users and XML experts in the #community channel > of the eXist-db Slack Workspace - https://exist-db.slack.com/ > > > > > > > > On Wed, 30 Oct 2024 at 16:31, Duncan Paterson <dun...@gm...> > wrote: > > In an abstract for his presentation at the upcoming Declarative > Amsterdam conference, Adam Retter announced his decision to fork eXist-db > and launch a competing project. This action is commonplace in open source. > However, in justifying his decision, Adam maligned the eXist community and > project - in a strikingly unprofessional manner. > > > > On October 7 and 14, 2024 during the weekly Community Call, eXist-db’s > core developers and active community members discussed this matter and > unanimously concluded that we no longer have the necessary trust in Adam to > speak or act in the best interests of the eXist community. We have > therefore revoked his status as a core developer and his administrative > privileges from the eXist-db GitHub organization and related community > resources. We regret having to take these measures. But we believe that > they are vital to restoring the collegial and welcoming atmosphere that > marked the eXist-db community since its founding by Wolfgang Meier in 2001. > We thank Adam for all of his work on eXist-db and wish him well with his > new project. > > > > > > == Signatories == > > > > Dannes Wessels, > > Duncan Paterson, > > Joseph Wicentowski, > > Joern Turner, > > Juri Leino, > > Lars Windauer, > > Magdalena Turska, > > Olaf Schreck, > > Patrick Reinhart, > > Wolfgang Meier, (founder eXist-db) > > _______________________________________________ > > Exist-open mailing list > > Exi...@li... > > https://lists.sourceforge.net/lists/listinfo/exist-open > > > > > > -- > > Adam Retter > > > > eXist Core Developer > > { United Kingdom } > > ad...@ex... > > _______________________________________________ > > Exist-open 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 > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > > > -- > Adam Retter > > eXist Core Developer > { United Kingdom } > ad...@ex... > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Adam Retter eXist Core Developer { United Kingdom } ad...@ex... |
|
From: Eduard D. <ed...@fr...> - 2024-12-05 20:51:39
|
Dear all, For our institution this all strengthens the feeling we need to reconsider the use of exist-db, we already felt that need because of performance, old java versions and libs, long standing issues, one highly complex monolithic solution for both database and app development, no jakarta ee compatible war, no atomic transactions, poor support for multiuser editing, etc. I value Xml and exist-db a lot, don't get me wrong, but our institution needs to make future proof choices, and I wonder whether sticking with exist-db is a good choice in that respect. Regards, Eduard Eduard Drenth, Software Architekt ed...@fr... Doelestrjitte 8 8911 DX Ljouwert (058) 213 14 14 +31 62 094 34 28 https://www.fryske-akademy.nl/ https://frysker.nl/ https://frisian.eu/ [cid:8bc42473-0b2f-46ae-9cf4-53515937ae62] gpg: https://keyserver.ubuntu.com/pks/lookup?search=eduard+drenth&fingerprint=on&op=index ________________________________ From: Adam Retter <ad...@ex...> Sent: Monday, November 4, 2024 11:57 PM To: Craig Berry <cra...@ma...> Cc: exi...@li... <exi...@li...> Subject: Re: [Exist-open] Exist DB Community Changes Thanks for the email Craig. Whilst I am deeply surprised and upset about what has happened, I am also sorry that it is effecting the eXist-db users such as yourself that I have worked so hard for and care about. I appreciate you crunching and highlighting the numbers. For those who appreciate stats, a couple more for you: 1. As you say commits aren't everything. I also produced the last 22 consecutive releases of eXist-db. Since 2017, of the 52 releases, I produced 75% of them. I did this unpaid. My company Evolved Binary also at its own expense maintains a lot of the technical infrastructure that is required to produce and publish releases of eXist-db. See - https://github.com/eXist-db/exist/releases 2. From your list of contributors. 8 of the other named people contributing to eXist-db were directed by me and paid for solely by my company Evolved Binary. There is also 1 more who was partially funded by my company. Removing me from the eXist-db project will also remove those other contributors too. 3. I undertook a 1 year solo project from 2017 to 2018 to fix locking and data corruption issues. It's not perfect still, but it was much improved. That code base is was what became eXist-db 5. https://evolvedbinary.com/technical-reports/exist-db/locking-and-cache-improvements/locking-and-cache-improvements-20180205.pdf https://evolvedbinary.com/technical-reports/exist-db/asymmetrical-locking/asymmetrical-locking-20180205.pdf 4. I migrated eXist-db through 3 major versions of Java. To Java 6, then Java 8, and then again later to Java 17. I did this unpaid. 5. I migrated eXist-db's code base from SourceForge (and Subversion) to GitHub (and Git), which is why we have a comprehensive and intact source history and can still see who has done what and when. I did this unpaid. Speaking of which, you can also download CSV files from the graphs of contributors on GitHub going back to 2003 here - https://github.com/eXist-db/exist/graphs/contributors. GitHub's own graphs are quite revealing! Out of sheer personal curiosity, I crunched some data myself. Considering only the top four contributors (as I didn't have time to crunch all the data available), I produced a little graph from the CSV data (attached). One could perhaps make the argument hat I have been the core contributor and maintainer of eXist-db since about 2015. Regards the future of eXist-db, I have some plans. Feel free to reach out to me - ad...@ev...<mailto:ad...@ev...>. [Screenshot 2024-11-04 at 23.48.08.png] On Mon, 4 Nov 2024 at 09:59, Craig Berry via Exist-open <exi...@li...<mailto:exi...@li...>> wrote: As someone who has had cordial and helpful interactions with both Adam and with some of the eXist Solutions folks for several years, this state of affairs really saddens me. As someone who maintains a project that depends on eXist, it also really concerns me about the future of eXist. I've had the somewhat vague impression that Adam has done the lion's share of the work to maintain eXist for quite some time, and I wanted to make that impression less vague, so I did some digging. The git logs below show that in the current develop branch the number of non-merge commits in the last five years totals 3115, or 2261 after weeding out dependabot commits. That's followed by a list showing the number of non-merge commits per committer in descending order by commit count. With 1266 commits, Adam produced 56% of all the human-produced commits in that period, 4.5 times as many as the next most-prolific human contributor. I realize commit counts are somewhat of a rough-and-ready placeholder for contribution and they surely overstate some things and understate others. One of the things they understate is producing releases, and it seems like Adam has done most of those in recent years too. I want to emphasize that I really appreciate the work of *all* the contributors, and I'm merely pointing out that the already somewhat anemic pace of eXist development appears to have taken a very serious blow given that its one really prolific contributor is being locked out. Is there a plan to address this? Should folks be looking for an alternative to eXist? % git describe eXist-6.2.0-1595-ge8b4798931 % git log --no-merges --pretty=format:"%an" --since=2019-11-01 | wc -l 3115 % git log --no-merges --pretty=format:"%an" --since=2019-11-01 \ | perl -ne 'chomp; $au{$_}++; END {for my $x (sort { $au{$b} <=> $au{$a} } keys %au ) {print qq/$au{$x}\t$x\n/}};' 1266 Adam Retter 638 dependabot[bot] 277 Dannes Wessels 253 Juri Leino 216 dependabot-preview[bot] 152 Alan Paxton 69 Patrick Reinhart 54 Christopher McGeorge 27 Joe Wicentowski 26 mamroure 19 marmoure 17 Radek Hubner 17 duncdrum 17 Gabriele Tomassetti 16 Wolfgang Meier 12 Adrian Hamm 10 Duncan Paterson 9 Lars Windauer 6 Stanislav Jordanov 5 Nico Verwer 1 Stefan Hynek 1 markhall82 1 lujie 1 Otmar Humbel 1 stephan makowski 1 naveen 1 hoijui 1 ch...@ev...<mailto:ch...@ev...> 1 Alberto Simões 1 Steven > On Nov 2, 2024, at 6:11 AM, Adam Retter <ad...@ex...<mailto:ad...@ex...>> wrote: > > > For those that are interested in hearing the truth, please feel free to contact me directly. Or if you wish you can read the public responses from myself, and other eXist-db users and XML experts in the #community channel of the eXist-db Slack Workspace - https://exist-db.slack.com/ > > > > On Wed, 30 Oct 2024 at 16:31, Duncan Paterson <dun...@gm...<mailto:dun...@gm...>> wrote: > In an abstract for his presentation at the upcoming Declarative Amsterdam conference, Adam Retter announced his decision to fork eXist-db and launch a competing project. This action is commonplace in open source. However, in justifying his decision, Adam maligned the eXist community and project - in a strikingly unprofessional manner. > > On October 7 and 14, 2024 during the weekly Community Call, eXist-db’s core developers and active community members discussed this matter and unanimously concluded that we no longer have the necessary trust in Adam to speak or act in the best interests of the eXist community. We have therefore revoked his status as a core developer and his administrative privileges from the eXist-db GitHub organization and related community resources. We regret having to take these measures. But we believe that they are vital to restoring the collegial and welcoming atmosphere that marked the eXist-db community since its founding by Wolfgang Meier in 2001. We thank Adam for all of his work on eXist-db and wish him well with his new project. > > > == Signatories == > > Dannes Wessels, > Duncan Paterson, > Joseph Wicentowski, > Joern Turner, > Juri Leino, > Lars Windauer, > Magdalena Turska, > Olaf Schreck, > Patrick Reinhart, > Wolfgang Meier, (founder eXist-db) > _______________________________________________ > Exist-open mailing list > Exi...@li...<mailto:Exi...@li...> > https://lists.sourceforge.net/lists/listinfo/exist-open > > > -- > Adam Retter > > eXist Core Developer > { United Kingdom } > ad...@ex...<mailto:ad...@ex...> > _______________________________________________ > Exist-open mailing list > Exi...@li...<mailto: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 _______________________________________________ Exist-open mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open -- Adam Retter eXist Core Developer { United Kingdom } ad...@ex...<mailto:ad...@ex...> |
|
From: Irene V. <ire...@pa...> - 2024-12-03 10:25:02
|
Hi there! I am trying to add a custom Lucene analyzer that behaves like the WhitespaceAnalyzer concerning tokenization and (lack of) stemming, but that is also case-insensitive (basically the same of https://sourceforge.net/p/exist/mailman/message/35188378/). I followed what suggested in the post thread above, that is writing the custom analyzer, compiling its class as JAR and saving it in $EXIST_HOME/lib/user, but it is not working. I tried also putting it in the same folder of the other Lucene JAR files, but the same. Since both my Java/Lucene and eXist-db knowledge are quite poor, I am struggling to figure out whether the problem concerns my code or has to do with eXist-db itself. This is my custom analyzer code: package org.custom; import org.apache.lucene.analysis.Analyzer; import org.apache.lucene.analysis.TokenStream; import org.apache.lucene.analysis.core.LowerCaseFilter; import org.apache.lucene.analysis.core.WhitespaceTokenizer; public class CaseInsensitiveWhitespaceAnalyzer extends Analyzer { @Override protected TokenStreamComponents createComponents(String fieldName) { final WhitespaceTokenizer source = new WhitespaceTokenizer(); final TokenStream filter = new LowerCaseFilter(source); return new TokenStreamComponents(source, filter); } } And this is how I reference to it in collection.xconf: <analyzer id="custom" class="org.custom.CaseInsensitiveWhitespaceAnalyzer"/> I also tested the analyzer outside eXist-db with the following and it returned the expected tokens: import org.apache.lucene.analysis.Analyzer; import org.apache.lucene.analysis.TokenStream; import org.apache.lucene.analysis.tokenattributes.CharTermAttribute; import org.custom.CaseInsensitiveWhitespaceAnalyzer; import java.io.IOException; import java.io.StringReader; public class TestAnalyzer { public static void main(String[] args) throws IOException { String text = "Lucene is a Simple1 123 5% _test - Yet Powerful - Java Based Search Library. I love IT!"; Analyzer analyzer = new CaseInsensitiveWhitespaceAnalyzer(); try (TokenStream tokenStream = analyzer.tokenStream("field", new StringReader(text))) { CharTermAttribute charTermAttribute = tokenStream.addAttribute(CharTermAttribute.class); tokenStream.reset(); while (tokenStream.incrementToken()) { System.out.println(charTermAttribute.toString()); } tokenStream.end(); } } } What am I doing wrong? Any suggestions/hints will be highly appreciated :) Thanks, Irene |
|
From: Tony C. <t.c...@su...> - 2024-12-02 17:44:28
|
Thanks Joe and Jean-Paul As you’d expect things are now working exactly as I’d hoped. Tony From: Joe Wicentowski <jo...@gm...> Sent: 02 December 2024 17:16 To: Corless, Tony (Comp Sci & Elec Eng) <t.c...@su...> Cc: exi...@li... Subject: Re: [Exist-open] Help with file upload please. Hi Tony, Instead of the request:get-parameter function, use request:get-uploaded-file-data. See: https://exist-db.org/exist/apps/fundocs/view.html?uri=http://exist-db.org/xquery/request#get-uploaded-file-data.1 Joe On Mon, Dec 2, 2024 at 4:20 AM Tony Corless via Exist-open <exi...@li...<mailto:exi...@li...>> wrote: Hello all, I am getting something slightly wrong and I’m not sure what. This is still new to me, so likely I am making a silly error. I want to provide users with a form that allows them to upload PDF files from their PC to the database. The form will also have information about the PDF, which is working as expected. For a test I have two XQueries one to post the data and the other to save it: xquery version "3.1"; declare option exist:serialize "method=html media-type=text/html indent=no"; <html><body> <p>file upload test</p> <form method="post" enctype="multipart/form-data" action="./storeFile.xql"> <input type="file" id="myFile" name="posted"/> <input type="submit"/> </form> </body></html> and xquery version "3.1"; declare option exist:serialize "method=html media-type=text/html indent=no"; declare variable $received := request:get-parameter("posted",()); let $filePath :="/db/apps/scratch/data/files" let $fileName := "test.pdf" return <html><body>Received {($filePath, $fileName, xmldb:store-as-binary($filePath, $fileName, $received))}</body></html> The result is that I get a file test.pdf in the target directory but it displays only as blank pages. The same file uploaded through the admin client displays correctly. (I get the same result with a side range of PDF files. If I change to store a JPG then I get a blank image from the XQuery route and the expected image using the admin client.) I feel that I am missing something that is obvious and trivial to those who know what they are doing! Any input welcome. Tony _______________________________________________ Exist-open mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Joe W. <jo...@gm...> - 2024-12-02 17:16:05
|
Hi Tony, Instead of the request:get-parameter function, use request:get-uploaded-file-data. See: https://exist-db.org/exist/apps/fundocs/view.html?uri=http://exist-db.org/xquery/request#get-uploaded-file-data.1 Joe On Mon, Dec 2, 2024 at 4:20 AM Tony Corless via Exist-open < exi...@li...> wrote: > Hello all, > > > > I am getting something slightly wrong and I’m not sure what. This is still > new to me, so likely I am making a silly error. > > I want to provide users with a form that allows them to upload PDF files > from their PC to the database. The form will also have information about > the PDF, which is working as expected. > > > > For a test I have two XQueries one to post the data and the other to save > it: > > > > xquery version "3.1"; > > declare option exist:serialize "method=html media-type=text/html > indent=no"; > > <html><body> > > <p>file upload test</p> > > <form method="post" enctype="multipart/form-data" > action="./storeFile.xql"> > > <input type="file" id="myFile" name="posted"/> > > <input type="submit"/> > > </form> > > </body></html> > > > > > > and > > > > xquery version "3.1"; > > declare option exist:serialize "method=html media-type=text/html > indent=no"; > > declare variable $received := request:get-parameter("posted",()); > > let $filePath :="/db/apps/scratch/data/files" > > let $fileName := "test.pdf" > > return > > <html><body>Received {($filePath, $fileName, > xmldb:store-as-binary($filePath, $fileName, $received))}</body></html> > > > > The result is that I get a file test.pdf in the target directory but it > displays only as blank pages. The same file uploaded through the admin > client displays correctly. > > (I get the same result with a side range of PDF files. If I change to > store a JPG then I get a blank image from the XQuery route and the expected > image using the admin client.) > > > > I feel that I am missing something that is obvious and trivial to those > who know what they are doing! > > > > Any input welcome. > > Tony > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Jean-Paul R. <re...@gm...> - 2024-12-02 10:00:32
|
Dear Tony, It seems you are trying to access the uploaded file (jpg, pdf, etc) via request:get-parameter()....but the file is not a parameter to the request. You need to use request:get-uploaded-file-data() within the context of multipart/form-data. This function takes the name from the file you uploaded, *not from an input*. This is accessed with request:get-uploaded-file-name() See https://exist-db.org/exist/apps/fundocs/view.html?uri=http://exist-db.org/xquery/request&location=java:org.exist.xquery.functions.request.RequestModule JPR On Mon, Dec 2, 2024 at 10:20 AM Tony Corless via Exist-open < exi...@li...> wrote: > Hello all, > > > > I am getting something slightly wrong and I’m not sure what. This is still > new to me, so likely I am making a silly error. > > I want to provide users with a form that allows them to upload PDF files > from their PC to the database. The form will also have information about > the PDF, which is working as expected. > > > > For a test I have two XQueries one to post the data and the other to save > it: > > > > xquery version "3.1"; > > declare option exist:serialize "method=html media-type=text/html > indent=no"; > > <html><body> > > <p>file upload test</p> > > <form method="post" enctype="multipart/form-data" > action="./storeFile.xql"> > > <input type="file" id="myFile" name="posted"/> > > <input type="submit"/> > > </form> > > </body></html> > > > > > > and > > > > xquery version "3.1"; > > declare option exist:serialize "method=html media-type=text/html > indent=no"; > > declare variable $received := request:get-parameter("posted",()); > > let $filePath :="/db/apps/scratch/data/files" > > let $fileName := "test.pdf" > > return > > <html><body>Received {($filePath, $fileName, > xmldb:store-as-binary($filePath, $fileName, $received))}</body></html> > > > > The result is that I get a file test.pdf in the target directory but it > displays only as blank pages. The same file uploaded through the admin > client displays correctly. > > (I get the same result with a side range of PDF files. If I change to > store a JPG then I get a blank image from the XQuery route and the expected > image using the admin client.) > > > > I feel that I am missing something that is obvious and trivial to those > who know what they are doing! > > > > Any input welcome. > > Tony > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Tony C. <t.c...@su...> - 2024-12-01 19:24:11
|
Hello all,
I am getting something slightly wrong and I'm not sure what. This is still new to me, so likely I am making a silly error.
I want to provide users with a form that allows them to upload PDF files from their PC to the database. The form will also have information about the PDF, which is working as expected.
For a test I have two XQueries one to post the data and the other to save it:
xquery version "3.1";
declare option exist:serialize "method=html media-type=text/html indent=no";
<html><body>
<p>file upload test</p>
<form method="post" enctype="multipart/form-data" action="./storeFile.xql">
<input type="file" id="myFile" name="posted"/>
<input type="submit"/>
</form>
</body></html>
and
xquery version "3.1";
declare option exist:serialize "method=html media-type=text/html indent=no";
declare variable $received := request:get-parameter("posted",());
let $filePath :="/db/apps/scratch/data/files"
let $fileName := "test.pdf"
return
<html><body>Received {($filePath, $fileName, xmldb:store-as-binary($filePath, $fileName, $received))}</body></html>
The result is that I get a file test.pdf in the target directory but it displays only as blank pages. The same file uploaded through the admin client displays correctly.
(I get the same result with a side range of PDF files. If I change to store a JPG then I get a blank image from the XQuery route and the expected image using the admin client.)
I feel that I am missing something that is obvious and trivial to those who know what they are doing!
Any input welcome.
Tony
|
|
From: Adam R. <ad...@ex...> - 2024-11-04 23:28:41
|
Thanks for the email Craig. Whilst I am deeply surprised and upset about what has happened, I am also sorry that it is effecting the eXist-db users such as yourself that I have worked so hard for and care about. I appreciate you crunching and highlighting the numbers. For those who appreciate stats, a couple more for you: 1. As you say commits aren't everything. I also produced the last 22 consecutive releases of eXist-db. Since 2017, of the 52 releases, I produced 75% of them. I did this unpaid. My company Evolved Binary also at its own expense maintains a lot of the technical infrastructure that is required to produce and publish releases of eXist-db. See - https://github.com/eXist-db/exist/releases 2. From your list of contributors. 8 of the other named people contributing to eXist-db were directed by me and paid for solely by my company Evolved Binary. There is also 1 more who was partially funded by my company. Removing me from the eXist-db project will also remove those other contributors too. 3. I undertook a 1 year solo project from 2017 to 2018 to fix locking and data corruption issues. It's not perfect still, but it was much improved. That code base is was what became eXist-db 5. https://evolvedbinary.com/technical-reports/exist-db/locking-and-cache-improvements/locking-and-cache-improvements-20180205.pdf https://evolvedbinary.com/technical-reports/exist-db/asymmetrical-locking/asymmetrical-locking-20180205.pdf 4. I migrated eXist-db through 3 major versions of Java. To Java 6, then Java 8, and then again later to Java 17. I did this unpaid. 5. I migrated eXist-db's code base from SourceForge (and Subversion) to GitHub (and Git), which is why we have a comprehensive and intact source history and can still see who has done what and when. I did this unpaid. Speaking of which, you can also download CSV files from the graphs of contributors on GitHub going back to 2003 here - https://github.com/eXist-db/exist/graphs/contributors. GitHub's own graphs are quite revealing! Out of sheer personal curiosity, I crunched some data myself. Considering only the top four contributors (as I didn't have time to crunch all the data available), I produced a little graph from the CSV data (attached). One could perhaps make the argument hat I have been the core contributor and maintainer of eXist-db since about 2015. Regards the future of eXist-db, I have some plans. Feel free to reach out to me - ad...@ev.... [image: Screenshot 2024-11-04 at 23.48.08.png] On Mon, 4 Nov 2024 at 09:59, Craig Berry via Exist-open < exi...@li...> wrote: > As someone who has had cordial and helpful interactions with both Adam and > with some of the eXist Solutions folks for several years, this state of > affairs really saddens me. As someone who maintains a project that depends > on eXist, it also really concerns me about the future of eXist. > > I've had the somewhat vague impression that Adam has done the lion's share > of the work to maintain eXist for quite some time, and I wanted to make > that impression less vague, so I did some digging. The git logs below show > that in the current develop branch the number of non-merge commits in the > last five years totals 3115, or 2261 after weeding out dependabot commits. > That's followed by a list showing the number of non-merge commits per > committer in descending order by commit count. > > With 1266 commits, Adam produced 56% of all the human-produced commits in > that period, 4.5 times as many as the next most-prolific human contributor. > I realize commit counts are somewhat of a rough-and-ready placeholder for > contribution and they surely overstate some things and understate others. > One of the things they understate is producing releases, and it seems like > Adam has done most of those in recent years too. > > I want to emphasize that I really appreciate the work of *all* the > contributors, and I'm merely pointing out that the already somewhat anemic > pace of eXist development appears to have taken a very serious blow given > that its one really prolific contributor is being locked out. Is there a > plan to address this? Should folks be looking for an alternative to eXist? > > % git describe > eXist-6.2.0-1595-ge8b4798931 > % git log --no-merges --pretty=format:"%an" --since=2019-11-01 | wc -l > 3115 > % git log --no-merges --pretty=format:"%an" --since=2019-11-01 \ > | perl -ne 'chomp; $au{$_}++; END {for my $x (sort { $au{$b} <=> $au{$a} } > keys %au ) {print qq/$au{$x}\t$x\n/}};' > 1266 Adam Retter > 638 dependabot[bot] > 277 Dannes Wessels > 253 Juri Leino > 216 dependabot-preview[bot] > 152 Alan Paxton > 69 Patrick Reinhart > 54 Christopher McGeorge > 27 Joe Wicentowski > 26 mamroure > 19 marmoure > 17 Radek Hubner > 17 duncdrum > 17 Gabriele Tomassetti > 16 Wolfgang Meier > 12 Adrian Hamm > 10 Duncan Paterson > 9 Lars Windauer > 6 Stanislav Jordanov > 5 Nico Verwer > 1 Stefan Hynek > 1 markhall82 > 1 lujie > 1 Otmar Humbel > 1 stephan makowski > 1 naveen > 1 hoijui > 1 ch...@ev... > 1 Alberto Simões > 1 Steven > > > > On Nov 2, 2024, at 6:11 AM, Adam Retter <ad...@ex...> wrote: > > > > > > For those that are interested in hearing the truth, please feel free to > contact me directly. Or if you wish you can read the public responses from > myself, and other eXist-db users and XML experts in the #community channel > of the eXist-db Slack Workspace - https://exist-db.slack.com/ > > > > > > > > On Wed, 30 Oct 2024 at 16:31, Duncan Paterson <dun...@gm...> > wrote: > > In an abstract for his presentation at the upcoming Declarative > Amsterdam conference, Adam Retter announced his decision to fork eXist-db > and launch a competing project. This action is commonplace in open source. > However, in justifying his decision, Adam maligned the eXist community and > project - in a strikingly unprofessional manner. > > > > On October 7 and 14, 2024 during the weekly Community Call, eXist-db’s > core developers and active community members discussed this matter and > unanimously concluded that we no longer have the necessary trust in Adam to > speak or act in the best interests of the eXist community. We have > therefore revoked his status as a core developer and his administrative > privileges from the eXist-db GitHub organization and related community > resources. We regret having to take these measures. But we believe that > they are vital to restoring the collegial and welcoming atmosphere that > marked the eXist-db community since its founding by Wolfgang Meier in 2001. > We thank Adam for all of his work on eXist-db and wish him well with his > new project. > > > > > > == Signatories == > > > > Dannes Wessels, > > Duncan Paterson, > > Joseph Wicentowski, > > Joern Turner, > > Juri Leino, > > Lars Windauer, > > Magdalena Turska, > > Olaf Schreck, > > Patrick Reinhart, > > Wolfgang Meier, (founder eXist-db) > > _______________________________________________ > > Exist-open mailing list > > Exi...@li... > > https://lists.sourceforge.net/lists/listinfo/exist-open > > > > > > -- > > Adam Retter > > > > eXist Core Developer > > { United Kingdom } > > ad...@ex... > > _______________________________________________ > > Exist-open 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 > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Adam Retter eXist Core Developer { United Kingdom } ad...@ex... |
|
From: Craig B. <cra...@ma...> - 2024-11-03 23:59:58
|
As someone who has had cordial and helpful interactions with both Adam and with some of the eXist Solutions folks for several years, this state of affairs really saddens me. As someone who maintains a project that depends on eXist, it also really concerns me about the future of eXist.
I've had the somewhat vague impression that Adam has done the lion's share of the work to maintain eXist for quite some time, and I wanted to make that impression less vague, so I did some digging. The git logs below show that in the current develop branch the number of non-merge commits in the last five years totals 3115, or 2261 after weeding out dependabot commits. That's followed by a list showing the number of non-merge commits per committer in descending order by commit count.
With 1266 commits, Adam produced 56% of all the human-produced commits in that period, 4.5 times as many as the next most-prolific human contributor. I realize commit counts are somewhat of a rough-and-ready placeholder for contribution and they surely overstate some things and understate others. One of the things they understate is producing releases, and it seems like Adam has done most of those in recent years too.
I want to emphasize that I really appreciate the work of *all* the contributors, and I'm merely pointing out that the already somewhat anemic pace of eXist development appears to have taken a very serious blow given that its one really prolific contributor is being locked out. Is there a plan to address this? Should folks be looking for an alternative to eXist?
% git describe
eXist-6.2.0-1595-ge8b4798931
% git log --no-merges --pretty=format:"%an" --since=2019-11-01 | wc -l
3115
% git log --no-merges --pretty=format:"%an" --since=2019-11-01 \
| perl -ne 'chomp; $au{$_}++; END {for my $x (sort { $au{$b} <=> $au{$a} } keys %au ) {print qq/$au{$x}\t$x\n/}};'
1266 Adam Retter
638 dependabot[bot]
277 Dannes Wessels
253 Juri Leino
216 dependabot-preview[bot]
152 Alan Paxton
69 Patrick Reinhart
54 Christopher McGeorge
27 Joe Wicentowski
26 mamroure
19 marmoure
17 Radek Hubner
17 duncdrum
17 Gabriele Tomassetti
16 Wolfgang Meier
12 Adrian Hamm
10 Duncan Paterson
9 Lars Windauer
6 Stanislav Jordanov
5 Nico Verwer
1 Stefan Hynek
1 markhall82
1 lujie
1 Otmar Humbel
1 stephan makowski
1 naveen
1 hoijui
1 ch...@ev...
1 Alberto Simões
1 Steven
> On Nov 2, 2024, at 6:11 AM, Adam Retter <ad...@ex...> wrote:
>
>
> For those that are interested in hearing the truth, please feel free to contact me directly. Or if you wish you can read the public responses from myself, and other eXist-db users and XML experts in the #community channel of the eXist-db Slack Workspace - https://exist-db.slack.com/
>
>
>
> On Wed, 30 Oct 2024 at 16:31, Duncan Paterson <dun...@gm...> wrote:
> In an abstract for his presentation at the upcoming Declarative Amsterdam conference, Adam Retter announced his decision to fork eXist-db and launch a competing project. This action is commonplace in open source. However, in justifying his decision, Adam maligned the eXist community and project - in a strikingly unprofessional manner.
>
> On October 7 and 14, 2024 during the weekly Community Call, eXist-db’s core developers and active community members discussed this matter and unanimously concluded that we no longer have the necessary trust in Adam to speak or act in the best interests of the eXist community. We have therefore revoked his status as a core developer and his administrative privileges from the eXist-db GitHub organization and related community resources. We regret having to take these measures. But we believe that they are vital to restoring the collegial and welcoming atmosphere that marked the eXist-db community since its founding by Wolfgang Meier in 2001. We thank Adam for all of his work on eXist-db and wish him well with his new project.
>
>
> == Signatories ==
>
> Dannes Wessels,
> Duncan Paterson,
> Joseph Wicentowski,
> Joern Turner,
> Juri Leino,
> Lars Windauer,
> Magdalena Turska,
> Olaf Schreck,
> Patrick Reinhart,
> Wolfgang Meier, (founder eXist-db)
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
> --
> Adam Retter
>
> eXist Core Developer
> { United Kingdom }
> ad...@ex...
> _______________________________________________
> Exist-open 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: Adam R. <ad...@ex...> - 2024-11-02 11:19:47
|
For those that are interested in hearing the truth, please feel free to contact me directly. Or if you wish you can read the public responses from myself, and other eXist-db users and XML experts in the #community channel of the eXist-db Slack Workspace - https://exist-db.slack.com/ On Wed, 30 Oct 2024 at 16:31, Duncan Paterson <dun...@gm...> wrote: > In an abstract for his presentation at the upcoming Declarative Amsterdam > conference, Adam Retter announced his decision to fork eXist-db and launch > a competing project. This action is commonplace in open source. However, in > justifying his decision, Adam maligned the eXist community and project - in > a strikingly unprofessional manner. > > On October 7 and 14, 2024 during the weekly Community Call, eXist-db’s > core developers and active community members discussed this matter and > unanimously concluded that we no longer have the necessary trust in Adam to > speak or act in the best interests of the eXist community. We have > therefore revoked his status as a core developer and his administrative > privileges from the eXist-db GitHub organization and related community > resources. We regret having to take these measures. But we believe that > they are vital to restoring the collegial and welcoming atmosphere that > marked the eXist-db community since its founding by Wolfgang Meier in 2001. > We thank Adam for all of his work on eXist-db and wish him well with his > new project. > > > == Signatories == > > Dannes Wessels, > > Duncan Paterson, > > Joseph Wicentowski, > > Joern Turner, > > Juri Leino, > > Lars Windauer, > > Magdalena Turska, > > Olaf Schreck, > > Patrick Reinhart, > > Wolfgang Meier, (founder eXist-db) > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Adam Retter eXist Core Developer { United Kingdom } ad...@ex... |
602 messages has been excluded from this view by a project administrator.
