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
|
Oct
|
Nov
|
Dec
|
|
From: Michael W. <wes...@ja...> - 2020-11-21 09:48:51
|
Hi Nick,
Yes, the error mentioned is that you aren't looping through any elements,
but rather references to the documents under /db/temp (which as somebody
else pointed out, doesn't exist -- you placed the XML files under /db/tmp).
Once you get the collection correct, you need an XPath following the
collection. That is:
for $note in collection('/db/tmp')//note
return $note
That will get all of the <note/> tags from all of the documents, whether
the <note/> tag is the root or under the root as in your notes.xml example.
The next thing you need to be careful of is that the results will be a few
<note/> tags with no single root containing them. That result will be an
illegal XML document if you try to view with
localhost:8080/exist/rest/db/scripts/notes.xq. That is why I tend to wrap
the result in a root tag, such as with:
<notes>{
for $note in collection('/db/tmp')//note
return $note
}</notes>
Hope this helps.
Take care.
2020年11月21日(土) 17:50 Nicholas <sau...@gm...>:
> Thanks, Michael. Probably I'm making a silly error:
>
>
> https://stackoverflow.com/q/64941000/4531180
>
>
> with the FLWOR.
>
>
> -Nick
>
>
> On 11/18/20 11:36 PM, Michael Westbay wrote:
>
> Hi Nick,
>
> Yes, that was placed on my local version.
>
> If you only got "<notes/>" then that means that it didn't find any *note* element
> in the collection "/db/temp". The annotated script reads:
>
> xquery version "3.1"; (: XQuery version declaration for the
> XQuery processor :)
>
> let $notes := collection('/db/temp')/note (: Gather all
> <note>...</note> documents under the /db/temp collection/folder/directory
> in the database :)
>
> return <notes>{$notes}</notes> (: Output a <notes>...</notes> tag with
> the gathered <note>...</note> documents embedded in it :)
>
>
> Since you had nothing within the <notes/> tag, it found not
> <note>...</note> documents on your eXist instance.
>
> You should create a lot of <note>...</note> documents within a collection
> and see that result. Then output:
>
> return <notes>{$note/body}</notes>
>
>
> and see what happens.
>
> Take care.
>
>
> 2020年11月19日(木) 14:59 Nicholas <sau...@gm...>:
>
>> Hi Michael,
>>
>>
>> Browsing to:
>>
>>
>> http://localhost:8080/exist/rest/db/scripts/notes.xq
>>
>>
>> gives me:
>>
>> <notes/>
>>
>> with an xquery of:
>>
>> xquery version "3.1";
>>
>> let $notes := collection('/db/temp')/note
>>
>> return <notes>{$notes}</notes>
>>
>> and a "note" file:
>>
>> <note>
>> <to>Tove</to>
>> <from>Jani</from>
>> <heading>Reminder</heading>
>> <body>Don't forget me this weekend!</body>
>> </note>
>>
>>
>> anyhow, that's enough output to get me rolling, so thanks. I think it's
>> just a mix-up there with plural/singular. Everything is on localhost.
>> Most interesting!
>>
>>
>> thanks,
>>
>>
>> Nick
>>
>>
>>
>> On 11/18/20 7:10 PM, Michael Westbay wrote:
>>
>> Hi Nick,
>>
>> First of all, XML files are NOT stored on the file system. The non-XML
>> files that do get stored there should NEVER be accessed outside of eXist as
>> that will throw the database's internal idea of what is in the database off.
>>
>> Within eXide, go to the "File" menu and select "Manage." this will let
>> you explore the database's internal file system to see where it is you
>> placed the XML file. Please make a note of the full path to where you
>> placed your <note> document.
>>
>> Next, create a new XQuery document. I placed your sample note under the
>> '/db/temp' *collection* (a collection corresponds to a folder in the
>> file hierarchy). If you enter a lot of these <note/> documents into the
>> same collection, you can get a list of them with:
>>
>> xquery version "3.1";
>>
>> let $notes := collection('/db/temp')/note
>>
>> return <notes>{$notes}</notes>
>>
>>
>> I only have the one <note> document, so my output is:
>>
>> [image: image.png]
>>
>>
>> You can then save the XQuery document to somewhere like
>> "/db/scripts/notes.xq" and access it at:
>>
>> localhost:8080/exist/rest/db/scripts.notes.xq
>>
>>
>> Hope this helps get you started.
>>
>> Take care.
>>
>>
>> 2020年11月19日(木) 11:50 Nicholas <sau...@gm...>:
>>
>>> I created a simple document through eXide on localhost:
>>>
>>> https://unix.stackexchange.com/q/620383/101935
>>>
>>> but can't seem to find the actual file. The content is from a sample:
>>>
>>> https://www.w3schools.com/xml/note.xml
>>>
>>> and I just wanted to store "in" eXist for query.
>>>
>>>
>>> thanks,
>>>
>>> Nick
>>>
>>>
>>> On 11/18/20 5:37 PM, Alasdair Dougall wrote:
>>> > Hi Nicholas,
>>> >
>>> > As Michael said in his reply, a problem to solve is the way to go.
>>> Another source of information is a book called eXist written by Erik Siegel
>>> and Adam Ritter. It will give you details of eXist.
>>> >
>>> > Alasdair
>>> >
>>> > Sent from my iPad
>>> >
>>> >> On 19 Nov 2020, at 9:56 am, Nicholas <sau...@gm...>
>>> wrote:
>>> >>
>>> >> I'm just looking for a simple starting point. I don't necessarily
>>> need a GUI, or web app, etc. Just looking to put an XML document into
>>> eXist and run a few XQuery's against it. Any pointers?
>>> >>
>>> >>
>>> >> thanks,
>>> >>
>>> >> Nick
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> 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
>>>
>>
>>
>> --
>> Michael Westbay
>> Writer/System Administrator
>> http://www.japanesebaseball.com/
>>
>>
>
> --
> Michael Westbay
> Writer/System Administrator
> http://www.japanesebaseball.com/
>
>
--
Michael Westbay
Writer/System Administrator
http://www.japanesebaseball.com/
|
|
From: Nicholas <sau...@gm...> - 2020-11-21 08:50:59
|
Thanks, Michael. Probably I'm making a silly error: https://stackoverflow.com/q/64941000/4531180 with the FLWOR. -Nick On 11/18/20 11:36 PM, Michael Westbay wrote: > Hi Nick, > > Yes, that was placed on my local version. > > If you only got "<notes/>" then that means that it didn't find any > *note* element in the collection "/db/temp". The annotated script reads: > > xquery version "3.1"; (: XQuery version declaration for > the XQuery processor :) > > let $notes := collection('/db/temp')/note (: Gather all > <note>...</note> documents under the /db/temp > collection/folder/directory in the database :) > > return <notes>{$notes}</notes> (: Output a <notes>...</notes> > tag with the gathered <note>...</note> documents embedded in it :) > > > Since you had nothing within the <notes/> tag, it found not > <note>...</note> documents on your eXist instance. > > You should create a lot of <note>...</note> documents within a > collection and see that result. Then output: > > return <notes>{$note/body}</notes> > > > and see what happens. > > Take care. > > > 2020年11月19日(木) 14:59 Nicholas <sau...@gm... > <mailto:sau...@gm...>>: > > Hi Michael, > > > Browsing to: > > > http://localhost:8080/exist/rest/db/scripts/notes.xq > > > gives me: > > <notes/> > > with an xquery of: > > xquery version "3.1"; > > let $notes := collection('/db/temp')/note > > return <notes>{$notes}</notes> > > and a "note" file: > > <note> > <to>Tove</to> > <from>Jani</from> > <heading>Reminder</heading> > <body>Don't forget me this weekend!</body> > </note> > > > anyhow, that's enough output to get me rolling, so thanks. I > think it's just a mix-up there with plural/singular. Everything > is on localhost. Most interesting! > > > thanks, > > > Nick > > > > On 11/18/20 7:10 PM, Michael Westbay wrote: >> Hi Nick, >> >> First of all, XML files are NOT stored on the file system. The >> non-XML files that do get stored there should NEVER be accessed >> outside of eXist as that will throw the database's internal idea >> of what is in the database off. >> >> Within eXide, go to the "File" menu and select "Manage." this >> will let you explore the database's internal file system to see >> where it is you placed the XML file. Please make a note of the >> full path to where you placed your <note> document. >> >> Next, create a new XQuery document. I placed your sample note >> under the '/db/temp' *collection* (a collection corresponds to a >> folder in the file hierarchy). If you enter a lot of these >> <note/> documents into the same collection, you can get a list of >> them with: >> >> xquery version "3.1"; >> >> let $notes := collection('/db/temp')/note >> >> return <notes>{$notes}</notes> >> >> >> I only have the one <note> document, so my output is: >> >> image.png >> >> >> You can then save the XQuery document to somewhere like >> "/db/scripts/notes.xq" and access it at: >> >> localhost:8080/exist/rest/db/scripts.notes.xq >> >> >> Hope this helps get you started. >> >> Take care. >> >> >> 2020年11月19日(木) 11:50 Nicholas <sau...@gm... >> <mailto:sau...@gm...>>: >> >> I created a simple document through eXide on localhost: >> >> https://unix.stackexchange.com/q/620383/101935 >> >> but can't seem to find the actual file. The content is from >> a sample: >> >> https://www.w3schools.com/xml/note.xml >> >> and I just wanted to store "in" eXist for query. >> >> >> thanks, >> >> Nick >> >> >> On 11/18/20 5:37 PM, Alasdair Dougall wrote: >> > Hi Nicholas, >> > >> > As Michael said in his reply, a problem to solve is the way >> to go. Another source of information is a book called eXist >> written by Erik Siegel and Adam Ritter. It will give you >> details of eXist. >> > >> > Alasdair >> > >> > Sent from my iPad >> > >> >> On 19 Nov 2020, at 9:56 am, Nicholas >> <sau...@gm... >> <mailto:sau...@gm...>> wrote: >> >> >> >> I'm just looking for a simple starting point. I don't >> necessarily need a GUI, or web app, etc. Just looking to put >> an XML document into eXist and run a few XQuery's against >> it. Any pointers? >> >> >> >> >> >> thanks, >> >> >> >> Nick >> >> >> >> >> >> >> >> _______________________________________________ >> >> Exist-open mailing list >> >> Exi...@li... >> <mailto:Exi...@li...> >> >> https://lists.sourceforge.net/lists/listinfo/exist-open >> >> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> <mailto:Exi...@li...> >> https://lists.sourceforge.net/lists/listinfo/exist-open >> >> >> >> -- >> Michael Westbay >> Writer/System Administrator >> http://www.japanesebaseball.com/ > > > > -- > Michael Westbay > Writer/System Administrator > http://www.japanesebaseball.com/ |
|
From: Nicholas <sau...@gm...> - 2020-11-21 07:27:15
|
Looking at docker hub, the official image documentation says: This repository will be archived soon. Images will continue to be available via DockerHub under the old address, but the build will move to eXist-db's core repo. what are the implications to this decision? And, why was it made? thanks, Nick |
|
From: Martin M. <mar...@no...> - 2020-11-20 23:10:18
|
That’s good news. How about putting sketches of the revisions up somewhere as comments on particular pages. It might not slow you down, help some users immediately, and get some user feedback on progress. From: Adam Retter <ad...@ex...> Date: Friday, November 20, 2020 at 11:56 AM To: Martin Mueller <mar...@no...> Cc: "exi...@li..." <exi...@li...> Subject: Re: [Exist-open] A TEI Publisher postscript to the eXist book? Erik and I were able to secure the IP from O'Reilly. We are considering working on a second revision. On Thu, 19 Nov 2020, 17:26 Martin Mueller, <mar...@no...<mailto:mar...@no...>> wrote: I think it would be very helpful to the not-so-technical-savvy eXist users, if some expert took the time to write an addition to the Retter and Siegel book. It would make for a short and very useful TEI Publisher document. I would envisage it as a very targeted set of note that point directly to sections or pages in that book that are no longer up-to-date. Martin Mueller Professor emeritus of English and Classics Northwestern University _______________________________________________ Exist-open mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open<https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/exist-open__;!!Dq0X2DkFhyF93HkjWTBQKhk!D9pT8lr2m1qiPyQ0_hYMkGONMDGzMnbOfqnmRXrj3JUziNjHHo8LXGMquV9-8QcJMxcpHcKldw$> |
|
From: Adam R. <ad...@ex...> - 2020-11-20 18:49:16
|
Erik and I were able to secure the IP from O'Reilly. We are considering working on a second revision. On Thu, 19 Nov 2020, 17:26 Martin Mueller, <mar...@no...> wrote: > > I think it would be very helpful to the not-so-technical-savvy eXist > users, if some expert took the time to write an addition to the Retter and > Siegel book. It would make for a short and very useful TEI Publisher > document. I would envisage it as a very targeted set of note that point > directly to sections or pages in that book that are no longer up-to-date. > > Martin Mueller > Professor emeritus of English and Classics > Northwestern University > > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Martin M. <mar...@no...> - 2020-11-19 16:24:35
|
I think it would be very helpful to the not-so-technical-savvy eXist users, if some expert took the time to write an addition to the Retter and Siegel book. It would make for a short and very useful TEI Publisher document. I would envisage it as a very targeted set of note that point directly to sections or pages in that book that are no longer up-to-date. Martin Mueller Professor emeritus of English and Classics Northwestern University |
|
From: Michael W. <wes...@ja...> - 2020-11-19 07:36:55
|
Hi Nick,
Yes, that was placed on my local version.
If you only got "<notes/>" then that means that it didn't find any
*note* element
in the collection "/db/temp". The annotated script reads:
xquery version "3.1"; (: XQuery version declaration for the
XQuery processor :)
let $notes := collection('/db/temp')/note (: Gather all <note>...</note>
documents under the /db/temp collection/folder/directory in the database :)
return <notes>{$notes}</notes> (: Output a <notes>...</notes> tag with
the gathered <note>...</note> documents embedded in it :)
Since you had nothing within the <notes/> tag, it found not
<note>...</note> documents on your eXist instance.
You should create a lot of <note>...</note> documents within a collection
and see that result. Then output:
return <notes>{$note/body}</notes>
and see what happens.
Take care.
2020年11月19日(木) 14:59 Nicholas <sau...@gm...>:
> Hi Michael,
>
>
> Browsing to:
>
>
> http://localhost:8080/exist/rest/db/scripts/notes.xq
>
>
> gives me:
>
> <notes/>
>
> with an xquery of:
>
> xquery version "3.1";
>
> let $notes := collection('/db/temp')/note
>
> return <notes>{$notes}</notes>
>
> and a "note" file:
>
> <note>
> <to>Tove</to>
> <from>Jani</from>
> <heading>Reminder</heading>
> <body>Don't forget me this weekend!</body>
> </note>
>
>
> anyhow, that's enough output to get me rolling, so thanks. I think it's
> just a mix-up there with plural/singular. Everything is on localhost.
> Most interesting!
>
>
> thanks,
>
>
> Nick
>
>
>
> On 11/18/20 7:10 PM, Michael Westbay wrote:
>
> Hi Nick,
>
> First of all, XML files are NOT stored on the file system. The non-XML
> files that do get stored there should NEVER be accessed outside of eXist as
> that will throw the database's internal idea of what is in the database off.
>
> Within eXide, go to the "File" menu and select "Manage." this will let you
> explore the database's internal file system to see where it is you placed
> the XML file. Please make a note of the full path to where you placed your
> <note> document.
>
> Next, create a new XQuery document. I placed your sample note under the
> '/db/temp' *collection* (a collection corresponds to a folder in the file
> hierarchy). If you enter a lot of these <note/> documents into the same
> collection, you can get a list of them with:
>
> xquery version "3.1";
>
> let $notes := collection('/db/temp')/note
>
> return <notes>{$notes}</notes>
>
>
> I only have the one <note> document, so my output is:
>
> [image: image.png]
>
>
> You can then save the XQuery document to somewhere like
> "/db/scripts/notes.xq" and access it at:
>
> localhost:8080/exist/rest/db/scripts.notes.xq
>
>
> Hope this helps get you started.
>
> Take care.
>
>
> 2020年11月19日(木) 11:50 Nicholas <sau...@gm...>:
>
>> I created a simple document through eXide on localhost:
>>
>> https://unix.stackexchange.com/q/620383/101935
>>
>> but can't seem to find the actual file. The content is from a sample:
>>
>> https://www.w3schools.com/xml/note.xml
>>
>> and I just wanted to store "in" eXist for query.
>>
>>
>> thanks,
>>
>> Nick
>>
>>
>> On 11/18/20 5:37 PM, Alasdair Dougall wrote:
>> > Hi Nicholas,
>> >
>> > As Michael said in his reply, a problem to solve is the way to go.
>> Another source of information is a book called eXist written by Erik Siegel
>> and Adam Ritter. It will give you details of eXist.
>> >
>> > Alasdair
>> >
>> > Sent from my iPad
>> >
>> >> On 19 Nov 2020, at 9:56 am, Nicholas <sau...@gm...>
>> wrote:
>> >>
>> >> I'm just looking for a simple starting point. I don't necessarily
>> need a GUI, or web app, etc. Just looking to put an XML document into
>> eXist and run a few XQuery's against it. Any pointers?
>> >>
>> >>
>> >> thanks,
>> >>
>> >> Nick
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> 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
>>
>
>
> --
> Michael Westbay
> Writer/System Administrator
> http://www.japanesebaseball.com/
>
>
--
Michael Westbay
Writer/System Administrator
http://www.japanesebaseball.com/
|
|
From: Nicholas <sau...@gm...> - 2020-11-19 05:59:54
|
Hi Michael,
Browsing to:
http://localhost:8080/exist/rest/db/scripts/notes.xq
gives me:
<notes/>
with an xquery of:
xquery version "3.1";
let $notes := collection('/db/temp')/note
return <notes>{$notes}</notes>
and a "note" file:
<note>
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Don't forget me this weekend!</body>
</note>
anyhow, that's enough output to get me rolling, so thanks. I think it's
just a mix-up there with plural/singular. Everything is on localhost.
Most interesting!
thanks,
Nick
On 11/18/20 7:10 PM, Michael Westbay wrote:
> Hi Nick,
>
> First of all, XML files are NOT stored on the file system. The non-XML
> files that do get stored there should NEVER be accessed outside of
> eXist as that will throw the database's internal idea of what is in
> the database off.
>
> Within eXide, go to the "File" menu and select "Manage." this will let
> you explore the database's internal file system to see where it is you
> placed the XML file. Please make a note of the full path to where you
> placed your <note> document.
>
> Next, create a new XQuery document. I placed your sample note under
> the '/db/temp' *collection* (a collection corresponds to a folder in
> the file hierarchy). If you enter a lot of these <note/> documents
> into the same collection, you can get a list of them with:
>
> xquery version "3.1";
>
> let $notes := collection('/db/temp')/note
>
> return <notes>{$notes}</notes>
>
>
> I only have the one <note> document, so my output is:
>
> image.png
>
>
> You can then save the XQuery document to somewhere like
> "/db/scripts/notes.xq" and access it at:
>
> localhost:8080/exist/rest/db/scripts.notes.xq
>
>
> Hope this helps get you started.
>
> Take care.
>
>
> 2020年11月19日(木) 11:50 Nicholas <sau...@gm...
> <mailto:sau...@gm...>>:
>
> I created a simple document through eXide on localhost:
>
> https://unix.stackexchange.com/q/620383/101935
>
> but can't seem to find the actual file. The content is from a sample:
>
> https://www.w3schools.com/xml/note.xml
>
> and I just wanted to store "in" eXist for query.
>
>
> thanks,
>
> Nick
>
>
> On 11/18/20 5:37 PM, Alasdair Dougall wrote:
> > Hi Nicholas,
> >
> > As Michael said in his reply, a problem to solve is the way to
> go. Another source of information is a book called eXist written
> by Erik Siegel and Adam Ritter. It will give you details of eXist.
> >
> > Alasdair
> >
> > Sent from my iPad
> >
> >> On 19 Nov 2020, at 9:56 am, Nicholas
> <sau...@gm... <mailto:sau...@gm...>>
> wrote:
> >>
> >> I'm just looking for a simple starting point. I don't
> necessarily need a GUI, or web app, etc. Just looking to put an
> XML document into eXist and run a few XQuery's against it. Any
> pointers?
> >>
> >>
> >> thanks,
> >>
> >> Nick
> >>
> >>
> >>
> >> _______________________________________________
> >> Exist-open mailing list
> >> Exi...@li...
> <mailto:Exi...@li...>
> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> <mailto:Exi...@li...>
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
>
> --
> Michael Westbay
> Writer/System Administrator
> http://www.japanesebaseball.com/
|
|
From: Nicholas <sau...@gm...> - 2020-11-19 05:43:44
|
Hi Michael, where you write that you've "placed" the sample note, do you mean on your own database? Or, do you mean: https://www.exist-db.org/exist/apps/eXide/index.html which looks to be a demo app. Either is fine. On my local machine, I'm not seeing this specific collection in localhost, but then happened on the above, I think, demo of eXist. Just curious. thanks, Nick On 11/18/20 7:10 PM, Michael Westbay wrote: > Hi Nick, > > First of all, XML files are NOT stored on the file system. The non-XML > files that do get stored there should NEVER be accessed outside of > eXist as that will throw the database's internal idea of what is in > the database off. > > Within eXide, go to the "File" menu and select "Manage." this will let > you explore the database's internal file system to see where it is you > placed the XML file. Please make a note of the full path to where you > placed your <note> document. > > Next, create a new XQuery document. I placed your sample note under > the '/db/temp' *collection* (a collection corresponds to a folder in > the file hierarchy). If you enter a lot of these <note/> documents > into the same collection, you can get a list of them with: > > xquery version "3.1"; > > let $notes := collection('/db/temp')/note > > return <notes>{$notes}</notes> > > > I only have the one <note> document, so my output is: > > image.png > > > You can then save the XQuery document to somewhere like > "/db/scripts/notes.xq" and access it at: > > localhost:8080/exist/rest/db/scripts.notes.xq > > > Hope this helps get you started. > > Take care. > > > 2020年11月19日(木) 11:50 Nicholas <sau...@gm... > <mailto:sau...@gm...>>: > > I created a simple document through eXide on localhost: > > https://unix.stackexchange.com/q/620383/101935 > > but can't seem to find the actual file. The content is from a sample: > > https://www.w3schools.com/xml/note.xml > > and I just wanted to store "in" eXist for query. > > > thanks, > > Nick > > > On 11/18/20 5:37 PM, Alasdair Dougall wrote: > > Hi Nicholas, > > > > As Michael said in his reply, a problem to solve is the way to > go. Another source of information is a book called eXist written > by Erik Siegel and Adam Ritter. It will give you details of eXist. > > > > Alasdair > > > > Sent from my iPad > > > >> On 19 Nov 2020, at 9:56 am, Nicholas > <sau...@gm... <mailto:sau...@gm...>> > wrote: > >> > >> I'm just looking for a simple starting point. I don't > necessarily need a GUI, or web app, etc. Just looking to put an > XML document into eXist and run a few XQuery's against it. Any > pointers? > >> > >> > >> thanks, > >> > >> Nick > >> > >> > >> > >> _______________________________________________ > >> Exist-open mailing list > >> Exi...@li... > <mailto:Exi...@li...> > >> https://lists.sourceforge.net/lists/listinfo/exist-open > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > <mailto:Exi...@li...> > https://lists.sourceforge.net/lists/listinfo/exist-open > > > > -- > Michael Westbay > Writer/System Administrator > http://www.japanesebaseball.com/ |
|
From: Michael W. <wes...@ja...> - 2020-11-19 04:53:31
|
Hi Martin, Yes, the Retter and Siegel book is still very much relevant. The book covers up to XQuery 3.0. The current version of eXist supports XQuery 3.1, so there are some additional functionality that you can discover in the included documentation. I also believe that support for XForms (or maybe "betterForms"?) has gone away -- but it's a functionality I had never used, so am not completely sure. Also, I've only used the XQuery Update extension rather than XUpdate, so can confirm that XQuery Update still works fine. Finally, I believe that there has recently been a major shift in app packages. If you plan on developing a package for eXist, you may need to go through the excellent eXist documentation rather than the eXist book for what has changed. But building a package is something you probably won't be doing right away. Hope this helps. Take care. 2020年11月19日(木) 13:33 Martin Mueller <mar...@no...>: > Is reading Retter and Siegel still the best way of finding out about eXist > of have changes been so pervasive that it no longer quite works? It > would be useful to have some guide on what one can still rely on and where > one needs to tread more carefully. > > On 11/18/20, 8:50 PM, "Nicholas" <sau...@gm...> wrote: > > I created a simple document through eXide on localhost: > > > https://urldefense.com/v3/__https://unix.stackexchange.com/q/620383/101935__;!!Dq0X2DkFhyF93HkjWTBQKhk!AY2BmgFIqwVsIdssaMtx1h4DJtu5iltQMmya_3OoHTBEbOTRKsOUoyHgsotVsiIegW-_vCphXw$ > > but can't seem to find the actual file. The content is from a sample: > > > https://urldefense.com/v3/__https://www.w3schools.com/xml/note.xml__;!!Dq0X2DkFhyF93HkjWTBQKhk!AY2BmgFIqwVsIdssaMtx1h4DJtu5iltQMmya_3OoHTBEbOTRKsOUoyHgsotVsiIegW_J3iXj5Q$ > > and I just wanted to store "in" eXist for query. > > > thanks, > > Nick > > > On 11/18/20 5:37 PM, Alasdair Dougall wrote: > > Hi Nicholas, > > > > As Michael said in his reply, a problem to solve is the way to go. > Another source of information is a book called eXist written by Erik Siegel > and Adam Ritter. It will give you details of eXist. > > > > Alasdair > > > > Sent from my iPad > > > >> On 19 Nov 2020, at 9:56 am, Nicholas <sau...@gm...> > wrote: > >> > >> I'm just looking for a simple starting point. I don't necessarily > need a GUI, or web app, etc. Just looking to put an XML document into > eXist and run a few XQuery's against it. Any pointers? > >> > >> > >> thanks, > >> > >> Nick > >> > >> > >> > >> _______________________________________________ > >> Exist-open mailing list > >> Exi...@li... > >> > https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/exist-open__;!!Dq0X2DkFhyF93HkjWTBQKhk!AY2BmgFIqwVsIdssaMtx1h4DJtu5iltQMmya_3OoHTBEbOTRKsOUoyHgsotVsiIegW8XWq9Ksw$ > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > > https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/exist-open__;!!Dq0X2DkFhyF93HkjWTBQKhk!AY2BmgFIqwVsIdssaMtx1h4DJtu5iltQMmya_3OoHTBEbOTRKsOUoyHgsotVsiIegW8XWq9Ksw$ > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Michael Westbay Writer/System Administrator http://www.japanesebaseball.com/ |
|
From: Martin M. <mar...@no...> - 2020-11-19 04:32:49
|
Is reading Retter and Siegel still the best way of finding out about eXist of have changes been so pervasive that it no longer quite works? It would be useful to have some guide on what one can still rely on and where one needs to tread more carefully.
On 11/18/20, 8:50 PM, "Nicholas" <sau...@gm...> wrote:
I created a simple document through eXide on localhost:
https://urldefense.com/v3/__https://unix.stackexchange.com/q/620383/101935__;!!Dq0X2DkFhyF93HkjWTBQKhk!AY2BmgFIqwVsIdssaMtx1h4DJtu5iltQMmya_3OoHTBEbOTRKsOUoyHgsotVsiIegW-_vCphXw$
but can't seem to find the actual file. The content is from a sample:
https://urldefense.com/v3/__https://www.w3schools.com/xml/note.xml__;!!Dq0X2DkFhyF93HkjWTBQKhk!AY2BmgFIqwVsIdssaMtx1h4DJtu5iltQMmya_3OoHTBEbOTRKsOUoyHgsotVsiIegW_J3iXj5Q$
and I just wanted to store "in" eXist for query.
thanks,
Nick
On 11/18/20 5:37 PM, Alasdair Dougall wrote:
> Hi Nicholas,
>
> As Michael said in his reply, a problem to solve is the way to go. Another source of information is a book called eXist written by Erik Siegel and Adam Ritter. It will give you details of eXist.
>
> Alasdair
>
> Sent from my iPad
>
>> On 19 Nov 2020, at 9:56 am, Nicholas <sau...@gm...> wrote:
>>
>> I'm just looking for a simple starting point. I don't necessarily need a GUI, or web app, etc. Just looking to put an XML document into eXist and run a few XQuery's against it. Any pointers?
>>
>>
>> thanks,
>>
>> Nick
>>
>>
>>
>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/exist-open__;!!Dq0X2DkFhyF93HkjWTBQKhk!AY2BmgFIqwVsIdssaMtx1h4DJtu5iltQMmya_3OoHTBEbOTRKsOUoyHgsotVsiIegW8XWq9Ksw$
_______________________________________________
Exist-open mailing list
Exi...@li...
https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/exist-open__;!!Dq0X2DkFhyF93HkjWTBQKhk!AY2BmgFIqwVsIdssaMtx1h4DJtu5iltQMmya_3OoHTBEbOTRKsOUoyHgsotVsiIegW8XWq9Ksw$
|
|
From: Michael W. <wes...@ja...> - 2020-11-19 03:11:10
|
Hi Nick,
First of all, XML files are NOT stored on the file system. The non-XML
files that do get stored there should NEVER be accessed outside of eXist as
that will throw the database's internal idea of what is in the database off.
Within eXide, go to the "File" menu and select "Manage." this will let you
explore the database's internal file system to see where it is you placed
the XML file. Please make a note of the full path to where you placed your
<note> document.
Next, create a new XQuery document. I placed your sample note under the
'/db/temp' *collection* (a collection corresponds to a folder in the file
hierarchy). If you enter a lot of these <note/> documents into the same
collection, you can get a list of them with:
xquery version "3.1";
let $notes := collection('/db/temp')/note
return <notes>{$notes}</notes>
I only have the one <note> document, so my output is:
[image: image.png]
You can then save the XQuery document to somewhere like
"/db/scripts/notes.xq" and access it at:
localhost:8080/exist/rest/db/scripts.notes.xq
Hope this helps get you started.
Take care.
2020年11月19日(木) 11:50 Nicholas <sau...@gm...>:
> I created a simple document through eXide on localhost:
>
> https://unix.stackexchange.com/q/620383/101935
>
> but can't seem to find the actual file. The content is from a sample:
>
> https://www.w3schools.com/xml/note.xml
>
> and I just wanted to store "in" eXist for query.
>
>
> thanks,
>
> Nick
>
>
> On 11/18/20 5:37 PM, Alasdair Dougall wrote:
> > Hi Nicholas,
> >
> > As Michael said in his reply, a problem to solve is the way to go.
> Another source of information is a book called eXist written by Erik Siegel
> and Adam Ritter. It will give you details of eXist.
> >
> > Alasdair
> >
> > Sent from my iPad
> >
> >> On 19 Nov 2020, at 9:56 am, Nicholas <sau...@gm...>
> wrote:
> >>
> >> I'm just looking for a simple starting point. I don't necessarily
> need a GUI, or web app, etc. Just looking to put an XML document into
> eXist and run a few XQuery's against it. Any pointers?
> >>
> >>
> >> thanks,
> >>
> >> Nick
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
>
--
Michael Westbay
Writer/System Administrator
http://www.japanesebaseball.com/
|
|
From: Nicholas <sau...@gm...> - 2020-11-19 02:49:52
|
I created a simple document through eXide on localhost: https://unix.stackexchange.com/q/620383/101935 but can't seem to find the actual file. The content is from a sample: https://www.w3schools.com/xml/note.xml and I just wanted to store "in" eXist for query. thanks, Nick On 11/18/20 5:37 PM, Alasdair Dougall wrote: > Hi Nicholas, > > As Michael said in his reply, a problem to solve is the way to go. Another source of information is a book called eXist written by Erik Siegel and Adam Ritter. It will give you details of eXist. > > Alasdair > > Sent from my iPad > >> On 19 Nov 2020, at 9:56 am, Nicholas <sau...@gm...> wrote: >> >> I'm just looking for a simple starting point. I don't necessarily need a GUI, or web app, etc. Just looking to put an XML document into eXist and run a few XQuery's against it. Any pointers? >> >> >> thanks, >> >> Nick >> >> >> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Michael W. <wes...@ja...> - 2020-11-19 01:16:50
|
Hi Nick, Like starting to learn most tech related things, O'Reilly has you covered: https://learning.oreilly.com/library/view/exist/9781449337094/ Some of the specifics in the book are for an older version, but the concepts remain the same. The next thing you need is "a problem to be solved," as Bart Busschots (creator of xkpassword.net) is fond of saying. If you can define the problem to be solved, then I'm sure we can help point you in a more solid direction. Hope this helps. Take care. 2020年11月19日(木) 8:56 Nicholas <sau...@gm...>: > I'm just looking for a simple starting point. I don't necessarily need > a GUI, or web app, etc. Just looking to put an XML document into eXist > and run a few XQuery's against it. Any pointers? > > > thanks, > > Nick > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Michael Westbay Writer/System Administrator http://www.japanesebaseball.com/ |
|
From: Loren C. <lor...@gm...> - 2020-11-19 00:45:04
|
Hello folks, I am the maintainer of xqDoc, so I am working on a reworking of function docs. One of the problems is that the current function docs does not care about the boundaries between applications. I am working on the following: The Rest APIs will be an implementation of the SwaggerUI coming from the rest annotations in the xqDoc files. These are application independent. The libraries are also application independent, because their namespaces are registered. This leaves the main and library modules within an application. I am wondering if I should have a level in the tree menu for the modules within an application or when you click on an application that a table with the list of the modules within an application along with the module’s description. Once we get down to a particular module, then the functions will be listed in the main body of the application. The xqDoc has all of the calls that a module makes, so then there will be a hyperlink for the calls, so that you can see dive down into the codebase. I am planning on adding to the application with things like sample code utilizing a function that is to be called. I would also like to attach a schema to parameters as well as results. I would like people’s feedback before I go too far down the rabbit hole. BTW: the Rest API panel is necessary for a client of mine. Please supply feedback! Thank you, Loren |
|
From: Nicholas <sau...@gm...> - 2020-11-18 23:55:58
|
I'm just looking for a simple starting point. I don't necessarily need a GUI, or web app, etc. Just looking to put an XML document into eXist and run a few XQuery's against it. Any pointers? thanks, Nick |
|
From: Michael W. <wes...@ja...> - 2020-11-18 12:34:16
|
2020年11月18日(水) 19:59 Eduard Drenth <ed...@fr...>: > If you standardize everything in the whole chain of > components/programs/processes on utf-8 you won't have problems is my > experience. Don't forget JAVA_OPTS=-Dfile.encoding=UTF-8. > > I use XmldbURI.xmldbUriFor(path.toFile().getName()); to store documents > in a collection. > I use URLDecoder.decode(u, "UTF-8"); to get the original filename. > I second this. I use Japanese and Korean for filenames with no problem having everything everything set to UTF-8. It works fine with oXygen and Nova editors' file trees this way. Take care. -- Michael Westbay Writer/System Administrator http://www.japanesebaseball.com/ |
|
From: Eduard D. <ed...@fr...> - 2020-11-18 10:58:34
|
If you standardize everything in the whole chain of components/programs/processes on utf-8 you won't have problems is my experience. Don't forget JAVA_OPTS=-Dfile.encoding=UTF-8. I use XmldbURI.xmldbUriFor(path.toFile().getName()); to store documents in a collection. I use URLDecoder.decode(u, "UTF-8"); to get the original filename. We too use weird names and diacrits, screenshots from exide/db manager: [cid:d23...@fr...] [cid:d65...@fr...] Hope this helps a bit -----Original Message----- From: David Birnbaum <dj...@gm...<mailto:David%20Birnbaum%20%3cd...@gm...%3e>> To: exi...@li...<mailto:exi...@li...> Subject: [Exist-open] Filenames with awkward characters in eXist-db? Date: Mon, 16 Nov 2020 13:15:29 -0500 Dear eXistentialists, Could someone please advise me about eXist-db’s expectations with respect to filenames? Within an XProc script I generate output files with names that I construct using encode-for-uri(), which I thought meant that they were acceptable URI filenames. Those names include the following: verb-1a%7%-forms.xml verb-1a%[x]%-forms.xml verb-1a%x%-forms.xml verb-1a, ё-forms.xml That is, they contain non-ASCII characters, spaces, percent signs (not as percent-escaping for URI purposes), and square brackets. I understand that these are awkward filenames, but they are usefully self-documenting with respect to their contents, and I don’t have to wrangle them myself on the command line, so on balance I decided that their transparency was more important to me than their awkwardness. But awkwardness is different from impossibility, which arose unexpectedly: When I then try to upload them into eXist-db using the Java admin client, eXist-db accepts the last one, which has a space and a non-ASCII character (both of which it percent-escapes) and rejects the others with the message that the filename “could not be encoded as a URI”. I understand that I can replace the challenging characters (apparently the percent signs that don’t fit the expectation for percent-escaping and the square brackets) myself when I create the files, but I thought creating a filename that was the output of escape-for-uri() was supposed to do that for me. Since encode-for-uri() in XProc can create the output filenames, and both Chrome and Firefox can open and parse the files (as file:/// ...), there seems to be a difference between what eXist-db thinks is acceptable in a URI and what XProc, Chrome, and Firefox think. I would be grateful if someone could please advise me about two questions, one practical and one more philosophical: Practical: What are the expectations of eXist-db with respect to filenames? That is, what awkward characters do I simply have to avoid and which ones will eXist-db handle with percent-escaping or in other ways? Philosophical: Is eXist-db improperly refusing to accept filenames that can, in fact, be encoded as URIs, or is XProc (where I execute the encode-for-uri() operation) creating, and the browsers accepting, something that is not really acceptable? Thanks, David dj...@gm...<mailto:dj...@gm...> _______________________________________________ Exist-open mailing list <mailto:Exi...@li...> Exi...@li... <https://lists.sourceforge.net/lists/listinfo/exist-open> https://lists.sourceforge.net/lists/listinfo/exist-open -- Eduard Drenth, Software Architekt ed...@fr...<mailto:ed...@fr...> Doelestrjitte 8 8911 DX Ljouwert +31 58 234 30 47 +31 62 094 34 28 (privé) skype: eduarddrenth https://github.com/eduarddrenth frisian.eu gpg: https://pgp.surfnet.nl/pks/lookup?search=eduarddrenth Op freed bin ik thús/wurkje ik minder |
|
From: J. J. F. <jjf...@go...> - 2020-11-17 17:40:47
|
Following these instructions: https://exist-db.org/exist/apps/doc/exist-building I did a clean pull and fresg compile via: mvn -DskipTests clean compile Then: mvn package But the tests errored out for "eXist-db Core" (see below) Before I invest more time in this, it would be nice to hear from someone that this should work without major changes. CentOS Linux release 7.9.2009 (Core) = fully patched. [jfelten@gibson exist]$ mvn --version Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /opt/apache-maven-3.6.3 Java version: 1.8.0_272, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.272.b10-1.el7_9.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.10.0-1127.19.1.el7.x86_64", arch: "amd64", family: "unix" Thanks, [INFO] Results: [INFO] [ERROR] Failures: [ERROR] BrokerPoolsTest.shutdownConcurrent:71 [ERROR] Errors: [ERROR] RestBinariesTest.streamBinaryRaw:108->postXquery:167 » NoHttpResponse localhos... [ERROR] org.exist.xquery.update.IndexIntegrationTest.insertElement [ERROR] Run 1: IndexIntegrationTest>AbstractTestUpdate.setUp:68 » XMLDB Failed to store colle... [ERROR] Run 2: IndexIntegrationTest>AbstractTestUpdate.tearDown:77 » IllegalState missing beh... [INFO] [ERROR] org.exist.xquery.update.IndexIntegrationTest.removeAttribute [ERROR] Run 1: IndexIntegrationTest>AbstractTestUpdate.setUp:68 » XMLDB Failed to store colle... [ERROR] Run 2: IndexIntegrationTest>AbstractTestUpdate.tearDown:77 » IllegalState missing beh... [INFO] [ERROR] org.exist.xquery.update.IndexIntegrationTest.updateAttribute [ERROR] Run 1: IndexIntegrationTest.updateAttribute:135->run:78->lambda$updateAttribute$2:142 » IllegalState [ERROR] Run 2: IndexIntegrationTest>AbstractTestUpdate.tearDown:77 » IllegalState 3 matchers ... [INFO] [ERROR] NumberTests » NullPointer [ERROR] SecurityManagerTests.initializationError » NullPointer [ERROR] ValidationTests » NullPointer [ERROR] XMLDBTests » NullPointer [ERROR] XQSuiteTests » NullPointer [INFO] [ERROR] Tests run: 4729, Failures: 1, Errors: 9, Skipped: 105 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for eXist-db 5.3.0-SNAPSHOT: [INFO] [INFO] eXist-db Parent .................................... SUCCESS [ 2.940 s] [INFO] eXist-db Startup ................................... SUCCESS [ 25.989 s] [INFO] eXist-db Jetty Configuration ....................... SUCCESS [ 0.784 s] [INFO] eXist-db Data Samples .............................. SUCCESS [ 0.882 s] [INFO] eXist-db Core ...................................... FAILURE [52:28 min] [INFO] eXist-db Ant Tasks ................................. SKIPPED [INFO] eXist-db Service ................................... SKIPPED [INFO] eXist-db Content Extraction Extension .............. SKIPPED [INFO] eXist-db EXIF Tool Extension ....................... SKIPPED [INFO] eXist-db EXPath Extensions ......................... SKIPPED [INFO] eXist-db EXQuery Request Module .................... SKIPPED [INFO] eXist-db RESTXQ Extension .......................... SKIPPED [INFO] eXist-db WebDAV Extension .......................... SKIPPED [INFO] eXist-db xqDoc Extension ........................... SKIPPED [INFO] eXist-db Lucene Index .............................. SKIPPED [INFO] eXist-db NGram Index ............................... SKIPPED [INFO] eXist-db Lucene Range Index ........................ SKIPPED [INFO] eXist-db Sort Index ................................ SKIPPED [INFO] eXist-db Spatial Index ............................. SKIPPED [INFO] eXist-db Cache Module .............................. SKIPPED [INFO] eXist-db Compression Module ........................ SKIPPED [INFO] eXist-db Counter Module ............................ SKIPPED [INFO] eXist-db CQL Parser Module ......................... SKIPPED [INFO] eXist-db EXPath Repository Module .................. SKIPPED [INFO] eXist-db File Module ............................... SKIPPED [INFO] eXist-db Image Module .............................. SKIPPED [INFO] eXist-db JNDI Module ............................... SKIPPED [INFO] eXist-db Email Module .............................. SKIPPED [INFO] eXist-db Persistent Login Module ................... SKIPPED [INFO] eXist-db Process Module ............................ SKIPPED [INFO] eXist-db Scheduler Module .......................... SKIPPED [INFO] eXist-db SimpleQL Module ........................... SKIPPED [INFO] eXist-db SQL Module ................................ SKIPPED [INFO] eXist-db XML Diff Module ........................... SKIPPED [INFO] eXist-db XSL:FO Module ............................. SKIPPED [INFO] eXist-db LDAP Security Module ...................... SKIPPED [INFO] eXist-db Active Directory Security Module .......... SKIPPED [INFO] eXist-db IP Range Security Module .................. SKIPPED [INFO] eXist-db Distributions ............................. SKIPPED [INFO] eXist-db EXQuery Extension Modules ................. SKIPPED [INFO] eXist-db EXQuery Extensions ........................ SKIPPED [INFO] eXist-db Index Extensions .......................... SKIPPED [INFO] eXist-db Example Module ............................ SKIPPED [INFO] eXist-db EXI Module ................................ SKIPPED [INFO] eXist-db Extension XQuery Modules .................. SKIPPED [INFO] eXist-db Extension Security Modules ................ SKIPPED [INFO] eXist-db Extensions ................................ SKIPPED [INFO] eXist-db IzPack Installer .......................... SKIPPED [INFO] eXist-db Core JCStress Tests ....................... SKIPPED [INFO] eXist-db Core JMH benchmarks ....................... SKIPPED [INFO] eXist-db ........................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 53:02 min [INFO] Finished at: 2020-11-17T17:09:14Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M4:test (default-test) on project exist-core: There are test failures. [ERROR] [ERROR] Please refer to /home/jfelten/exist/exist-core/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :exist-core |
|
From: David B. <dj...@gm...> - 2020-11-16 18:16:02
|
Dear eXistentialists, Could someone please advise me about eXist-db’s expectations with respect to filenames? Within an XProc script I generate output files with names that I construct using encode-for-uri(), which I thought meant that they were acceptable URI filenames. Those names include the following: verb-1a%7%-forms.xml verb-1a%[x]%-forms.xml verb-1a%x%-forms.xml verb-1a, ё-forms.xml That is, they contain non-ASCII characters, spaces, percent signs (not as percent-escaping for URI purposes), and square brackets. I understand that these are awkward filenames, but they are usefully self-documenting with respect to their contents, and I don’t have to wrangle them myself on the command line, so on balance I decided that their transparency was more important to me than their awkwardness. But awkwardness is different from impossibility, which arose unexpectedly: When I then try to upload them into eXist-db using the Java admin client, eXist-db accepts the last one, which has a space and a non-ASCII character (both of which it percent-escapes) and rejects the others with the message that the filename “could not be encoded as a URI”. I understand that I can replace the challenging characters (apparently the percent signs that don’t fit the expectation for percent-escaping and the square brackets) myself when I create the files, but I thought creating a filename that was the output of escape-for-uri() was supposed to do that for me. Since encode-for-uri() in XProc can create the output filenames, and both Chrome and Firefox can open and parse the files (as file:/// ...), there seems to be a difference between what eXist-db thinks is acceptable in a URI and what XProc, Chrome, and Firefox think. I would be grateful if someone could please advise me about two questions, one practical and one more philosophical: Practical: What are the expectations of eXist-db with respect to filenames? That is, what awkward characters do I simply have to avoid and which ones will eXist-db handle with percent-escaping or in other ways? Philosophical: Is eXist-db improperly refusing to accept filenames that can, in fact, be encoded as URIs, or is XProc (where I execute the encode-for-uri() operation) creating, and the browsers accepting, something that is not really acceptable? Thanks, David dj...@gm... |
|
From: Loren C. <lor...@gm...> - 2020-11-16 14:31:27
|
Please make sure to keep me in the loop. I will need to keep xqDoc up to date. > On Nov 16, 2020, at 6:28 AM, Christian Grün <chr...@gm...> wrote: > >> I don't know how many implementers we have on this list, outside of Christian and co., but thought you all might find it interesting. > > Everyone: raise your hands and get involved ;) > > Michael’s initiative to push for a new version of XQuery, XPath & co. > is very promising indeed. If you are interested in sharing your ideas > which features you would like to see in a new version: Now may still > be a good time for it! > > > >> PS I found this announcement on the XML.com Slack channel, fyi. >> >> [1] Mike Kay's post from Slack: >> I've been working on fleshing out my ideas for XSLT/XPath 4.0, based on my XML Prague paper earlier this year. I'm hoping to gather together a community group of some kind to take this forward; meanwhile I've published a very preliminary set of drafts: >> XSLT: https://www.saxonica.com/qt4specs/XT/Overview-diff.html >> F&O: https://www.saxonica.com/qt4specs/FO/Overview-diff.html >> XPath: https://www.saxonica.com/qt4specs/XP/xpath-40-diff.html >> XQuery: https://www.saxonica.com/qt4specs/XQ/xquery-40-diff.html >> Preparing for the rotten tomatoes: let me know what you think and whether you want to participate. >> NOTE: each document has a summary of changes at the end. It's probably best to go there first. |
|
From: <sju...@mr...> - 2020-11-14 00:42:23
|
Hi All, we ran into the issue where client's server lost power (UPS failed), server was not gracefully powered off and at the end eXist corrupted. eXist version 4.7.1, Windows OS We tried to use Consistency Check tool, which usually works like a charm, so we can export all XMLs and re-import them, but this time it failes ...b-tree failure. If we keep just dom, collection and symbols and try to restart exist ... it fails and exist generates huge log files (roughly 20 of them) all containing error messages. ----------------- Now, is there a way to retrieve the data as of the time of the crash? Is there any other tool available to the public? Wolfgang helps us with the same issue 10 years ago, with exist 2.1 (or 2.2), but that is not the right way. We do have daily backups, so we can restore as of yesterday. Much appreciated! Sava |
|
From: John R. <jr...@gm...> - 2020-10-30 23:52:13
|
The icon worked after I changed the file name in the controller.xql on line 17 <redirect url="FileLinkedFromTheLauncher.xqy"/> Thanks. On Fri, Oct 30, 2020 at 9:53 AM Joe Wicentowski <jo...@gm...> wrote: > Hi John, > > Ah, thanks for clarifying. Now I understand. The launcher will always > first submit a request to http://localhost:8080/exist/apps/my-app. How > your app responds depends on whether you have a specifically named XQuery > main module, "controller.xql", in that collection or not. Without that > module, eXist will serve up a listing of the resources in your app's > collection. With that module, eXist will execute its logic using the rules > defined in the URL Rewriting documentation. See > https://exist-db.org/exist/apps/doc/urlrewrite. > > To accomplish what you want, it sounds like you want to redirect a request > from your app's root to FileLinkedFromTheLauncher.xqy. For a sample of > similar behavior (redirecting a request for eXide's root to > eXide/index.html), see > https://github.com/eXist-db/eXide/blob/develop/controller.xql#L81-L94. > > Joe > > On Fri, Oct 30, 2020 at 12:30 PM John Reed <jr...@gm...> wrote: > >> EXist-db 5.2.0 on Windows 10 Pro 64 bit >> >> For example, if I click on the icon labelled "xforms-tutorial" it opens >> to the second screen shot. But let's say for example, I want to change that >> file to another one: >> http://localhost:8080/exist/apps/xforms-tutorial/FileLinkedFromTheLauncher.xqy >> so that it opens to the xquery. >> How do I change the uri associated with the icon in the Launcher tray? Is >> there a file in eXist-db that I modify? >> >> >> >> >> [image: image.png] >> >> http://localhost:8080/exist/apps/xforms-tutorial/index.html >> >> [image: image.png] >> >> [image: image.png] >> >> >> On Fri, Oct 30, 2020 at 8:40 AM Joe Wicentowski <jo...@gm...> wrote: >> >>> Hi John, >>> >>> I'm not sure I'll have the answer, but let's establish a context so >>> others might be able to help: Which version of eXist and which OS are you >>> using? And could you also please clarify (perhaps with screenshots) what >>> you mean by "the icon from the launcher", "the app icon", and "the file"? >>> >>> Joe >>> >>> On Fri, Oct 30, 2020 at 11:34 AM John Reed <jr...@gm...> wrote: >>> >>>> Hello, How can I change the uri of the file of my app at the launcher >>>> app so that when I click on the icon from the launcher the app icon opens >>>> the file? Thanks John Reed >>>> _______________________________________________ >>>> Exist-open mailing list >>>> Exi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>> >>> |
|
From: Nick S. <nsi...@nu...> - 2020-10-30 17:49:14
|
I also wanted to point out that the Expath Crypto v5.3.0 module information says that it requires eXist-db 4.4.0, but it also says it is available in my eXist-db 5.3.0-SNAPSHOT system. It is my understanding that the module structure changed when we moved to eXist-db 5.x.x. So, I think something is wrong. Either this module should say it requires eXist-db 5.x.x or it should not be available for eXist-db 5.x.x systems. I am not sure which it is. Nick On 10/30/20 10:04 AM, Joe Wicentowski wrote: > Hi Joern, > > I agree, this state is not ideal. > > A duplicate entry will occur whenever a package's namespace URI > changes. All of these packages changed from http://expath.org/lib/_ > <http://expath.org/lib/_> to http://expath.org/ns/_ > <http://expath.org/ns/_>. > > The change in package namespace also roughly corresponds with a new > minimum version requirement - from 2.2+ to some higher version. The > earlier variant is still offered in the public-repo, because it is > compatible with older versions of eXist than the newer variant. (This > version issue is clearer in the public-repo than in the package > manager, since version dependencies are displayed). The duplicates > still appear in package manager because the older variants do not > state a maximum version - so they appear to be compatible with all > versions of eXist since 2.2. > > A partial solution would be for us to issue a new release of each > older variant *with a maximum version declared*, corresponding to the > minimum version for the newer variant. That way, the older variant > would be filtered out of package manager views, since the package > manager includes its version in its query to the public repo. We would > have to pull any versions of the older variant that lack this minimum > version declaration from the public-repo. We could also repair the > package metadata for datatypes v0.2.0, which appears to be missing the > description and abbrev fields. > > Claudius, do you think we could work together on preparing these new > versions? I could check them before uploading and remove the earlier > variants at the public repo. > > Joe > > p.s. I sent this response earlier this morning, but it appears to have > bounced back to me because the screenshot I included of the > public-repo was too large. Sorry if anyone receives a duplicate. > > On Fri, Oct 30, 2020 at 8:49 AM Joern Turner <joe...@gm... > <mailto:joe...@gm...>> wrote: > > Goto packagemanager and click 'available' tab. > > Some EXPath packages occur as duplicates in the list (see attached > screenshot) > > Seems that by changing the underlying name is the problem. For > packagemanager this is now (correctly) assumed to be a new lib. > IMO the name should be guaranteed to be persistent as it > constitutes the identity of the lib. Or - on the other hand you > have strong evidence to change it anyway you should at least > > > also change the title. > Screenshot_2020-10-30 existdb-dashboard.png > was not sure where to file that issue. > > Joern > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > <mailto:Exi...@li...> > https://lists.sourceforge.net/lists/listinfo/exist-open > <https://lists.sourceforge.net/lists/listinfo/exist-open> > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open -- Nick Sincaglia President/Founder NueMeta, LLC Digital Media & Technology Phone: +1-630-303-7035 nsi...@nu... http://www.nuemeta.com Skype: nsincaglia |
|
From: Joe W. <jo...@gm...> - 2020-10-30 16:54:07
|
Hi John, Ah, thanks for clarifying. Now I understand. The launcher will always first submit a request to http://localhost:8080/exist/apps/my-app. How your app responds depends on whether you have a specifically named XQuery main module, "controller.xql", in that collection or not. Without that module, eXist will serve up a listing of the resources in your app's collection. With that module, eXist will execute its logic using the rules defined in the URL Rewriting documentation. See https://exist-db.org/exist/apps/doc/urlrewrite. To accomplish what you want, it sounds like you want to redirect a request from your app's root to FileLinkedFromTheLauncher.xqy. For a sample of similar behavior (redirecting a request for eXide's root to eXide/index.html), see https://github.com/eXist-db/eXide/blob/develop/controller.xql#L81-L94. Joe On Fri, Oct 30, 2020 at 12:30 PM John Reed <jr...@gm...> wrote: > EXist-db 5.2.0 on Windows 10 Pro 64 bit > > For example, if I click on the icon labelled "xforms-tutorial" it opens to > the second screen shot. But let's say for example, I want to change that > file to another one: > http://localhost:8080/exist/apps/xforms-tutorial/FileLinkedFromTheLauncher.xqy > so that it opens to the xquery. > How do I change the uri associated with the icon in the Launcher tray? Is > there a file in eXist-db that I modify? > > > > > [image: image.png] > > http://localhost:8080/exist/apps/xforms-tutorial/index.html > > [image: image.png] > > [image: image.png] > > > On Fri, Oct 30, 2020 at 8:40 AM Joe Wicentowski <jo...@gm...> wrote: > >> Hi John, >> >> I'm not sure I'll have the answer, but let's establish a context so >> others might be able to help: Which version of eXist and which OS are you >> using? And could you also please clarify (perhaps with screenshots) what >> you mean by "the icon from the launcher", "the app icon", and "the file"? >> >> Joe >> >> On Fri, Oct 30, 2020 at 11:34 AM John Reed <jr...@gm...> wrote: >> >>> Hello, How can I change the uri of the file of my app at the launcher >>> app so that when I click on the icon from the launcher the app icon opens >>> the file? Thanks John Reed >>> _______________________________________________ >>> Exist-open mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-open >>> >> |
602 messages has been excluded from this view by a project administrator.
