You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(31) |
Nov
(25) |
Dec
(33) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(48) |
Feb
(62) |
Mar
(22) |
Apr
(29) |
May
(9) |
Jun
(45) |
Jul
(28) |
Aug
(41) |
Sep
(60) |
Oct
(96) |
Nov
(99) |
Dec
(70) |
| 2003 |
Jan
(98) |
Feb
(159) |
Mar
(164) |
Apr
(150) |
May
(143) |
Jun
(97) |
Jul
(184) |
Aug
(143) |
Sep
(207) |
Oct
(126) |
Nov
(159) |
Dec
(165) |
| 2004 |
Jan
(131) |
Feb
(229) |
Mar
(220) |
Apr
(212) |
May
(320) |
Jun
(223) |
Jul
(191) |
Aug
(390) |
Sep
(261) |
Oct
(229) |
Nov
(215) |
Dec
(184) |
| 2005 |
Jan
(221) |
Feb
(312) |
Mar
(336) |
Apr
(273) |
May
(359) |
Jun
(277) |
Jul
(303) |
Aug
(321) |
Sep
(256) |
Oct
(415) |
Nov
(428) |
Dec
(508) |
| 2006 |
Jan
(585) |
Feb
(419) |
Mar
(496) |
Apr
(296) |
May
(403) |
Jun
(404) |
Jul
(553) |
Aug
(296) |
Sep
(252) |
Oct
(416) |
Nov
(414) |
Dec
(245) |
| 2007 |
Jan
(354) |
Feb
(422) |
Mar
(389) |
Apr
(298) |
May
(397) |
Jun
(318) |
Jul
(315) |
Aug
(339) |
Sep
(253) |
Oct
(317) |
Nov
(350) |
Dec
(264) |
| 2008 |
Jan
(353) |
Feb
(313) |
Mar
(433) |
Apr
(383) |
May
(343) |
Jun
(355) |
Jul
(321) |
Aug
(338) |
Sep
(242) |
Oct
(206) |
Nov
(199) |
Dec
(279) |
| 2009 |
Jan
(327) |
Feb
(221) |
Mar
(280) |
Apr
(278) |
May
(237) |
Jun
(345) |
Jul
(322) |
Aug
(324) |
Sep
(676) |
Oct
(586) |
Nov
(735) |
Dec
(329) |
| 2010 |
Jan
(619) |
Feb
(424) |
Mar
(529) |
Apr
(241) |
May
(312) |
Jun
(554) |
Jul
(698) |
Aug
(576) |
Sep
(408) |
Oct
(268) |
Nov
(391) |
Dec
(426) |
| 2011 |
Jan
(629) |
Feb
(512) |
Mar
(465) |
Apr
(467) |
May
(475) |
Jun
(403) |
Jul
(426) |
Aug
(542) |
Sep
(418) |
Oct
(620) |
Nov
(614) |
Dec
(358) |
| 2012 |
Jan
(357) |
Feb
(466) |
Mar
(344) |
Apr
(215) |
May
(408) |
Jun
(375) |
Jul
(241) |
Aug
(260) |
Sep
(401) |
Oct
(461) |
Nov
(498) |
Dec
(294) |
| 2013 |
Jan
(453) |
Feb
(447) |
Mar
(434) |
Apr
(326) |
May
(295) |
Jun
(471) |
Jul
(463) |
Aug
(278) |
Sep
(525) |
Oct
(343) |
Nov
(389) |
Dec
(405) |
| 2014 |
Jan
(564) |
Feb
(324) |
Mar
(319) |
Apr
(319) |
May
(384) |
Jun
(259) |
Jul
(210) |
Aug
(219) |
Sep
(315) |
Oct
(478) |
Nov
(207) |
Dec
(316) |
| 2015 |
Jan
(222) |
Feb
(234) |
Mar
(201) |
Apr
(145) |
May
(367) |
Jun
(318) |
Jul
(195) |
Aug
(210) |
Sep
(234) |
Oct
(248) |
Nov
(217) |
Dec
(189) |
| 2016 |
Jan
(219) |
Feb
(177) |
Mar
(110) |
Apr
(91) |
May
(159) |
Jun
(124) |
Jul
(192) |
Aug
(119) |
Sep
(125) |
Oct
(64) |
Nov
(80) |
Dec
(68) |
| 2017 |
Jan
(156) |
Feb
(312) |
Mar
(386) |
Apr
(217) |
May
(89) |
Jun
(115) |
Jul
(79) |
Aug
(122) |
Sep
(100) |
Oct
(99) |
Nov
(129) |
Dec
(77) |
| 2018 |
Jan
(106) |
Feb
(78) |
Mar
(160) |
Apr
(73) |
May
(110) |
Jun
(160) |
Jul
(93) |
Aug
(92) |
Sep
(75) |
Oct
(147) |
Nov
(114) |
Dec
(97) |
| 2019 |
Jan
(141) |
Feb
(78) |
Mar
(158) |
Apr
(60) |
May
(123) |
Jun
(54) |
Jul
(44) |
Aug
(147) |
Sep
(117) |
Oct
(54) |
Nov
(74) |
Dec
(96) |
| 2020 |
Jan
(113) |
Feb
(125) |
Mar
(142) |
Apr
(57) |
May
(71) |
Jun
(99) |
Jul
(58) |
Aug
(81) |
Sep
(49) |
Oct
(50) |
Nov
(63) |
Dec
(37) |
| 2021 |
Jan
(37) |
Feb
(45) |
Mar
(39) |
Apr
(18) |
May
(14) |
Jun
(9) |
Jul
(44) |
Aug
(23) |
Sep
(13) |
Oct
(31) |
Nov
(13) |
Dec
(33) |
| 2022 |
Jan
(17) |
Feb
(8) |
Mar
(32) |
Apr
(7) |
May
(17) |
Jun
(7) |
Jul
(36) |
Aug
(29) |
Sep
(9) |
Oct
(20) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(30) |
Feb
(37) |
Mar
(23) |
Apr
(1) |
May
(14) |
Jun
(5) |
Jul
(3) |
Aug
(6) |
Sep
(5) |
Oct
(48) |
Nov
(4) |
Dec
(29) |
| 2024 |
Jan
(1) |
Feb
|
Mar
(21) |
Apr
(6) |
May
(16) |
Jun
(41) |
Jul
(11) |
Aug
(17) |
Sep
(16) |
Oct
(11) |
Nov
(3) |
Dec
(9) |
| 2025 |
Jan
(7) |
Feb
(7) |
Mar
(6) |
Apr
(6) |
May
(30) |
Jun
(8) |
Jul
(10) |
Aug
(4) |
Sep
(10) |
Oct
(32) |
Nov
(3) |
Dec
|
|
From: Joe W. <jo...@gm...> - 2023-01-26 19:35:48
|
Hi Bernie, Great, thanks for confirming that and testing with the exist namespace prefix. I do not know if this serialization parameter is available in the RESTXQ context. Looking at the history of the RESTXQ serializer code, it appears that it's had to be updated whenever new serialization properties have been added to eXist. This suggests that if your code is not working, that RESTXQ has to be updated to support this serialization property. You might look into constructing your JSON with XQuery, instead of relying on eXist's own XML-to-JSON serialization handling. (For reference, these are the rules exist applies: https://exist-db.org/exist/apps/wiki/blogs/eXist/JSONSerializer.) Or as a real kludge, you could re-parse the serialized JSON: ``` xquery version "3.1"; declare namespace hdp="http://www.spase-group.org/data/schema"; let $node := <hdp:result xmlns="http://www.spase-group.org/data/schema"> <hdp:collection> <hdp:resource> <Spase xmlns="http://www.spase-group.org/data/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_4_0.xsd"> <Version>2.4.0</Version> <NumericalData> <ResourceID>spase://NASA/NumericalData/ACE/CRIS/L2/PT1H</ResourceID> <ResourceHeader> <ResourceName>ACE Cosmic Ray Isotope Spectrometer (CRIS) 1-Hour Level 2 Data</ResourceName> <DOI>https://doi.org/10.48322/g72t-0814</DOI> <ReleaseDate>2022-05-17T12:34:56.789</ReleaseDate> </ResourceHeader> </NumericalData> </Spase></hdp:resource></hdp:collection></hdp:result> let $serialized := serialize($node, map { "method": "json", "exist:json-ignore-whitespace-text-nodes": true() }) return parse-json($serialized) ``` This returns: ``` map { "collection": map { "resource": map { "Spase": map { "xsi:schemaLocation": " http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_4_0.xsd", "NumericalData": map { "ResourceID": "spase://NASA/NumericalData/ACE/CRIS/L2/PT1H", "ResourceHeader": map { "DOI": "https://doi.org/10.48322/g72t-0814", "ResourceName": "ACE Cosmic Ray Isotope Spectrometer (CRIS) 1-Hour Level 2 Data", "ReleaseDate": "2022-05-17T12:34:56.789" } }, "Version": "2.4.0" } } } } ``` Returning this in your RESTXQ function should work (though I haven't tested it). Joe On Thu, Jan 26, 2023 at 1:57 PM Harris, Bernard T. (GSFC-5870) < ber...@na...> wrote: > And I still have the problem with > > <exist:json-ignore-whitespace-text-nodes value="yes" /> > > > > Bernie > > > > *From: *"Harris, Bernard T. (GSFC-5870)" <ber...@na...> > *Date: *Thursday, January 26, 2023 at 1:52 PM > *To: *Joe Wicentowski <jo...@gm...> > *Cc: *Exist-open <exi...@li...> > *Subject: *Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes > > > > I saw it but did not think it was applicable since I was not explicitly > calling serialize. But just now, I added an extra line to my example > > > > <rest:response> > > <output:serialization-parameters> > > <output:method value="json" /> > > <output:json-ignore-whitespace-text-nodes value="yes" /> > > </output:serialization-parameters> > > <http:response> > > <http:header name="Content-Type" value="application/json" > /> > > </http:response> > > </rest:response>, > > > > And reran the test. It does not change the output. I still get a bunch > of “#text” stuff. > > > > Bernie > > > > *From: *Joe Wicentowski <jo...@gm...> > *Date: *Thursday, January 26, 2023 at 1:42 PM > *To: *"Harris, Bernard T. (GSFC-5870)" <ber...@na...> > *Cc: *Exist-open <exi...@li...> > *Subject: *Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes > > > > Hi Bernie, > > > Did you by chance see my earlier response with links to code demonstrating > how to use the json-ignore-whitespace-text-nodes property? > > > > Joe > > > > On Thu, Jan 26, 2023 at 1:32 PM Harris, Bernard T. (GSFC-5870) < > ber...@na...> wrote: > > https://cdaweb.gsfc.nasa.gov/registry/hdp/restxqJson-0.1.xar > > contains an example app that demonstrates my problem. Once the > application is install, > > > > $ curl http://localhost:8100/exist/restxq/test > > { "collection" : { "resource" : { "Spase" : { "xsi:schemaLocation" : http://www.spase-group.org/data/schema > https://www.spase-group.org/data/schema/spase-2_4_0.xsd > <https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spase-group.org%2Fdata%2Fschema%2520https%3A%2Fwww.spase-group.org%2Fdata%2Fschema%2Fspase-2_4_0.xsd&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=JDLepR8iMWsG2SJ8bXCDAatYqmV9Y8CReHu99XeqE7U%3D&reserved=0>, > "#text" : ["\n ", "\n ", "\n" ], "Version" : "2.4.0", "NumericalData" : > { "#text" : ["\n ", "\n ", "\n " ], "ResourceID" : > "spase://NASA/NumericalData/ACE/CRIS/L2/PT1H", "ResourceHeader" : { "#text" > : ["\n ", "\n ", "\n ", "\n " ], > "ResourceName" : "ACE Cosmic Ray Isotope Spectrometer (CRIS) 1-Hour Level 2 > Data", "DOI" : https://doi.org/10.48322/g72t-0814 > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoi.org%2F10.48322%2Fg72t-0814&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=lGrJL%2BI77%2FMd%2F56pG93TJtx%2BxHHUNuFX7sfZMjUQAoA%3D&reserved=0>, > "ReleaseDate" : "2022-05-17T12:34:56.789" } } } } } > > > > Demonstrates the problem. If you change the code to > > let $example := 2 > > so that the xml does not come from the db, the json will not contain all > the “#text” stuff. Let me know if you need anything else. Thanks for > looking at this. > > > > Bernie Harris > > > > *From: *"Harris, Bernard T. (GSFC-5870)" <ber...@na...> > *Date: *Thursday, January 26, 2023 at 5:26 AM > *To: *Joe Wicentowski <jo...@gm...> > *Cc: *Exist-open <exi...@li...> > *Subject: *Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes > > > > I’m still attempting to reproduce in a minimal amount of code but it is > taking a lot of time. But maybe just seeing the output will be enough for > you to know what is wrong. This is a RESTXQ application and I first > noticed the problem on exist 6.0.1 but have also now reproduced it on 4.4. > Here is a little bit of the output > > > > $ curl -s -H "Accept: application/json" > http://localhost:8100/exist/restxq/Spase/NumericalData?ResourceID=spase://NASA/NumericalData/ACE/MAG/L2/PT16S > |jq |head -15 > > { > > "collection": { > > "resource": { > > "Spase": { > > "xsi:schemaLocation": http://www.spase-group.org/data/schema > https://www.spase-group.org/data/schema/spase-2_3_2.xsd > <https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spase-group.org%2Fdata%2Fschema%2520%2520https%3A%2Fwww.spase-group.org%2Fdata%2Fschema%2Fspase-2_3_2.xsd&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=fIKPZfwfeBYomcQtNKigX4mnl95WBz1z9WhoIKBsU6E%3D&reserved=0> > , > > "#text": [ > > "\n ", > > "\n ", > > "\n" > > ], > > "Version": "2.3.2", > > "NumericalData": { > > "#text": [ > > "\n ", > > "\n ", > > > > The problem is all the extra #text values. They don’t appear in the xml > output. Years ago when I developed something similar without RESTXQ, this > > > > declare option exist:serialize "json-ignore-whitespace-text-nodes=yes"; > > > > eliminated the extra #text stuff. But that does not work in my RESTXQ > app. and it will take me more time to create a minimal RESTXQ example. I > would apricate any help you can give but understand if you need example > code. > > > > Bernie > > > > *From: *Joe Wicentowski <jo...@gm...> > *Date: *Wednesday, January 25, 2023 at 6:07 AM > *To: *"Harris, Bernard T. (GSFC-5870)" <ber...@na...> > *Cc: *Exist-open <exi...@li...> > *Subject: *Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes > > > > Could you provide more info? How to reproduce? Expected vs. actual > results? What version of eXist? > > > > On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via > Exist-open <exi...@li...> wrote: > > I noticed the same thing. But I was working with RESTXQ (and exist-db > 6.0.1) for the first time and thought I might need to do things differently > than the way it had worked in the past. I would like to know if this is a > bug or if there is a different way to accomplish the same thing. > > > > Bernie Harris > > > > *From: *Eduard Drenth <ed...@fr...> > *Date: *Sunday, January 22, 2023 at 11:22 AM > *To: *Exist-open <exi...@li...> > *Subject: *[EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes > > > > json-ignore-whitespace-text-nodes not supported anymore? > > > > > > > > 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=iKPW3w5hT7zCv%2F3FORRs7AbwmaNL%2F8Ll5EaNkkQIwns%3D&reserved=0> > > https://frysker.nl/ > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=9eMUDr0ES2uRkRPhhe%2FVP33hpglV1%2B8Q10JBfpWss6M%3D&reserved=0> > > https://frisian.eu/ > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=%2B0l%2FnBilBZdzESuGGLthhiE2DERf%2BKAvBwJm3V%2FBZ3U%3D&reserved=0> > > gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth > <https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpgp.key-server.io%2Fpks%2Flookup%3Fsearch%3Deduarddrenth&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=ilxi51ZR4iMEUnOL4MxFWG0jyflw5fmnaGXqq5KYqqA%3D&reserved=0> > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fexist-open&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=T4finZMlulTU9YjweRgqGS84auNJj9ehC3SoKcoJtZ4%3D&reserved=0> > > -- > > Sent from my iPhone > > |
|
From: Harris, B. T. (GSFC-5870) <ber...@na...> - 2023-01-26 19:06:39
|
I saw it but did not think it was applicable since I was not explicitly calling serialize. But just now, I added an extra line to my example
<rest:response>
<output:serialization-parameters>
<output:method value="json" />
<output:json-ignore-whitespace-text-nodes value="yes" />
</output:serialization-parameters>
<http:response>
<http:header name="Content-Type" value="application/json" />
</http:response>
</rest:response>,
And reran the test. It does not change the output. I still get a bunch of “#text” stuff.
Bernie
From: Joe Wicentowski <jo...@gm...>
Date: Thursday, January 26, 2023 at 1:42 PM
To: "Harris, Bernard T. (GSFC-5870)" <ber...@na...>
Cc: Exist-open <exi...@li...>
Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes
Hi Bernie,
Did you by chance see my earlier response with links to code demonstrating how to use the json-ignore-whitespace-text-nodes property?
Joe
On Thu, Jan 26, 2023 at 1:32 PM Harris, Bernard T. (GSFC-5870) <ber...@na...<mailto:ber...@na...>> wrote:
https://cdaweb.gsfc.nasa.gov/registry/hdp/restxqJson-0.1.xar
contains an example app that demonstrates my problem. Once the application is install,
$ curl http://localhost:8100/exist/restxq/test
{ "collection" : { "resource" : { "Spase" : { "xsi:schemaLocation" : http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_4_0.xsd<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spase-group.org%2Fdata%2Fschema%2520https%3A%2Fwww.spase-group.org%2Fdata%2Fschema%2Fspase-2_4_0.xsd&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=JDLepR8iMWsG2SJ8bXCDAatYqmV9Y8CReHu99XeqE7U%3D&reserved=0>, "#text" : ["\n ", "\n ", "\n" ], "Version" : "2.4.0", "NumericalData" : { "#text" : ["\n ", "\n ", "\n " ], "ResourceID" : "spase://NASA/NumericalData/ACE/CRIS/L2/PT1H", "ResourceHeader" : { "#text" : ["\n ", "\n ", "\n ", "\n " ], "ResourceName" : "ACE Cosmic Ray Isotope Spectrometer (CRIS) 1-Hour Level 2 Data", "DOI" : https://doi.org/10.48322/g72t-0814<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoi.org%2F10.48322%2Fg72t-0814&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=lGrJL%2BI77%2FMd%2F56pG93TJtx%2BxHHUNuFX7sfZMjUQAoA%3D&reserved=0>, "ReleaseDate" : "2022-05-17T12:34:56.789" } } } } }
Demonstrates the problem. If you change the code to
let $example := 2
so that the xml does not come from the db, the json will not contain all the “#text” stuff. Let me know if you need anything else. Thanks for looking at this.
Bernie Harris
From: "Harris, Bernard T. (GSFC-5870)" <ber...@na...<mailto:ber...@na...>>
Date: Thursday, January 26, 2023 at 5:26 AM
To: Joe Wicentowski <jo...@gm...<mailto:jo...@gm...>>
Cc: Exist-open <exi...@li...<mailto:exi...@li...>>
Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes
I’m still attempting to reproduce in a minimal amount of code but it is taking a lot of time. But maybe just seeing the output will be enough for you to know what is wrong. This is a RESTXQ application and I first noticed the problem on exist 6.0.1 but have also now reproduced it on 4.4. Here is a little bit of the output
$ curl -s -H "Accept: application/json" http://localhost:8100/exist/restxq/Spase/NumericalData?ResourceID=spase://NASA/NumericalData/ACE/MAG/L2/PT16S |jq |head -15
{
"collection": {
"resource": {
"Spase": {
"xsi:schemaLocation": http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_3_2.xsd<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spase-group.org%2Fdata%2Fschema%2520%2520https%3A%2Fwww.spase-group.org%2Fdata%2Fschema%2Fspase-2_3_2.xsd&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=fIKPZfwfeBYomcQtNKigX4mnl95WBz1z9WhoIKBsU6E%3D&reserved=0>,
"#text": [
"\n ",
"\n ",
"\n"
],
"Version": "2.3.2",
"NumericalData": {
"#text": [
"\n ",
"\n ",
The problem is all the extra #text values. They don’t appear in the xml output. Years ago when I developed something similar without RESTXQ, this
declare option exist:serialize "json-ignore-whitespace-text-nodes=yes";
eliminated the extra #text stuff. But that does not work in my RESTXQ app. and it will take me more time to create a minimal RESTXQ example. I would apricate any help you can give but understand if you need example code.
Bernie
From: Joe Wicentowski <jo...@gm...<mailto:jo...@gm...>>
Date: Wednesday, January 25, 2023 at 6:07 AM
To: "Harris, Bernard T. (GSFC-5870)" <ber...@na...<mailto:ber...@na...>>
Cc: Exist-open <exi...@li...<mailto:exi...@li...>>
Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes
Could you provide more info? How to reproduce? Expected vs. actual results? What version of eXist?
On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via Exist-open <exi...@li...<mailto:exi...@li...>> wrote:
I noticed the same thing. But I was working with RESTXQ (and exist-db 6.0.1) for the first time and thought I might need to do things differently than the way it had worked in the past. I would like to know if this is a bug or if there is a different way to accomplish the same thing.
Bernie Harris
From: Eduard Drenth <ed...@fr...<mailto:ed...@fr...>>
Date: Sunday, January 22, 2023 at 11:22 AM
To: Exist-open <exi...@li...<mailto:exi...@li...>>
Subject: [EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes
json-ignore-whitespace-text-nodes not supported anymore?
Eduard Drenth, Software Architekt
ed...@fr...<mailto:ed...@fr...>
Doelestrjitte 8
8911 DX Ljouwert
(058) 213 14 14
+31 62 094 34 28
https://www.fryske-akademy.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=iKPW3w5hT7zCv%2F3FORRs7AbwmaNL%2F8Ll5EaNkkQIwns%3D&reserved=0>
https://frysker.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=9eMUDr0ES2uRkRPhhe%2FVP33hpglV1%2B8Q10JBfpWss6M%3D&reserved=0>
https://frisian.eu/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=%2B0l%2FnBilBZdzESuGGLthhiE2DERf%2BKAvBwJm3V%2FBZ3U%3D&reserved=0>
[cid:image001.png@01D9318D.5D986B00]
gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpgp.key-server.io%2Fpks%2Flookup%3Fsearch%3Deduarddrenth&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=ilxi51ZR4iMEUnOL4MxFWG0jyflw5fmnaGXqq5KYqqA%3D&reserved=0>
_______________________________________________
Exist-open mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-open<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fexist-open&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=T4finZMlulTU9YjweRgqGS84auNJj9ehC3SoKcoJtZ4%3D&reserved=0>
--
Sent from my iPhone
|
|
From: Harris, B. T. (GSFC-5870) <ber...@na...> - 2023-01-26 18:57:49
|
And I still have the problem with
<exist:json-ignore-whitespace-text-nodes value="yes" />
Bernie
From: "Harris, Bernard T. (GSFC-5870)" <ber...@na...>
Date: Thursday, January 26, 2023 at 1:52 PM
To: Joe Wicentowski <jo...@gm...>
Cc: Exist-open <exi...@li...>
Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes
I saw it but did not think it was applicable since I was not explicitly calling serialize. But just now, I added an extra line to my example
<rest:response>
<output:serialization-parameters>
<output:method value="json" />
<output:json-ignore-whitespace-text-nodes value="yes" />
</output:serialization-parameters>
<http:response>
<http:header name="Content-Type" value="application/json" />
</http:response>
</rest:response>,
And reran the test. It does not change the output. I still get a bunch of “#text” stuff.
Bernie
From: Joe Wicentowski <jo...@gm...>
Date: Thursday, January 26, 2023 at 1:42 PM
To: "Harris, Bernard T. (GSFC-5870)" <ber...@na...>
Cc: Exist-open <exi...@li...>
Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes
Hi Bernie,
Did you by chance see my earlier response with links to code demonstrating how to use the json-ignore-whitespace-text-nodes property?
Joe
On Thu, Jan 26, 2023 at 1:32 PM Harris, Bernard T. (GSFC-5870) <ber...@na...<mailto:ber...@na...>> wrote:
https://cdaweb.gsfc.nasa.gov/registry/hdp/restxqJson-0.1.xar
contains an example app that demonstrates my problem. Once the application is install,
$ curl http://localhost:8100/exist/restxq/test
{ "collection" : { "resource" : { "Spase" : { "xsi:schemaLocation" : http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_4_0.xsd<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spase-group.org%2Fdata%2Fschema%2520https%3A%2Fwww.spase-group.org%2Fdata%2Fschema%2Fspase-2_4_0.xsd&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=JDLepR8iMWsG2SJ8bXCDAatYqmV9Y8CReHu99XeqE7U%3D&reserved=0>, "#text" : ["\n ", "\n ", "\n" ], "Version" : "2.4.0", "NumericalData" : { "#text" : ["\n ", "\n ", "\n " ], "ResourceID" : "spase://NASA/NumericalData/ACE/CRIS/L2/PT1H", "ResourceHeader" : { "#text" : ["\n ", "\n ", "\n ", "\n " ], "ResourceName" : "ACE Cosmic Ray Isotope Spectrometer (CRIS) 1-Hour Level 2 Data", "DOI" : https://doi.org/10.48322/g72t-0814<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoi.org%2F10.48322%2Fg72t-0814&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=lGrJL%2BI77%2FMd%2F56pG93TJtx%2BxHHUNuFX7sfZMjUQAoA%3D&reserved=0>, "ReleaseDate" : "2022-05-17T12:34:56.789" } } } } }
Demonstrates the problem. If you change the code to
let $example := 2
so that the xml does not come from the db, the json will not contain all the “#text” stuff. Let me know if you need anything else. Thanks for looking at this.
Bernie Harris
From: "Harris, Bernard T. (GSFC-5870)" <ber...@na...<mailto:ber...@na...>>
Date: Thursday, January 26, 2023 at 5:26 AM
To: Joe Wicentowski <jo...@gm...<mailto:jo...@gm...>>
Cc: Exist-open <exi...@li...<mailto:exi...@li...>>
Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes
I’m still attempting to reproduce in a minimal amount of code but it is taking a lot of time. But maybe just seeing the output will be enough for you to know what is wrong. This is a RESTXQ application and I first noticed the problem on exist 6.0.1 but have also now reproduced it on 4.4. Here is a little bit of the output
$ curl -s -H "Accept: application/json" http://localhost:8100/exist/restxq/Spase/NumericalData?ResourceID=spase://NASA/NumericalData/ACE/MAG/L2/PT16S |jq |head -15
{
"collection": {
"resource": {
"Spase": {
"xsi:schemaLocation": http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_3_2.xsd<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spase-group.org%2Fdata%2Fschema%2520%2520https%3A%2Fwww.spase-group.org%2Fdata%2Fschema%2Fspase-2_3_2.xsd&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=fIKPZfwfeBYomcQtNKigX4mnl95WBz1z9WhoIKBsU6E%3D&reserved=0>,
"#text": [
"\n ",
"\n ",
"\n"
],
"Version": "2.3.2",
"NumericalData": {
"#text": [
"\n ",
"\n ",
The problem is all the extra #text values. They don’t appear in the xml output. Years ago when I developed something similar without RESTXQ, this
declare option exist:serialize "json-ignore-whitespace-text-nodes=yes";
eliminated the extra #text stuff. But that does not work in my RESTXQ app. and it will take me more time to create a minimal RESTXQ example. I would apricate any help you can give but understand if you need example code.
Bernie
From: Joe Wicentowski <jo...@gm...<mailto:jo...@gm...>>
Date: Wednesday, January 25, 2023 at 6:07 AM
To: "Harris, Bernard T. (GSFC-5870)" <ber...@na...<mailto:ber...@na...>>
Cc: Exist-open <exi...@li...<mailto:exi...@li...>>
Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes
Could you provide more info? How to reproduce? Expected vs. actual results? What version of eXist?
On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via Exist-open <exi...@li...<mailto:exi...@li...>> wrote:
I noticed the same thing. But I was working with RESTXQ (and exist-db 6.0.1) for the first time and thought I might need to do things differently than the way it had worked in the past. I would like to know if this is a bug or if there is a different way to accomplish the same thing.
Bernie Harris
From: Eduard Drenth <ed...@fr...<mailto:ed...@fr...>>
Date: Sunday, January 22, 2023 at 11:22 AM
To: Exist-open <exi...@li...<mailto:exi...@li...>>
Subject: [EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes
json-ignore-whitespace-text-nodes not supported anymore?
Eduard Drenth, Software Architekt
ed...@fr...<mailto:ed...@fr...>
Doelestrjitte 8
8911 DX Ljouwert
(058) 213 14 14
+31 62 094 34 28
https://www.fryske-akademy.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=iKPW3w5hT7zCv%2F3FORRs7AbwmaNL%2F8Ll5EaNkkQIwns%3D&reserved=0>
https://frysker.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=9eMUDr0ES2uRkRPhhe%2FVP33hpglV1%2B8Q10JBfpWss6M%3D&reserved=0>
https://frisian.eu/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=%2B0l%2FnBilBZdzESuGGLthhiE2DERf%2BKAvBwJm3V%2FBZ3U%3D&reserved=0>
[cid:image001.png@01D9318E.2445EDE0]
gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpgp.key-server.io%2Fpks%2Flookup%3Fsearch%3Deduarddrenth&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=ilxi51ZR4iMEUnOL4MxFWG0jyflw5fmnaGXqq5KYqqA%3D&reserved=0>
_______________________________________________
Exist-open mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-open<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fexist-open&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C8eef6bc44fc249de20b008daffccc15d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638103553796310665%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=T4finZMlulTU9YjweRgqGS84auNJj9ehC3SoKcoJtZ4%3D&reserved=0>
--
Sent from my iPhone
|
|
From: Harris, B. T. (GSFC-5870) <ber...@na...> - 2023-01-26 18:47:19
|
https://cdaweb.gsfc.nasa.gov/registry/hdp/restxqJson-0.1.xar contains an example app that demonstrates my problem. Once the application is install, $ curl http://localhost:8100/exist/restxq/test { "collection" : { "resource" : { "Spase" : { "xsi:schemaLocation" : http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_4_0.xsd<http://www.spase-group.org/data/schema%20https:/www.spase-group.org/data/schema/spase-2_4_0.xsd>, "#text" : ["\n ", "\n ", "\n" ], "Version" : "2.4.0", "NumericalData" : { "#text" : ["\n ", "\n ", "\n " ], "ResourceID" : "spase://NASA/NumericalData/ACE/CRIS/L2/PT1H", "ResourceHeader" : { "#text" : ["\n ", "\n ", "\n ", "\n " ], "ResourceName" : "ACE Cosmic Ray Isotope Spectrometer (CRIS) 1-Hour Level 2 Data", "DOI" : https://doi.org/10.48322/g72t-0814, "ReleaseDate" : "2022-05-17T12:34:56.789" } } } } } Demonstrates the problem. If you change the code to let $example := 2 so that the xml does not come from the db, the json will not contain all the “#text” stuff. Let me know if you need anything else. Thanks for looking at this. Bernie Harris From: "Harris, Bernard T. (GSFC-5870)" <ber...@na...> Date: Thursday, January 26, 2023 at 5:26 AM To: Joe Wicentowski <jo...@gm...> Cc: Exist-open <exi...@li...> Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes I’m still attempting to reproduce in a minimal amount of code but it is taking a lot of time. But maybe just seeing the output will be enough for you to know what is wrong. This is a RESTXQ application and I first noticed the problem on exist 6.0.1 but have also now reproduced it on 4.4. Here is a little bit of the output $ curl -s -H "Accept: application/json" http://localhost:8100/exist/restxq/Spase/NumericalData?ResourceID=spase://NASA/NumericalData/ACE/MAG/L2/PT16S |jq |head -15 { "collection": { "resource": { "Spase": { "xsi:schemaLocation": http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_3_2.xsd<http://www.spase-group.org/data/schema%20%20https:/www.spase-group.org/data/schema/spase-2_3_2.xsd>, "#text": [ "\n ", "\n ", "\n" ], "Version": "2.3.2", "NumericalData": { "#text": [ "\n ", "\n ", The problem is all the extra #text values. They don’t appear in the xml output. Years ago when I developed something similar without RESTXQ, this declare option exist:serialize "json-ignore-whitespace-text-nodes=yes"; eliminated the extra #text stuff. But that does not work in my RESTXQ app. and it will take me more time to create a minimal RESTXQ example. I would apricate any help you can give but understand if you need example code. Bernie From: Joe Wicentowski <jo...@gm...> Date: Wednesday, January 25, 2023 at 6:07 AM To: "Harris, Bernard T. (GSFC-5870)" <ber...@na...> Cc: Exist-open <exi...@li...> Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes Could you provide more info? How to reproduce? Expected vs. actual results? What version of eXist? On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via Exist-open <exi...@li...<mailto:exi...@li...>> wrote: I noticed the same thing. But I was working with RESTXQ (and exist-db 6.0.1) for the first time and thought I might need to do things differently than the way it had worked in the past. I would like to know if this is a bug or if there is a different way to accomplish the same thing. Bernie Harris From: Eduard Drenth <ed...@fr...<mailto:ed...@fr...>> Date: Sunday, January 22, 2023 at 11:22 AM To: Exist-open <exi...@li...<mailto:exi...@li...>> Subject: [EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes json-ignore-whitespace-text-nodes not supported anymore? Eduard Drenth, Software Architekt ed...@fr...<mailto:ed...@fr...> Doelestrjitte 8 8911 DX Ljouwert (058) 213 14 14 +31 62 094 34 28 https://www.fryske-akademy.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0O1QGHF%2FoYAWVIsHuJpNXaBG5Pwmyt41aNnjYAtEt7I%3D&reserved=0> https://frysker.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=y%2F5CFfYDWLmNlEf8MfDuI2zr6SWF%2FQY8R8bnttYLGzo%3D&reserved=0> https://frisian.eu/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=suopw7zfA7r3EW4%2FFt1aLlEMe2iQl%2BjX7JREqXeT7uw%3D&reserved=0> [cid:image001.png@01D9318A.A0B62600] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpgp.key-server.io%2Fpks%2Flookup%3Fsearch%3Deduarddrenth&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XcyiU9dnfYQGMDlFxq%2FUZKND0Xmo4xkbFq3lv5nqwa8%3D&reserved=0> _______________________________________________ Exist-open mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fexist-open&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bvDGOROh5LtgzYwxDnv8NHx7lgfsZFPUVTfD6BRYL5k%3D&reserved=0> -- Sent from my iPhone |
|
From: Joe W. <jo...@gm...> - 2023-01-26 18:40:11
|
Hi Bernie, Did you by chance see my earlier response with links to code demonstrating how to use the json-ignore-whitespace-text-nodes property? Joe On Thu, Jan 26, 2023 at 1:32 PM Harris, Bernard T. (GSFC-5870) < ber...@na...> wrote: > https://cdaweb.gsfc.nasa.gov/registry/hdp/restxqJson-0.1.xar > > contains an example app that demonstrates my problem. Once the > application is install, > > > > $ curl http://localhost:8100/exist/restxq/test > > { "collection" : { "resource" : { "Spase" : { "xsi:schemaLocation" : http://www.spase-group.org/data/schema > https://www.spase-group.org/data/schema/spase-2_4_0.xsd > <http://www.spase-group.org/data/schema%20https:/www.spase-group.org/data/schema/spase-2_4_0.xsd>, > "#text" : ["\n ", "\n ", "\n" ], "Version" : "2.4.0", "NumericalData" : > { "#text" : ["\n ", "\n ", "\n " ], "ResourceID" : > "spase://NASA/NumericalData/ACE/CRIS/L2/PT1H", "ResourceHeader" : { "#text" > : ["\n ", "\n ", "\n ", "\n " ], > "ResourceName" : "ACE Cosmic Ray Isotope Spectrometer (CRIS) 1-Hour Level 2 > Data", "DOI" : https://doi.org/10.48322/g72t-0814, "ReleaseDate" : > "2022-05-17T12:34:56.789" } } } } } > > > > Demonstrates the problem. If you change the code to > > let $example := 2 > > so that the xml does not come from the db, the json will not contain all > the “#text” stuff. Let me know if you need anything else. Thanks for > looking at this. > > > > Bernie Harris > > > > *From: *"Harris, Bernard T. (GSFC-5870)" <ber...@na...> > *Date: *Thursday, January 26, 2023 at 5:26 AM > *To: *Joe Wicentowski <jo...@gm...> > *Cc: *Exist-open <exi...@li...> > *Subject: *Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes > > > > I’m still attempting to reproduce in a minimal amount of code but it is > taking a lot of time. But maybe just seeing the output will be enough for > you to know what is wrong. This is a RESTXQ application and I first > noticed the problem on exist 6.0.1 but have also now reproduced it on 4.4. > Here is a little bit of the output > > > > $ curl -s -H "Accept: application/json" > http://localhost:8100/exist/restxq/Spase/NumericalData?ResourceID=spase://NASA/NumericalData/ACE/MAG/L2/PT16S > |jq |head -15 > > { > > "collection": { > > "resource": { > > "Spase": { > > "xsi:schemaLocation": http://www.spase-group.org/data/schema > https://www.spase-group.org/data/schema/spase-2_3_2.xsd > <http://www.spase-group.org/data/schema%20%20https:/www.spase-group.org/data/schema/spase-2_3_2.xsd> > , > > "#text": [ > > "\n ", > > "\n ", > > "\n" > > ], > > "Version": "2.3.2", > > "NumericalData": { > > "#text": [ > > "\n ", > > "\n ", > > > > The problem is all the extra #text values. They don’t appear in the xml > output. Years ago when I developed something similar without RESTXQ, this > > > > declare option exist:serialize "json-ignore-whitespace-text-nodes=yes"; > > > > eliminated the extra #text stuff. But that does not work in my RESTXQ > app. and it will take me more time to create a minimal RESTXQ example. I > would apricate any help you can give but understand if you need example > code. > > > > Bernie > > > > *From: *Joe Wicentowski <jo...@gm...> > *Date: *Wednesday, January 25, 2023 at 6:07 AM > *To: *"Harris, Bernard T. (GSFC-5870)" <ber...@na...> > *Cc: *Exist-open <exi...@li...> > *Subject: *Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes > > > > Could you provide more info? How to reproduce? Expected vs. actual > results? What version of eXist? > > > > On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via > Exist-open <exi...@li...> wrote: > > I noticed the same thing. But I was working with RESTXQ (and exist-db > 6.0.1) for the first time and thought I might need to do things differently > than the way it had worked in the past. I would like to know if this is a > bug or if there is a different way to accomplish the same thing. > > > > Bernie Harris > > > > *From: *Eduard Drenth <ed...@fr...> > *Date: *Sunday, January 22, 2023 at 11:22 AM > *To: *Exist-open <exi...@li...> > *Subject: *[EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes > > > > json-ignore-whitespace-text-nodes not supported anymore? > > > > > > > > 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0O1QGHF%2FoYAWVIsHuJpNXaBG5Pwmyt41aNnjYAtEt7I%3D&reserved=0> > > https://frysker.nl/ > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=y%2F5CFfYDWLmNlEf8MfDuI2zr6SWF%2FQY8R8bnttYLGzo%3D&reserved=0> > > https://frisian.eu/ > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=suopw7zfA7r3EW4%2FFt1aLlEMe2iQl%2BjX7JREqXeT7uw%3D&reserved=0> > > gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth > <https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpgp.key-server.io%2Fpks%2Flookup%3Fsearch%3Deduarddrenth&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XcyiU9dnfYQGMDlFxq%2FUZKND0Xmo4xkbFq3lv5nqwa8%3D&reserved=0> > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fexist-open&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bvDGOROh5LtgzYwxDnv8NHx7lgfsZFPUVTfD6BRYL5k%3D&reserved=0> > > -- > > Sent from my iPhone > |
|
From: Harris, B. T. (GSFC-5870) <ber...@na...> - 2023-01-26 13:01:12
|
I’m still attempting to reproduce in a minimal amount of code but it is taking a lot of time. But maybe just seeing the output will be enough for you to know what is wrong. This is a RESTXQ application and I first noticed the problem on exist 6.0.1 but have also now reproduced it on 4.4. Here is a little bit of the output
$ curl -s -H "Accept: application/json" http://localhost:8100/exist/restxq/Spase/NumericalData?ResourceID=spase://NASA/NumericalData/ACE/MAG/L2/PT16S |jq |head -15
{
"collection": {
"resource": {
"Spase": {
"xsi:schemaLocation": http://www.spase-group.org/data/schema https://www.spase-group.org/data/schema/spase-2_3_2.xsd<http://www.spase-group.org/data/schema%20%20https:/www.spase-group.org/data/schema/spase-2_3_2.xsd>,
"#text": [
"\n ",
"\n ",
"\n"
],
"Version": "2.3.2",
"NumericalData": {
"#text": [
"\n ",
"\n ",
The problem is all the extra #text values. They don’t appear in the xml output. Years ago when I developed something similar without RESTXQ, this
declare option exist:serialize "json-ignore-whitespace-text-nodes=yes";
eliminated the extra #text stuff. But that does not work in my RESTXQ app. and it will take me more time to create a minimal RESTXQ example. I would apricate any help you can give but understand if you need example code.
Bernie
From: Joe Wicentowski <jo...@gm...>
Date: Wednesday, January 25, 2023 at 6:07 AM
To: "Harris, Bernard T. (GSFC-5870)" <ber...@na...>
Cc: Exist-open <exi...@li...>
Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes
Could you provide more info? How to reproduce? Expected vs. actual results? What version of eXist?
On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via Exist-open <exi...@li...<mailto:exi...@li...>> wrote:
I noticed the same thing. But I was working with RESTXQ (and exist-db 6.0.1) for the first time and thought I might need to do things differently than the way it had worked in the past. I would like to know if this is a bug or if there is a different way to accomplish the same thing.
Bernie Harris
From: Eduard Drenth <ed...@fr...<mailto:ed...@fr...>>
Date: Sunday, January 22, 2023 at 11:22 AM
To: Exist-open <exi...@li...<mailto:exi...@li...>>
Subject: [EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes
json-ignore-whitespace-text-nodes not supported anymore?
Eduard Drenth, Software Architekt
ed...@fr...<mailto:ed...@fr...>
Doelestrjitte 8
8911 DX Ljouwert
(058) 213 14 14
+31 62 094 34 28
https://www.fryske-akademy.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0O1QGHF%2FoYAWVIsHuJpNXaBG5Pwmyt41aNnjYAtEt7I%3D&reserved=0>
https://frysker.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=y%2F5CFfYDWLmNlEf8MfDuI2zr6SWF%2FQY8R8bnttYLGzo%3D&reserved=0>
https://frisian.eu/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=suopw7zfA7r3EW4%2FFt1aLlEMe2iQl%2BjX7JREqXeT7uw%3D&reserved=0>
[cid:image001.png@01D93146.B2DEADF0]
gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpgp.key-server.io%2Fpks%2Flookup%3Fsearch%3Deduarddrenth&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XcyiU9dnfYQGMDlFxq%2FUZKND0Xmo4xkbFq3lv5nqwa8%3D&reserved=0>
_______________________________________________
Exist-open mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-open<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fexist-open&data=05%7C01%7Cbernard.t.harris%40nasa.gov%7C7e5a6f8b6e754f7436e608dafec43f34%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638102416673638149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bvDGOROh5LtgzYwxDnv8NHx7lgfsZFPUVTfD6BRYL5k%3D&reserved=0>
--
Sent from my iPhone
|
|
From: Eduard D. <ed...@fr...> - 2023-01-26 10:31:37
|
Thanks for your response, it pointed me to what the problem was: output:json-ignore-whitespace-text-nodes => exist:json-ignore-whitespace-text-nodes Regards, 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:f4170f80-6d2d-410c-b4fc-1d1f1430a12a] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth ________________________________ From: Joe Wicentowski <jo...@gm...> Sent: Wednesday, January 25, 2023 7:46 PM To: Eduard Drenth <ed...@fr...> Cc: Harris, Bernard T. (GSFC-5870) <ber...@na...>; Exist-open <exi...@li...> Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes Hi Eduard, By examining the tests included in the eXist source, I found an example that exercises the serialization method that you're using. Here's code that demonstrates how to use it. https://gist.github.com/joewiz/4f06d44794a268d2b262034b31eac5c4 The relevant PR that enabled the use of these eXist-specific serialization methods in fn:serialize() is: https://github.com/eXist-db/exist/issues/2394 Joe On Wed, Jan 25, 2023 at 12:46 PM Joe Wicentowski <jo...@gm...<mailto:jo...@gm...>> wrote: Besides your script not failing, what is the actual expected result? On Wed, Jan 25, 2023 at 10:03 AM Eduard Drenth <ed...@fr...<mailto:ed...@fr...>> wrote: declare variable $teidictjson:jsonparams := <output:serialization-parameters xmlns:output="http://www.w3.org/2010/xslt-xquery-serialization"> <output:method value="json"/> <output:json-ignore-whitespace-text-nodes value="yes"/> </output:serialization-parameters>; fn:serialize(<noresults>no results</noresults>,$teidictjson:jsonparams) In 6.1.0 the above fails Eduard Drenth, Software Architekt ed...@fr...<mailto: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:185ea095e6fbabbb33e2] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth<http://pgp.key-server.io/pks/lookup?search=eduarddrenth> ________________________________ From: Joe Wicentowski <jo...@gm...<mailto:jo...@gm...>> Sent: Wednesday, January 25, 2023 12:06 PM To: Harris, Bernard T. (GSFC-5870) <ber...@na...<mailto:ber...@na...>> Cc: Exist-open <exi...@li...<mailto:exi...@li...>> Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes Could you provide more info? How to reproduce? Expected vs. actual results? What version of eXist? On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via Exist-open <exi...@li...<mailto:exi...@li...>> wrote: I noticed the same thing. But I was working with RESTXQ (and exist-db 6.0.1) for the first time and thought I might need to do things differently than the way it had worked in the past. I would like to know if this is a bug or if there is a different way to accomplish the same thing. Bernie Harris From: Eduard Drenth <ed...@fr...<mailto:ed...@fr...>> Date: Sunday, January 22, 2023 at 11:22 AM To: Exist-open <exi...@li...<mailto:exi...@li...>> Subject: [EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes json-ignore-whitespace-text-nodes not supported anymore? Eduard Drenth, Software Architekt ed...@fr...<mailto:ed...@fr...> Doelestrjitte 8 8911 DX Ljouwert (058) 213 14 14 +31 62 094 34 28 https://www.fryske-akademy.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=GHeHpN59VC5xjXYZv%2FTqgld4HFzVtNe4O0eZnJRM4og%3D&reserved=0> https://frysker.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=VLqoS94QI7sj5wR0WQ%2FLz20atSzleWdn7HMydkykkF0%3D&reserved=0> https://frisian.eu/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=NZHee7QsEXzXI0OmaS7aEhIX%2BTCUlil3o9icruakOGY%3D&reserved=0> [cid:185ea095e6f4cff311] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth<http://pgp.key-server.io/pks/lookup?search=eduarddrenth> _______________________________________________ Exist-open mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open -- Sent from my iPhone |
|
From: Adam R. <ad...@ex...> - 2023-01-25 22:17:47
|
Regards XSLT it should not be... However I was investigating an issue whereby twice as much work for XSLT compilation is done - https://github.com/eXist-db/exist/issues/4691 On Mon, 23 Jan 2023, 13:27 Eduard Drenth, <ed...@fr...> wrote: > Dear all, > > Can it be that 6.1.0 exist-db is significantly slower (twice as slow at > least) compared to 6.0.1? > > I am running: > > > > > 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: pgp.key-server.io/pks/lookup?search=eduarddrenth > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Eduard D. <ed...@fr...> - 2023-01-25 18:58:19
|
More specific performance question as follow-up on the previous. For one of my apps I use xslt to output html, it is being called many times with different nodes as input. The xslt is rather simple, no expensive stuff. In my module I "cache" the stylesheet like this: declare variable $teidictapp:teiToHtmlxslt := doc($config:app-root||"/teiToHtml.xslt"); The many calls to this stylesheet make up a big portion of total processing time. Are there ways to speed up xslt processing in exist-db? Are stylesheets cached and templates reused under the hood in Java? Regards, 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:ba445708-3750-4b0a-a408-338f86bead3a] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth ________________________________ From: Eduard Drenth <ed...@fr...> Sent: Monday, January 23, 2023 1:51 PM To: Exist-open <exi...@li...> Subject: [Exist-open] performance 6.1.0 Dear all, Can it be that 6.1.0 exist-db is significantly slower (twice as slow at least) compared to 6.0.1? I am running: [cid:4551aa26-680a-4f73-a0cd-9d07c07efee9] 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:3ae03765-821d-44e7-b05c-bf70259d6d51] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth |
|
From: Joe W. <jo...@gm...> - 2023-01-25 18:46:55
|
Hi Eduard, By examining the tests included in the eXist source, I found an example that exercises the serialization method that you're using. Here's code that demonstrates how to use it. https://gist.github.com/joewiz/4f06d44794a268d2b262034b31eac5c4 The relevant PR that enabled the use of these eXist-specific serialization methods in fn:serialize() is: https://github.com/eXist-db/exist/issues/2394 Joe On Wed, Jan 25, 2023 at 12:46 PM Joe Wicentowski <jo...@gm...> wrote: > Besides your script not failing, what is the actual expected result? > > On Wed, Jan 25, 2023 at 10:03 AM Eduard Drenth <ed...@fr...> > wrote: > >> declare variable $teidictjson:jsonparams := <output:serialization-parameters xmlns:output="http://www.w3.org/2010/xslt-xquery-serialization"> >> >> <output:method value="json"/> >> <output:json-ignore-whitespace-text-nodes value="yes"/> >> </output:serialization-parameters>; >> >> fn:serialize(<noresults>no results</noresults>,$teidictjson:jsonparams) >> >> In 6.1.0 the above fails >> >> >> >> 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: pgp.key-server.io/pks/lookup?search=eduarddrenth >> ------------------------------ >> *From:* Joe Wicentowski <jo...@gm...> >> *Sent:* Wednesday, January 25, 2023 12:06 PM >> *To:* Harris, Bernard T. (GSFC-5870) <ber...@na...> >> *Cc:* Exist-open <exi...@li...> >> *Subject:* Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes >> >> Could you provide more info? How to reproduce? Expected vs. actual >> results? What version of eXist? >> >> On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via >> Exist-open <exi...@li...> wrote: >> >> I noticed the same thing. But I was working with RESTXQ (and exist-db >> 6.0.1) for the first time and thought I might need to do things differently >> than the way it had worked in the past. I would like to know if this is a >> bug or if there is a different way to accomplish the same thing. >> >> >> >> Bernie Harris >> >> >> >> *From: *Eduard Drenth <ed...@fr...> >> *Date: *Sunday, January 22, 2023 at 11:22 AM >> *To: *Exist-open <exi...@li...> >> *Subject: *[EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes >> >> >> >> json-ignore-whitespace-text-nodes not supported anymore? >> >> >> >> >> >> >> >> 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=GHeHpN59VC5xjXYZv%2FTqgld4HFzVtNe4O0eZnJRM4og%3D&reserved=0> >> >> https://frysker.nl/ >> <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=VLqoS94QI7sj5wR0WQ%2FLz20atSzleWdn7HMydkykkF0%3D&reserved=0> >> >> https://frisian.eu/ >> <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=NZHee7QsEXzXI0OmaS7aEhIX%2BTCUlil3o9icruakOGY%3D&reserved=0> >> >> gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> >> -- >> Sent from my iPhone >> > |
|
From: Joe W. <jo...@gm...> - 2023-01-25 17:46:48
|
Besides your script not failing, what is the actual expected result? On Wed, Jan 25, 2023 at 10:03 AM Eduard Drenth <ed...@fr...> wrote: > declare variable $teidictjson:jsonparams := <output:serialization-parameters xmlns:output="http://www.w3.org/2010/xslt-xquery-serialization"> > > <output:method value="json"/> > <output:json-ignore-whitespace-text-nodes value="yes"/> > </output:serialization-parameters>; > > fn:serialize(<noresults>no results</noresults>,$teidictjson:jsonparams) > > In 6.1.0 the above fails > > > > 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: pgp.key-server.io/pks/lookup?search=eduarddrenth > ------------------------------ > *From:* Joe Wicentowski <jo...@gm...> > *Sent:* Wednesday, January 25, 2023 12:06 PM > *To:* Harris, Bernard T. (GSFC-5870) <ber...@na...> > *Cc:* Exist-open <exi...@li...> > *Subject:* Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes > > Could you provide more info? How to reproduce? Expected vs. actual > results? What version of eXist? > > On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via > Exist-open <exi...@li...> wrote: > > I noticed the same thing. But I was working with RESTXQ (and exist-db > 6.0.1) for the first time and thought I might need to do things differently > than the way it had worked in the past. I would like to know if this is a > bug or if there is a different way to accomplish the same thing. > > > > Bernie Harris > > > > *From: *Eduard Drenth <ed...@fr...> > *Date: *Sunday, January 22, 2023 at 11:22 AM > *To: *Exist-open <exi...@li...> > *Subject: *[EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes > > > > json-ignore-whitespace-text-nodes not supported anymore? > > > > > > > > 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=GHeHpN59VC5xjXYZv%2FTqgld4HFzVtNe4O0eZnJRM4og%3D&reserved=0> > > https://frysker.nl/ > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=VLqoS94QI7sj5wR0WQ%2FLz20atSzleWdn7HMydkykkF0%3D&reserved=0> > > https://frisian.eu/ > <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=NZHee7QsEXzXI0OmaS7aEhIX%2BTCUlil3o9icruakOGY%3D&reserved=0> > > gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > -- > Sent from my iPhone > |
|
From: Eduard D. <ed...@fr...> - 2023-01-25 15:36:04
|
declare variable $teidictjson:jsonparams := <output:serialization-parameters xmlns:output="http://www.w3.org/2010/xslt-xquery-serialization"> <output:method value="json"/> <output:json-ignore-whitespace-text-nodes value="yes"/> </output:serialization-parameters>; fn:serialize(<noresults>no results</noresults>,$teidictjson:jsonparams) In 6.1.0 the above fails 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:24465444-763d-4dfe-91c2-ba81bee19fe6] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth ________________________________ From: Joe Wicentowski <jo...@gm...> Sent: Wednesday, January 25, 2023 12:06 PM To: Harris, Bernard T. (GSFC-5870) <ber...@na...> Cc: Exist-open <exi...@li...> Subject: Re: [Exist-open] [EXTERNAL] json-ignore-whitespace-text-nodes Could you provide more info? How to reproduce? Expected vs. actual results? What version of eXist? On Wed, Jan 25, 2023 at 5:39 AM Harris, Bernard T. (GSFC-5870) via Exist-open <exi...@li...<mailto:exi...@li...>> wrote: I noticed the same thing. But I was working with RESTXQ (and exist-db 6.0.1) for the first time and thought I might need to do things differently than the way it had worked in the past. I would like to know if this is a bug or if there is a different way to accomplish the same thing. Bernie Harris From: Eduard Drenth <ed...@fr...<mailto:ed...@fr...>> Date: Sunday, January 22, 2023 at 11:22 AM To: Exist-open <exi...@li...<mailto:exi...@li...>> Subject: [EXTERNAL] [Exist-open] json-ignore-whitespace-text-nodes json-ignore-whitespace-text-nodes not supported anymore? Eduard Drenth, Software Architekt ed...@fr...<mailto:ed...@fr...> Doelestrjitte 8 8911 DX Ljouwert (058) 213 14 14 +31 62 094 34 28 https://www.fryske-akademy.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fryske-akademy.nl%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=GHeHpN59VC5xjXYZv%2FTqgld4HFzVtNe4O0eZnJRM4og%3D&reserved=0> https://frysker.nl/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrysker.nl%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=VLqoS94QI7sj5wR0WQ%2FLz20atSzleWdn7HMydkykkF0%3D&reserved=0> https://frisian.eu/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrisian.eu%2F&data=05%7C01%7CBernard.T.Harris%40nasa.gov%7C0bf6fca97ad74a78833108dafc94d22f%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638100013365653479%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=NZHee7QsEXzXI0OmaS7aEhIX%2BTCUlil3o9icruakOGY%3D&reserved=0> [cid:185e89a12d2ad7999131] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth<http://pgp.key-server.io/pks/lookup?search=eduarddrenth> _______________________________________________ Exist-open mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open -- Sent from my iPhone |
|
From: Eduard D. <ed...@fr...> - 2023-01-23 13:27:15
|
Dear all, Can it be that 6.1.0 exist-db is significantly slower (twice as slow at least) compared to 6.0.1? I am running: [cid:4551aa26-680a-4f73-a0cd-9d07c07efee9] 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:3ae03765-821d-44e7-b05c-bf70259d6d51] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth |
|
From: Eduard D. <ed...@fr...> - 2023-01-22 16:19:51
|
json-ignore-whitespace-text-nodes not supported anymore? 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:81af706a-ce67-47b7-a9de-80010cc6f16f] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth |
|
From: Eduard D. <ed...@fr...> - 2023-01-16 16:03:32
|
Since 6.1.0 is out, CONGRATS!, I'll try if below issue still exists... Regards, 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:a2247bbe-3aff-4c9d-b685-3a463ae59c47] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth ________________________________ From: Eduard Drenth <ed...@fr...> Sent: Thursday, January 12, 2023 1:45 PM To: Exist-open <exi...@li...> Subject: [Exist-open] problem with nodes Dear all, We have dictionary applications running in exist-db, latest version. Users only read from the applications. The only writing is done by syncing data from filesystem to exist-db using https://bitbucket.org/fryske-akademy/exist-db-addons/src/master/src/main/java/org/fryske_akademy/exist/jobs/DataSyncTask.java. Regularly the log shows problems like this: WARN (EmbeddedXMLStreamReader.java [verifyOriginNodeId]:241) - Expected node id 1.3.2.6.4.3.4, got 1.5.2.2.2.20.5.1; resyncing address WARN (EmbeddedXMLStreamReader.java [verifyOriginNodeId]:241) - Expected node id 1.3.2.6.4, got 1.5.2.2.2.18.12; resyncing address ERROR (VirtualNodeSet.java [addChildren]:529) - javax.xml.stream.XMLStreamException: java.io.IOException: Node not found. When, under what circumstances, might these problems likely occur? Regards, 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:08d11238-1c07-4b95-9f15-6dd966f35bd0] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth |
|
From: Adam R. <ad...@ex...> - 2023-01-16 14:53:59
|
I would like to make the community aware that the mainline of development for eXist-db will soon move from the 6.x.x series to the 7.x.x. series. As such the develop branch of the eXist-db GitHub repository (i.e. https://github.com/exist-db/exist/tree/develop) will be updated by Thursday 19th January to bump the current version number from 6.2.0-SNAPSHOT to 7.0.0-SNAPSHOT. After that we will also start merging into the develop branch outstanding Pull Requests that target eXist-db 7.0.0. As always the eXist-db project follows the SemVer 2.0.0 standard of versioning (https://semver.org/), and so a major version change, i.e. 6.x.x to 7.x.x indicates a version of eXist-db that has non-backwards-compatible changes. This is only of note to you, if for some reason you are dependent on building from the develop branch. If that is the case, we would consider setting up a develop-6.x.x branch... please just contact Adam Retter <ad...@ev...> to discuss it. Kind regards. Adam. -- Adam Retter eXist Core Developer { United Kingdom } ad...@ex... |
|
From: Nick S. <nsi...@nu...> - 2023-01-15 22:21:50
|
Congratulations and a big thank you to all the contributors who made this release a reality. I am eager to give this new version a try! Best regards, Nick On 1/15/23 9:00 AM, Adam Retter wrote: > Dear eXist-db users, > > After almost a year since our last releases, I am delighted to > announce the release of eXist-db versions 6.1.0, 5.5.1, and 4.11.1. > > eXist-db 6.x.x is our main active line of development, and we have > recommended this version series for all users for some time now. > eXist-db 6.1.0 includes numerous improvements, optimisations, and bug > fixes. In particular it adds a number of additional functions from > XQuery 3.1 that were previously missing, including: fn:transform, > fn:default-language, fn:format-integer, fn:round, fn:path, > fn:collation-key, fn:n:element-with-id, fn:nilled, fn:uri-collection, > andmap:find. With these additions, eXist-db 6.1.0 now supports all > XQuery 3.1 functions. > > For those users already on the 6.x.x series, eXist-db 6.1.0 is > backwards binary compatible with previous 6.x.x versions, which should > make upgrading simple with no changes required to XQuery or XSLT > application code. For those users migrating from 4.x.x or 5.x.x > versions to 6.x.x a full backup and restore of the database will be > required and possibly some small changes to XQuery and XSLT > application code. > > The 4.x.x and 5.x.x series of eXist-db should be considered > deprecated, our new releases of 4.x.x and 5.x.x include a number of > crucial bug fixes for those users who cannot yet upgrade to 6.x.x. The > 5.x.x series also includes a small handful of selected features and > improvements that have been backported from the 6.x.x series. > > Finally, for those users considering a major upgrade from 4.x.x or > 5.x.x to 6.x.x, you may wish to wait for the upcoming release of > eXist-db 7.0.0. This release will update eXist-db from Java 8 to Java > 17, and greatly improve its XQuery compliance with the W3C > specifications. The improvements in compliance mean that some small > changes to your XQuery application code may be required, but we > believe that this is most worthwhile. We expect to release eXist-db > 7.0.0 with Q1 of 2023. > > The full release notes and downloads can be found here: > > 1. eXist-db 6.1.0 -https://github.com/eXist-db/exist/releases/tag/eXist-6.1.0 > > 2. eXist-db 5.5.1 -https://github.com/eXist-db/exist/releases/tag/eXist-5.5.1 > > 3. eXist-db 4.11.1 -https://github.com/eXist-db/exist/releases/tag/eXist-4.11.1 > > As well as thanking all contributors, I would also like to especially > thank the Office of the Historian, U.S. Department of State, > https://history.state.gov, which commissioned several of the > improvements in eXist 6.1.0 through Evolved Binary > https://www.evolvedbinary.com and eXist Solutions > https://www.existsolutions.com, and worked with Evolved Binary to make > this release a reality. > > Best wishes. Adam. > -- Nick Sincaglia President/Founder NueMeta, LLC Digital Media & Technology Phone: +1-630-303-7035 nsi...@nu... http://www.nuemeta.com Skype: nsincaglia |
|
From: Ari N. <ari...@gm...> - 2023-01-15 15:36:10
|
Congrats and thanks for your hard work, to everyone involved! Best, /Ari On 2023-01-15 16:00, Adam Retter wrote: > Dear eXist-db users, > > After almost a year since our last releases, I am delighted to > announce the release of eXist-db versions 6.1.0, 5.5.1, and 4.11.1. > > eXist-db 6.x.x is our main active line of development, and we have > recommended this version series for all users for some time now. > eXist-db 6.1.0 includes numerous improvements, optimisations, and bug > fixes. In particular it adds a number of additional functions from > XQuery 3.1 that were previously missing, including: fn:transform, > fn:default-language, fn:format-integer, fn:round, fn:path, > fn:collation-key, fn:n:element-with-id, fn:nilled, fn:uri-collection, > and map:find. With these additions, eXist-db 6.1.0 now supports all > XQuery 3.1 functions. > > For those users already on the 6.x.x series, eXist-db 6.1.0 is > backwards binary compatible with previous 6.x.x versions, which should > make upgrading simple with no changes required to XQuery or XSLT > application code. For those users migrating from 4.x.x or 5.x.x > versions to 6.x.x a full backup and restore of the database will be > required and possibly some small changes to XQuery and XSLT > application code. > > The 4.x.x and 5.x.x series of eXist-db should be considered > deprecated, our new releases of 4.x.x and 5.x.x include a number of > crucial bug fixes for those users who cannot yet upgrade to 6.x.x. The > 5.x.x series also includes a small handful of selected features and > improvements that have been backported from the 6.x.x series. > > Finally, for those users considering a major upgrade from 4.x.x or > 5.x.x to 6.x.x, you may wish to wait for the upcoming release of > eXist-db 7.0.0. This release will update eXist-db from Java 8 to Java > 17, and greatly improve its XQuery compliance with the W3C > specifications. The improvements in compliance mean that some small > changes to your XQuery application code may be required, but we > believe that this is most worthwhile. We expect to release eXist-db > 7.0.0 with Q1 of 2023. > > The full release notes and downloads can be found here: > > 1. eXist-db 6.1.0 - https://github.com/eXist-db/exist/releases/tag/eXist-6.1.0 > > 2. eXist-db 5.5.1 - https://github.com/eXist-db/exist/releases/tag/eXist-5.5.1 > > 3. eXist-db 4.11.1 - https://github.com/eXist-db/exist/releases/tag/eXist-4.11.1 > > As well as thanking all contributors, I would also like to especially > thank the Office of the Historian, U.S. Department of State, > https://history.state.gov, which commissioned several of the > improvements in eXist 6.1.0 through Evolved Binary > https://www.evolvedbinary.com and eXist Solutions > https://www.existsolutions.com, and worked with Evolved Binary to make > this release a reality. > > Best wishes. Adam. > |
|
From: Joe W. <jo...@gm...> - 2023-01-15 15:34:42
|
Hi all, A huge thanks to all of the developers who contributed to these releases! Congratulations for helping make eXist 6.1.0 the first release of eXist that supports all XQuery 3.1 functions—among other great improvements and important fixes. Joe On Sun, Jan 15, 2023 at 10:27 AM Adam Retter <ad...@ex...> wrote: > Dear eXist-db users, > > After almost a year since our last releases, I am delighted to > announce the release of eXist-db versions 6.1.0, 5.5.1, and 4.11.1. > > eXist-db 6.x.x is our main active line of development, and we have > recommended this version series for all users for some time now. > eXist-db 6.1.0 includes numerous improvements, optimisations, and bug > fixes. In particular it adds a number of additional functions from > XQuery 3.1 that were previously missing, including: fn:transform, > fn:default-language, fn:format-integer, fn:round, fn:path, > fn:collation-key, fn:n:element-with-id, fn:nilled, fn:uri-collection, > and map:find. With these additions, eXist-db 6.1.0 now supports all > XQuery 3.1 functions. > > For those users already on the 6.x.x series, eXist-db 6.1.0 is > backwards binary compatible with previous 6.x.x versions, which should > make upgrading simple with no changes required to XQuery or XSLT > application code. For those users migrating from 4.x.x or 5.x.x > versions to 6.x.x a full backup and restore of the database will be > required and possibly some small changes to XQuery and XSLT > application code. > > The 4.x.x and 5.x.x series of eXist-db should be considered > deprecated, our new releases of 4.x.x and 5.x.x include a number of > crucial bug fixes for those users who cannot yet upgrade to 6.x.x. The > 5.x.x series also includes a small handful of selected features and > improvements that have been backported from the 6.x.x series. > > Finally, for those users considering a major upgrade from 4.x.x or > 5.x.x to 6.x.x, you may wish to wait for the upcoming release of > eXist-db 7.0.0. This release will update eXist-db from Java 8 to Java > 17, and greatly improve its XQuery compliance with the W3C > specifications. The improvements in compliance mean that some small > changes to your XQuery application code may be required, but we > believe that this is most worthwhile. We expect to release eXist-db > 7.0.0 with Q1 of 2023. > > The full release notes and downloads can be found here: > > 1. eXist-db 6.1.0 - > https://github.com/eXist-db/exist/releases/tag/eXist-6.1.0 > > 2. eXist-db 5.5.1 - > https://github.com/eXist-db/exist/releases/tag/eXist-5.5.1 > > 3. eXist-db 4.11.1 - > https://github.com/eXist-db/exist/releases/tag/eXist-4.11.1 > > As well as thanking all contributors, I would also like to especially > thank the Office of the Historian, U.S. Department of State, > https://history.state.gov, which commissioned several of the > improvements in eXist 6.1.0 through Evolved Binary > https://www.evolvedbinary.com and eXist Solutions > https://www.existsolutions.com, and worked with Evolved Binary to make > this release a reality. > > Best wishes. Adam. > > -- > Adam Retter > > eXist Core Developer > { United Kingdom } > ad...@ex... > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Adam R. <ad...@ex...> - 2023-01-15 15:26:49
|
Dear eXist-db users, After almost a year since our last releases, I am delighted to announce the release of eXist-db versions 6.1.0, 5.5.1, and 4.11.1. eXist-db 6.x.x is our main active line of development, and we have recommended this version series for all users for some time now. eXist-db 6.1.0 includes numerous improvements, optimisations, and bug fixes. In particular it adds a number of additional functions from XQuery 3.1 that were previously missing, including: fn:transform, fn:default-language, fn:format-integer, fn:round, fn:path, fn:collation-key, fn:n:element-with-id, fn:nilled, fn:uri-collection, and map:find. With these additions, eXist-db 6.1.0 now supports all XQuery 3.1 functions. For those users already on the 6.x.x series, eXist-db 6.1.0 is backwards binary compatible with previous 6.x.x versions, which should make upgrading simple with no changes required to XQuery or XSLT application code. For those users migrating from 4.x.x or 5.x.x versions to 6.x.x a full backup and restore of the database will be required and possibly some small changes to XQuery and XSLT application code. The 4.x.x and 5.x.x series of eXist-db should be considered deprecated, our new releases of 4.x.x and 5.x.x include a number of crucial bug fixes for those users who cannot yet upgrade to 6.x.x. The 5.x.x series also includes a small handful of selected features and improvements that have been backported from the 6.x.x series. Finally, for those users considering a major upgrade from 4.x.x or 5.x.x to 6.x.x, you may wish to wait for the upcoming release of eXist-db 7.0.0. This release will update eXist-db from Java 8 to Java 17, and greatly improve its XQuery compliance with the W3C specifications. The improvements in compliance mean that some small changes to your XQuery application code may be required, but we believe that this is most worthwhile. We expect to release eXist-db 7.0.0 with Q1 of 2023. The full release notes and downloads can be found here: 1. eXist-db 6.1.0 - https://github.com/eXist-db/exist/releases/tag/eXist-6.1.0 2. eXist-db 5.5.1 - https://github.com/eXist-db/exist/releases/tag/eXist-5.5.1 3. eXist-db 4.11.1 - https://github.com/eXist-db/exist/releases/tag/eXist-4.11.1 As well as thanking all contributors, I would also like to especially thank the Office of the Historian, U.S. Department of State, https://history.state.gov, which commissioned several of the improvements in eXist 6.1.0 through Evolved Binary https://www.evolvedbinary.com and eXist Solutions https://www.existsolutions.com, and worked with Evolved Binary to make this release a reality. Best wishes. Adam. -- Adam Retter eXist Core Developer { United Kingdom } ad...@ex... |
|
From: Eduard D. <ed...@fr...> - 2023-01-12 12:45:48
|
Dear all, We have dictionary applications running in exist-db, latest version. Users only read from the applications. The only writing is done by syncing data from filesystem to exist-db using https://bitbucket.org/fryske-akademy/exist-db-addons/src/master/src/main/java/org/fryske_akademy/exist/jobs/DataSyncTask.java. Regularly the log shows problems like this: WARN (EmbeddedXMLStreamReader.java [verifyOriginNodeId]:241) - Expected node id 1.3.2.6.4.3.4, got 1.5.2.2.2.20.5.1; resyncing address WARN (EmbeddedXMLStreamReader.java [verifyOriginNodeId]:241) - Expected node id 1.3.2.6.4, got 1.5.2.2.2.18.12; resyncing address ERROR (VirtualNodeSet.java [addChildren]:529) - javax.xml.stream.XMLStreamException: java.io.IOException: Node not found. When, under what circumstances, might these problems likely occur? Regards, 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:08d11238-1c07-4b95-9f15-6dd966f35bd0] gpg: pgp.key-server.io/pks/lookup?search=eduarddrenth |
|
From: Juri L. <jur...@ex...> - 2023-01-09 23:38:04
|
Happy new Year! I think this was never announced here on the list, so: There is a new command line client for eXist-db called xst. If you have node >=14 available on your system you can install it with npm install -g @existdb/xst The idea is to have one client that can connect and interact with any instance that you have access to. The current version is 1.2.0 and it features a command to list all installed packages. It has a plethora of options such as filtering by type, sorting by name, type and installation date. On top of this it can list, and check, the dependencies of each package and library and reports missing or mismatching dependencies. The entire list of available commands with some examples can be found in the readme https://github.com/eXist-db/xst#readme If you like the project, leave a star :) |
|
From: Lizzi, V. <Vin...@ta...> - 2023-01-09 21:55:37
|
Hello eXist community,
I am trying to use eXist's Full Text index to speed up a query but have not been able to figure out how to construct this particular query correctly. Hopefully someone here who has more familiarity with eXist's Lucene full text index features will have some useful pointers.
The query should find text that contains at least one phrase from a set of phrases that appear in conjunction with at least one phrase from another set of phrases.
I have a regular expression that does the job like this:
matches(., "\s(jumping jack|kettle bell|push up)+\s(\S+\s){0,20}(yard|park|jungle gym|exercise machine)\s")
I've tried to construct an equivalent search using ft:query as described in the documentation at http://exist-db.org/exist/apps/doc/lucene#describe but haven't been able to construct a query that produces the expected results. The following query expresses what I think should work, but eXide gives an error saying that this query is invalid.
ft:query(.,
<query>
<near slop="20">
<bool min="1">
<phrase occur="should">jumping jack</phrase>
<phrase occur="should">kettle bell</phrase>
<phrase occur="should">push up</phrase>
</bool>
<bool min="1">
<phrase occur="should">yard</phrase>
<phrase occur="should">park</phrase>
<phrase occur="should">jungle gym</phrase>
<phrase occur="should">exercise machine</phrase>
</bool>
</near>
</query>)
If the full text index is not suitable for this kind of query I will continue using the regex approach, but I'm hoping that the full text index will work better for this query.
Thanks,
Vincent
______________________________________________
Vincent M. Lizzi
Head of Information Standards | Taylor & Francis Group
530 Walnut St., Suite 850, Philadelphia, PA 19106
E-Mail: vin...@ta...
Web: www.tandfonline.com
Taylor & Francis is a trading name of Informa UK Limited,
registered in England under no. 1072954
"Everything should be made as simple as possible, but not simpler."
Information Classification: General
|