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
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ted H. <meg...@gm...> - 2024-08-19 05:25:44
|
My apology for giving you incorrect Javascript code. I corrected my code.
Here it is:
function Setup() {
var XMLHttp;
var JSON_Data;
XMLHttp = new XMLHttpRequest();
XMLHttp.open("GET", "
http://localhost:8080/exist/rest/db/apps/HTML_Student/people.json", true);
XMLHttp.onreadystatechange = function () {
if(XMLHttp.readyState == 4){}{
JSON_Data = XMLHttp.responseText;
document.getElementById("JSON_Text").value = JSON_Data;
}
};
}
When I run the code and check the console, it states that it can't find
people.json. I don't know why my webpage can't find people.json Can you
assist me?
On Sun, Aug 18, 2024 at 11:42 AM Jean-Paul Rehr <re...@gm...> wrote:
> Ted, none of this has to do with eXist parsing JSON.
>
> The URL http://localhost:8080/exist/rest/db/apps/HTML_Student/people.json
> is requesting a JSON document from eXist, that is, eXist is serving the
> document not parsing it.
>
> Incidentally, one can parse a json document in Xquery with the command:
>
> fn:json-doc("/db/apps/HTML_Student/people.json")
>
> JPR
>
> On Sun, Aug 18, 2024 at 6:26 PM Ted Hickox <meg...@gm...> wrote:
>
>> If it's possible to parse JSON with the eXist database, why is the
>> following code retrieving any data from my JSON document:
>>
>> JSON Example.xhtml
>>
>> <html xmlns="http://www.w3.org/1999/xhtml">
>> <head>
>> <title>First JSON Experiment</title>
>> <link rel="stylesheet" type="text/css" href="
>> http://localhost:8080/exist/rest/db/apps/HTML_Student/JSON_Example.css"/>
>> <script language="javascript" src="
>> http://localhost:8080/exist/rest/db/apps/HTML_Student/JSON_Example.js"/>
>> </head>
>> <body onload = "Setup()">
>> <input type = "text" id = "JSON_Text">
>> </input>
>> </body>
>> </html>
>>
>> JSON Example.css
>>
>> #JSON_Text {
>> position: absolute;
>> top: 200px;
>> left: 300px;
>> height: 25px;
>> width: 300px;
>> }
>>
>> JSON Example.js
>>
>> function Setup() {
>> var XMLHttp;
>> var JSON_Data;
>>
>> XMLHttp = new XMLHttpRequest();
>>
>> XMLHttp.onreadystatechange = function () {
>> if(XMLHttp.readyState == 4){
>> JSON_Data = JSON.parse(XMLHttp.responseText);
>> }
>> };
>>
>> XMLHttp.open("Get", "
>> http://localhost:8080/exist/rest/db/apps/HTML_Student/people.json",
>> true);
>> XMLHttp.send();
>>
>>
>> document.getElementById("JSON_Text").value = JSON_Data;
>> }
>>
>> People.json
>>
>> {
>> "People":{
>> {
>> "name": "Alex",
>> "online": true
>> },
>> {
>> "name": "Billy",
>> "online": false
>> }
>>
>> }
>> }
>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>
|
|
From: Jean-Paul R. <re...@gm...> - 2024-08-18 16:42:39
|
Ted, none of this has to do with eXist parsing JSON.
The URL http://localhost:8080/exist/rest/db/apps/HTML_Student/people.json
is requesting a JSON document from eXist, that is, eXist is serving the
document not parsing it.
Incidentally, one can parse a json document in Xquery with the command:
fn:json-doc("/db/apps/HTML_Student/people.json")
JPR
On Sun, Aug 18, 2024 at 6:26 PM Ted Hickox <meg...@gm...> wrote:
> If it's possible to parse JSON with the eXist database, why is the
> following code retrieving any data from my JSON document:
>
> JSON Example.xhtml
>
> <html xmlns="http://www.w3.org/1999/xhtml">
> <head>
> <title>First JSON Experiment</title>
> <link rel="stylesheet" type="text/css" href="
> http://localhost:8080/exist/rest/db/apps/HTML_Student/JSON_Example.css"/>
> <script language="javascript" src="
> http://localhost:8080/exist/rest/db/apps/HTML_Student/JSON_Example.js"/>
> </head>
> <body onload = "Setup()">
> <input type = "text" id = "JSON_Text">
> </input>
> </body>
> </html>
>
> JSON Example.css
>
> #JSON_Text {
> position: absolute;
> top: 200px;
> left: 300px;
> height: 25px;
> width: 300px;
> }
>
> JSON Example.js
>
> function Setup() {
> var XMLHttp;
> var JSON_Data;
>
> XMLHttp = new XMLHttpRequest();
>
> XMLHttp.onreadystatechange = function () {
> if(XMLHttp.readyState == 4){
> JSON_Data = JSON.parse(XMLHttp.responseText);
> }
> };
>
> XMLHttp.open("Get", "
> http://localhost:8080/exist/rest/db/apps/HTML_Student/people.json", true);
> XMLHttp.send();
>
>
> document.getElementById("JSON_Text").value = JSON_Data;
> }
>
> People.json
>
> {
> "People":{
> {
> "name": "Alex",
> "online": true
> },
> {
> "name": "Billy",
> "online": false
> }
>
> }
> }
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
|
|
From: Ted H. <meg...@gm...> - 2024-08-18 16:25:48
|
If it's possible to parse JSON with the eXist database, why is the following code retrieving any data from my JSON document: JSON Example.xhtml <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>First JSON Experiment</title> <link rel="stylesheet" type="text/css" href=" http://localhost:8080/exist/rest/db/apps/HTML_Student/JSON_Example.css"/> <script language="javascript" src=" http://localhost:8080/exist/rest/db/apps/HTML_Student/JSON_Example.js"/> </head> <body onload = "Setup()"> <input type = "text" id = "JSON_Text"> </input> </body> </html> JSON Example.css #JSON_Text { position: absolute; top: 200px; left: 300px; height: 25px; width: 300px; } JSON Example.js function Setup() { var XMLHttp; var JSON_Data; XMLHttp = new XMLHttpRequest(); XMLHttp.onreadystatechange = function () { if(XMLHttp.readyState == 4){ JSON_Data = JSON.parse(XMLHttp.responseText); } }; XMLHttp.open("Get", " http://localhost:8080/exist/rest/db/apps/HTML_Student/people.json", true); XMLHttp.send(); document.getElementById("JSON_Text").value = JSON_Data; } People.json { "People":{ { "name": "Alex", "online": true }, { "name": "Billy", "online": false } } } |
|
From: Michael W. <wes...@ja...> - 2024-08-07 00:20:27
|
Hi Ted, You have the answer of how to link to an external namespace in your first XML file. Namely, use the `xmlns:xsi` and `xsi:schemaLocation` to point to an instance of the SVG schema. Good luck! On Wed, Aug 7, 2024 at 4:26 AM Ted Hickox <meg...@gm...> wrote: > Currently I have a project with the following HTML: > > <?xml version="1.0" encoding="utf-8"?> > <xs:html xmlns="http://www.w3.org/1999/xhtml" > xmlns:svg="http://www.w3.org/2000/svg" > xmlns:xs="http://www.w3.org/1999/xhtml" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.w3.org/1999/xhtml > SVG_Bezier_Curve_Webpage_XML_Schema.xsd"> > <head> > <title>SVG_Bezier_Curve</title> > <link rel="stylesheet" type="text/css" href=" > http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.css > "/> > <script language="javascript" src=" > http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve_2.js > "/> > </head> > <body onload="Setup()"> > <input type="button" id="Bezier_Curve_Button" value="Click Me!" > onclick="Setup2()"/> > <svg:svg id="My_SVG" height="500" width="500"> > <svg:path id="Bezier_Curve_1"/> > <svg:path id="Bezier_Curve_2"/> > </svg:svg> > </body> > </xs:html> > > And I have a XML Schema that looks like this: > > <xs:schema xmlns:web="http://www.w3.org/1999/xhtml" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > xmlns:svg = "http://www.w3.org/2000/svg" > xmlns:target="http://www.w3.org/1999/xhtml" > targetNamespace="http://www.w3.org/1999/xhtml" > elementFormDefault="qualified"> > <xs:import namespace="http://www.w3.org/2000/svg"/> > <xs:complexType name="HeadType"> > <xs:sequence> > <xs:element name="head" type="target:TitleType"/> > <xs:element name="body" type="target:BodyType"/> > </xs:sequence> > </xs:complexType> > <xs:complexType name="TitleType"> > <xs:sequence> > <xs:element name="title" type="xs:string"/> > <xs:element name="link" type="target:LinkType"/> > <xs:element name="script" type="target:ScriptType"/> > </xs:sequence> > </xs:complexType> > <xs:complexType name="LinkType"> > <xs:attribute name="rel" type="xs:string"/> > <xs:attribute name="type" type="xs:string"/> > <xs:attribute name="href" type="xs:string"/> > </xs:complexType> > <xs:complexType name="ScriptType"> > <xs:attribute name="language" type="xs:string"/> > <xs:attribute name="src" type="xs:string"/> > </xs:complexType> > <xs:complexType name="BodyType"> > <xs:sequence> > <xs:element name="input" type="target:InputType"/> > <xs:element name="svg" type="target:SvgType"/> > </xs:sequence> > <xs:attribute name="onload" type="xs:string"/> > </xs:complexType> > <xs:complexType name="InputType"> > <xs:attribute name="type" type="xs:string"/> > <xs:attribute name="id" type="xs:string"/> > <xs:attribute name="value" type="xs:string"/> > <xs:attribute name="onclick" type="xs:string"/> > </xs:complexType> > <xs:complexType name="SvgType"> > <xs:sequence> > <xs:element name="path" type="target:PathType"/> > <xs:element name="path" type="target:PathType"/> > </xs:sequence> > <xs:attribute name="id" type="xs:string"/> > <xs:attribute name="height" type="xs:string"/> > <xs:attribute name="width" type="xs:string"/> > </xs:complexType> > <xs:complexType name="PathType"> > <xs:attribute name="id" type="xs:string"/> > </xs:complexType> > <xs:element name="html" type="target:HeadType"/> > </xs:schema> > > Because the SVG elements in the HTML document are in a different > namespace, I'm generating a validation error. Can I create a XML Schema > for the SVG tags in my HTML and import that schema into the schema I have > now? Would this finally validate my svg tags in my HTML code? > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Michael Westbay Writer/System Administrator http://www.japanesebaseball.com/ |
|
From: Ted H. <meg...@gm...> - 2024-08-06 19:25:26
|
Currently I have a project with the following HTML: <?xml version="1.0" encoding="utf-8"?> <xs:html xmlns="http://www.w3.org/1999/xhtml" xmlns:svg="http://www.w3.org/2000/svg" xmlns:xs="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/1999/xhtml SVG_Bezier_Curve_Webpage_XML_Schema.xsd"> <head> <title>SVG_Bezier_Curve</title> <link rel="stylesheet" type="text/css" href=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.css "/> <script language="javascript" src=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve_2.js "/> </head> <body onload="Setup()"> <input type="button" id="Bezier_Curve_Button" value="Click Me!" onclick="Setup2()"/> <svg:svg id="My_SVG" height="500" width="500"> <svg:path id="Bezier_Curve_1"/> <svg:path id="Bezier_Curve_2"/> </svg:svg> </body> </xs:html> And I have a XML Schema that looks like this: <xs:schema xmlns:web="http://www.w3.org/1999/xhtml" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:svg = "http://www.w3.org/2000/svg" xmlns:target="http://www.w3.org/1999/xhtml" targetNamespace="http://www.w3.org/1999/xhtml" elementFormDefault="qualified"> <xs:import namespace="http://www.w3.org/2000/svg"/> <xs:complexType name="HeadType"> <xs:sequence> <xs:element name="head" type="target:TitleType"/> <xs:element name="body" type="target:BodyType"/> </xs:sequence> </xs:complexType> <xs:complexType name="TitleType"> <xs:sequence> <xs:element name="title" type="xs:string"/> <xs:element name="link" type="target:LinkType"/> <xs:element name="script" type="target:ScriptType"/> </xs:sequence> </xs:complexType> <xs:complexType name="LinkType"> <xs:attribute name="rel" type="xs:string"/> <xs:attribute name="type" type="xs:string"/> <xs:attribute name="href" type="xs:string"/> </xs:complexType> <xs:complexType name="ScriptType"> <xs:attribute name="language" type="xs:string"/> <xs:attribute name="src" type="xs:string"/> </xs:complexType> <xs:complexType name="BodyType"> <xs:sequence> <xs:element name="input" type="target:InputType"/> <xs:element name="svg" type="target:SvgType"/> </xs:sequence> <xs:attribute name="onload" type="xs:string"/> </xs:complexType> <xs:complexType name="InputType"> <xs:attribute name="type" type="xs:string"/> <xs:attribute name="id" type="xs:string"/> <xs:attribute name="value" type="xs:string"/> <xs:attribute name="onclick" type="xs:string"/> </xs:complexType> <xs:complexType name="SvgType"> <xs:sequence> <xs:element name="path" type="target:PathType"/> <xs:element name="path" type="target:PathType"/> </xs:sequence> <xs:attribute name="id" type="xs:string"/> <xs:attribute name="height" type="xs:string"/> <xs:attribute name="width" type="xs:string"/> </xs:complexType> <xs:complexType name="PathType"> <xs:attribute name="id" type="xs:string"/> </xs:complexType> <xs:element name="html" type="target:HeadType"/> </xs:schema> Because the SVG elements in the HTML document are in a different namespace, I'm generating a validation error. Can I create a XML Schema for the SVG tags in my HTML and import that schema into the schema I have now? Would this finally validate my svg tags in my HTML code? |
|
From: Ted H. <meg...@gm...> - 2024-07-27 19:14:05
|
Here is my XHTML: <html xmlns="http://www.w3.org/1999/xhtml" xmlns:svg=" http://www.w3.org/2000/svg" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.TedTheSpeedlearner.com SVG_Bezier_Curve_Webpage_XML_Schema.xsd"> <head> <title>SVG_Bezier_Curve</title> <link rel="stylesheet" type="text/css" href=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.css "/> <script language="javascript" src=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve_2.js "> </script> </head> <body onload="Setup()"> <input type="button" id="Bezier_Curve_Button" value="Click Me!" onclick="Setup2()"/> <svg:svg id="My_SVG" height="500" width="500"> <svg:path id="Bezier_Curve_1"/> <svg:path id="Bezier_Curve_2"/> </svg:svg> </body> </html> Here is my XML Schema: <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:target=" http://www.TedTheSpeedlearner.com" targetNamespace=" http://www.TedTheSpeedlearner.com" elementFormDefault="qualified"> <complexType name="HeadType"> <sequence> <element name="head" type="target:TitleType"/> <element name="body" type="target:BodyType"/> </sequence> </complexType> <complexType name="TitleType"> <sequence> <element name="title" type="string"/> <element name="link" type="target:LinkType"/> <element name="script" type="target:ScriptType"/> </sequence> </complexType> <complexType name="LinkType"> <attribute name="rel" type="string"/> <attribute name="type" type="string"/> <attribute name="href" type="string"/> </complexType> <complexType name="ScriptType"> <attribute name="language" type="string"/> <attribute name="src" type="string"/> </complexType> <complexType name="BodyType"> <sequence> <element name="input" type="target:InputType"/> <element name="svg" type="target:SvgType"/> <element name="path" type="PathType"/> <element name="path" type="PathType"/> </sequence> <attribute name="onload" type="string"/> </complexType> <complexType name="SvgType"> <attribute name="xmlns" type="string"/> <attribute name="id" type="string"/> <attribute name="height" type="string"/> <attribute name="width" type="string"/> </complexType> <complexType name="InputType"> <attribute name="id" type="string"/> <attribute name="onclick" type="string"/> </complexType> <complexType name="PathType"> <attribute name="id" type="string"/> </complexType> <element name="html" type="target:HeadType"/> </schema> And here is my Xquery: xquery version "3.0"; import module namespace validation="http://exist-db.org/xquery/validation"; let $schema := xs:anyURI('/db/apps/HTML_Student/SVG_Bezier_Curve_Webpage_XML_Schema.xsd') let $instance := xs:anyURI('/db/apps/HTML_Student/SVG_Bezier_Curve.xhtml') return (validation:jaxp-report($instance, xs:boolean("false"), $schema)) When I run the Xquery, the following error occurs: [image: image.png] I don't know what that error is so I don't know how to fix it. Please assist me. |
|
From: Nick S. <nsi...@nu...> - 2024-07-27 18:47:30
|
If our eXist-db has an unclean shutdown and we restart it and we see the below error, in our logs, what is the recommended action we should take? 2024-07-27 18:16:28,239 [main] ERROR (BFile.java [readOffsets]:2547) - Problematic tid found: 12338; trying to recover ... 2024-07-27 18:16:28,240 [main] ERROR (BFile.java [readOffsets]:2547) - Problematic tid found: 19508; trying to recover ... 2024-07-27 18:16:28,240 [main] ERROR (BFile.java [readOffsets]:2547) - Problematic tid found: 17473; trying to recover ... This error does not indicate whether the effort to recover the tid was successful or not. What is a tid? My experience historically, has been to instantiate another server and try to export the data and import it into the new server. I don't believe I have ever been able to reliably fix whatever this error is trying to tell me. I just try to get a new system setup and replace the system that reports this error. I would be interested in hearing what other people do or recommend. Nick -- Nick Sincaglia President/Founder NueMeta, LLC Digital Media & Technology Phone: +1-630-303-7035 nsi...@nu... http://www.nuemeta.com Skype: nsincaglia |
|
From: Ted H. <meg...@gm...> - 2024-07-26 03:59:30
|
I got an error message when I ran an xquery against my XHTML document. Here is the error: [image: image.png] Here is my XHTML: <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>SVG_Bezier_Curve</title> <link rel="stylesheet" type="text/css" href=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.css "/> <script language="javascript" src=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve_2.js "> </script> </head> <body onload="Setup()"> <input type="button" id="Bezier_Curve_Button" value="Click Me!" onclick="Setup2()"/> <svg xmlns="http://www.w3.org/2000/svg" id="My_SVG" height="500" width="500"> <path id="Bezier_Curve_1"/> <path id="Bezier_Curve_2"> </path> </svg> </body> </html> And here is my XML Schema: <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:target=" http://www.TedTheSpeedlearner.com" targetNamespace=" http://www.TedTheSpeedlearner.com" elementFormDefault="qualified"> <complexType name="HeadType"> <sequence> <element name="head" type="target:TitleType"/> <element name="body" type="target:BodyType"/> </sequence> </complexType> <complexType name="TitleType"> <sequence> <element name="title" type="string"/> <element name="link" type="target:LinkType"/> <element name="script" type="target:ScriptType"/> </sequence> </complexType> <complexType name="LinkType"> <attribute name="rel" type="string"/> <attribute name="type" type="string"/> <attribute name="href" type="string"/> </complexType> <complexType name="ScriptType"> <attribute name="language" type="string"/> <attribute name="src" type="string"/> </complexType> <complexType name="BodyType"> <sequence> <element name="input" type="target:InputType"/> <element name="svg" type="target:SvgType"/> </sequence> <attribute name="onload" type="string"/> </complexType> <complexType name="SvgType"> <sequence> <attribute name="id" type="string"/> <attribute name="height" type="string"/> <attribute name="width" type="string"/> <element name="path" type="PathType"/> <element name="path" type="PathType"/> </sequence> <attribute name="id" type="string"/> </complexType> <complexType name="InputType"> <attribute name="id" type="string"/> <attribute name="onclick" type="string"/> </complexType> <complexType name="PathType"> <attribute name="id" type="string"/> </complexType> <element name="html" type="target:HeadType"/> </schema> |
|
From: Ralph C. <ra...@ra...> - 2024-07-17 13:35:42
|
Thanks Jean-Paul, that worked perfectly! Cheers Ralph On 15/07/2024 19:37, Jean-Paul Rehr wrote: > In my experience this requires reindexing the entire database. When > this happens, as a general practice, I go through and reindex each app > separately. I start with the "core" apps like eXide, Monex, package > manager, etc. As you go through each app and reindex you should find > that each app is back online again... > > JPR > > On Mon, Jul 15, 2024 at 7:39 PM Ralph Corrigan <ra...@ra...> > wrote: > >> Hi all, following a JVM crash at the weekend, all of the apps front >> ends (except the dashboard) are failing to load and displaying the >> following error (this one from Monex). Has anyone seen anything >> similar? The db is accessible from Oxygen and seems fine, but nothing >> (including exide) will load... >> >> Ralph >> >> <exception> >> >> <path>/db/apps/monex/modules/view.xql</path> >> <message>exerr:ERROR The actual return type does not match the >> sequence type declared in the function's signature: >> config:app-title(node(), map(*)) text(). Expected cardinality: exactly >> one, got 0. [at line 63, column 50, source: >> /db/apps/monex/modules/view.xql] In function: config:app-title(node(), >> map(*)) [-1:-1:/db/apps/monex/modules/config.xqm] >> templates:process-output(element(), map(*), item()*, element()) >> [211:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:call-by-introspection(element(), map(*), map(*), >> function(*)) >> [189:28:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:call(item(), element(), map(*)) >> [137:36:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:process(node()*, map(*)) >> [148:81:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:process(node()*, map(*)) >> [148:81:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:process(node()*, map(*)) >> [428:17:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:process-output(element(), map(*), item()*) >> [230:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:process-output(element(), map(*), item()*, element()) >> [211:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:call-by-introspection(element(), map(*), map(*), >> function(*)) >> [189:28:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:call(item(), element(), map(*)) >> [145:37:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:process(node()*, map(*)) >> [133:51:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:process(node()*, map(*)) >> [90:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] >> templates:apply(node()+, function(*), map(*)?, map(*)?) >> [43:5:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql]</message> >> </exception> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Ted H. <meg...@gm...> - 2024-07-17 13:25:51
|
Here is my XHTML <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>SVG_Bezier_Curve</title> <link rel="stylesheet" type="text/css" href=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.css "/> <script language="javascript" src=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve_2.js "> </script> </head> <body> <input type="text" id="My_Text" value="I was here."/> <input type="button" onclick="Setup2()"/> <input type="button" onclick="Setup()"/> <p id="My_Paragraph"/> <svg xmlns="http://www.w3.org/2000/svg" id="My_SVG" height="500" width="500"> <path id="Bezier_Curve_1"/> <path id="Bezier_Curve_2" d="M 300, 200 A 50, 50 0,0,1 400,200" stroke="red" stroke-width="3" fill="none"> </path> </svg> </body> </html> Here is my Javascript: function Setup() { var Bezier_Curve_Identification; var Attribute_Name; var Attribute_Name_2; var Coordinate; var My_Properties; document.getElementById("My_Text").value = "My Setup."; Attribute_Name = "d"; Attribute_Name_2 = "style"; My_Properties = "stroke: blue; stroke-width: 3; fill: none;"; Coordinate = "M 300 200 A 20 20 0 0 0 400 200"; Bezier_Curve_Identification = document.getElementById('Bezier_Curve_1'); Bezier_Curve_Identification.setAttribute(Attribute_Name, Coordinate); Bezier_Curve_Identification.setAttribute(Attribute_Name_2, My_Properties); } function Setup2() { var SVG_Data; var Retrieved_Data; SVG_Data = new XMLHttpRequest(); SVG_Data.open("GET"," http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.xq", true); SVG_Data.onreadystatechange = function () { if (SVG_Data.readyState == 4) { Retrieved_Data = SVG_Data.responseText; document.getElementById("My_Text").value = Retrieved_Data;} }; SVG_Data.send();} Here is my Xquery: xquery version "3.0"; declare default element namespace "http://www.TedTheSpeedlearner.com"; declare option exist:serialize "method=text media-type=text/plain"; let $header-addition := response:set-header("Access-Control-Allow-Origin","*"); let $doc := doc("SVG_Bezier_Curve_Data.xml")/SVG_Data_Collection/Bezier_Curve_1; let $First_Data_Name := $doc/Main_Attribute; let $Data := concat($First_Data_Name, "*"); let $Second_Data_Name := $doc/Initial_Attribute; let $Data := concat($Data, $Second_Data_Name, "-"); let $Third_Data_Name := $doc/Coordinate_Start; let $Data := concat($Data, $Third_Data_Name, "-"); let $Fourth_Data_Name := $doc/Arc_Attribute; let $Data := concat($Data, $Fourth_Data_Name, "-"); let $Fifth_Data_Name := $doc/Bezier_Arc; let $Data := concat($Data, $Fifth_Data_Name, "-"); let $Sixth_Data_Name := $doc/Terminal_Coordinate; let $Data := concat($Data, $Sixth_Data_Name); return $Data; Here is my data: <SVG_Data_Collection xmlns="http://www.TedTheSpeedlearner.com" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.TedTheSpeedlearner.com SVG_Bezier_Curve_Data_Schema.xsd"> <Bezier_Curve_1> <Main_Attribute>d</Main_Attribute> <Initial_Attribute>M</Initial_Attribute> <Coordinate_Start>300 200</Coordinate_Start> <Arc_Attribute>A</Arc_Attribute> <Bezier_Arc>20 20 0 0 0</Bezier_Arc> <Terminal_Coordinate>400 200</Terminal_Coordinate> <Style_Attribute>style</Style_Attribute> <Style_Color>stroke: red;</Style_Color> <Style_Width>stroke-width: 3;</Style_Width> <Style_Fill>fill: none;</Style_Fill> </Bezier_Curve_1> <Bezier_Curve_2> <Main_Attribute>d</Main_Attribute> <Initial_Attribute>M</Initial_Attribute> <Coordinate_Start>300 200</Coordinate_Start> <Arc_Attribute>A</Arc_Attribute> <Bezier_Arc>20 20 0 0 0</Bezier_Arc> <Terminal_Coordinate>400 200</Terminal_Coordinate> <Style_Attribute>style</Style_Attribute> <Style_Color>stroke: blue;</Style_Color> <Style_Width>stroke-width: 3;</Style_Width> <Style_Fill>fill: none;</Style_Fill> </Bezier_Curve_2> </SVG_Data_Collection> I already validated the XML data. Why do I get this error: <html><head><meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/><title>Error 404 Document /db/apps/HTML_Student/SVG_Bezier_Curve.xq not found</title></head><body><h2>HTTP ERROR 404 Document /db/apps/HTML_Student/SVG_Bezier_Curve.xq not found</h2><table><tr><th>URI:</th><td>/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.xq</td></tr><tr><th>STATUS:</th><td>404</td></tr><tr><th>MESSAGE:</th><td>Document /db/apps/HTML_Student/SVG_Bezier_Curve.xq not found</td></tr><tr><th>SERVLET:</th><td>EXistServlet</td></tr></table><hr/><a href="https://eclipse.org/jetty">Powered by Jetty:// 9.4.50.v20221201</a><hr/></body></html> |
|
From: Jean-Paul R. <re...@gm...> - 2024-07-15 18:37:31
|
In my experience this requires reindexing the entire database. When this happens, as a general practice, I go through and reindex each app separately. I start with the "core" apps like eXide, Monex, package manager, etc. As you go through each app and reindex you should find that each app is back online again... JPR On Mon, Jul 15, 2024 at 7:39 PM Ralph Corrigan <ra...@ra...> wrote: > Hi all, following a JVM crash at the weekend, all of the apps front ends > (except the dashboard) are failing to load and displaying the following > error (this one from Monex). Has anyone seen anything similar? The db is > accessible from Oxygen and seems fine, but nothing (including exide) will > load... > > Ralph > <exception> > <path>/db/apps/monex/modules/view.xql</path> > <message>exerr:ERROR The actual return type does not match the sequence > type declared in the function's signature: config:app-title(node(), map(*)) > text(). Expected cardinality: exactly one, got 0. [at line 63, column 50, > source: /db/apps/monex/modules/view.xql] In function: > config:app-title(node(), map(*)) [-1:-1:/db/apps/monex/modules/config.xqm] > templates:process-output(element(), map(*), item()*, element()) > [211:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:call-by-introspection(element(), map(*), map(*), function(*)) > [189:28:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:call(item(), element(), map(*)) > [137:36:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:process(node()*, map(*)) > [148:81:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:process(node()*, map(*)) > [148:81:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:process(node()*, map(*)) > [428:17:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:process-output(element(), map(*), item()*) > [230:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:process-output(element(), map(*), item()*, element()) > [211:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:call-by-introspection(element(), map(*), map(*), function(*)) > [189:28:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:call(item(), element(), map(*)) > [145:37:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:process(node()*, map(*)) > [133:51:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:process(node()*, map(*)) > [90:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > templates:apply(node()+, function(*), map(*)?, map(*)?) > [43:5:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] > </message> > </exception> > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Ralph C. <ra...@ra...> - 2024-07-15 17:39:04
|
Hi all, following a JVM crash at the weekend, all of the apps front ends (except the dashboard) are failing to load and displaying the following error (this one from Monex). Has anyone seen anything similar? The db is accessible from Oxygen and seems fine, but nothing (including exide) will load... Ralph <exception> <path>/db/apps/monex/modules/view.xql</path> <message>exerr:ERROR The actual return type does not match the sequence type declared in the function's signature: config:app-title(node(), map(*)) text(). Expected cardinality: exactly one, got 0. [at line 63, column 50, source: /db/apps/monex/modules/view.xql] In function: config:app-title(node(), map(*)) [-1:-1:/db/apps/monex/modules/config.xqm] templates:process-output(element(), map(*), item()*, element()) [211:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:call-by-introspection(element(), map(*), map(*), function(*)) [189:28:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:call(item(), element(), map(*)) [137:36:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:process(node()*, map(*)) [148:81:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:process(node()*, map(*)) [148:81:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:process(node()*, map(*)) [428:17:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:process-output(element(), map(*), item()*) [230:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:process-output(element(), map(*), item()*, element()) [211:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:call-by-introspection(element(), map(*), map(*), function(*)) [189:28:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:call(item(), element(), map(*)) [145:37:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:process(node()*, map(*)) [133:51:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:process(node()*, map(*)) [90:9:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql] templates:apply(node()+, function(*), map(*)?, map(*)?) [43:5:/exist/etc/../data/expathrepo/shared-0.9.1/content/templates.xql]</message> </exception> |
|
From: Jo C. <Jo....@ha...> - 2024-07-15 15:17:50
|
Dear list, I have been asked to review the behaviour of exist backups. At https://exist-db.org/exist/apps/doc/backup, it says that prior to running the backup, the following steps are taken: - Wait for all pending transactions to complete. - Enter protected mode. No new transactions will be allowed. Concurrent requests by other clients will be blocked and added to the internal queue. Experiments suggest that, while a backup is in progress, database writes are still in fact permitted. I did a manual trace through the code at exist-core/src/main/java/org/exist/backup/Backup.java and didn't see any code that places a lock on the database or sets the db as read-only (as the system will do when disk space drops below the minimum). Has anyone looked at this situation? Is the documentation inaccurate here? Best regards, -- Jo |
|
From: Ted H. <meg...@gm...> - 2024-07-14 21:30:04
|
I thank you very much for your suggestion. But I really don't want to use
PHP at this time. Fortunately StackOverflow finally gave me a good answer
to my question. I will share my code with all of you in case someone needs
this information:
function Setup2() {
var Bezier_Curve_Identification;
var Attribute_Name;
var Attribute_Name_2;
var Coordinate;
var My_Properties;
document.getElementById("My_Text").value = "I'm right here.";
Attribute_Name = "d";
Attribute_Name_2 = "style";
My_Properties = "stroke: blue; stroke-width: 3; fill: none";
Coordinate = "M 300 200 A 20 20 0 0 0 400 200";
Bezier_Curve_Identification = document.getElementById('Bezier_Curve_1');
Bezier_Curve_Identification.setAttribute(Attribute_Name, Coordinate);
Bezier_Curve_Identification.setAttribute(Attribute_Name_2,
My_Properties);
}
Now that I know that I can store my attribute information into variables,
all I have to do is create an XML document, store the information into the
document, validate my XML document, and then use Javascript to retrieve my
information. After that's completed, I can just store the information into
my variables and display my Bezier curve. This will help tremendously with
all future SVG animations. All I would have to do is find the coordinates
I need to change in my XML documents and apply the changes. Or I could
just create an XQuery that could locate and change the coordinates in my
XML documents.
On Sun, Jul 14, 2024 at 2:45 PM dl <dl...@gm...> wrote:
> By chance I spotted your post when I am not applying eXistdb at this
> moment.
> I can't answer your immediate question using setAttributeNS. So I do not
> post to the forum. But some time back I learned and bookmarked a neat
> trick to use PHP variables to modify SVG attributes - dynamically.
>
> It is documented in old.carto.net.
>
> https://old.carto.net/papers/svg/postgis_geturl_xmlhttprequest/
>
> It involves creating a custom mimetype. Mine is psvg. But otherwise I
> find it useful for customising SVG (and indeed other standard types such
> as css, js). Requires a PHP enabled server to generate custom code from
> the hybrid mimetypes.
>
> This "outlier" approach might not answer your immediate question. But
> I'm sure that it can apply to XHTML code after some experimenting. Refer
> to old.carto.net tutorial.
>
> dl
>
> On 14/07/2024 19:54, Ted Hickox wrote:
> > I really didn't want to contact you, but I felt like I had no other
> > choice. I'm trying to use the setAttributeNS command to change a path
> > arc element inside my XHTML. Once I'm successful in doing this, I
> > will store the arc path coordinates inside the eXist database. Here
> > is my XHTML code:
> >
> > <html xmlns="http://www.w3.org/1999/xhtml">
> > <head>
> > <title>SVG_Bezier_Curve</title>
> > <link rel="stylesheet" type="text/css"
> > href="
> http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.css
> "/>
> > <script language = "javascript" src =
> > "
> http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.js
> ">
> >
> > </script>
> > </head>
> > <body>
> > <input type = "text" id = "My_Text" value = "I was
> > here."></input>
> > <input type = "button" onclick = "Setup2()"/>
> > <p id = "My_Paragraph"></p>
> > <svg id = "My_SVG" xmlns="http://www.w3.org/2000/svg"
> > height="500" width="500">
> > <path id = "Bezier_Curve_1"/>
> > <path id="Bezier_Curve_2" d="M 300, 200 A 50, 50 0,0,1
> > 400,200" stroke="red" stroke-width="3" fill="none">
> > </path>
> > </svg>
> > </body>
> > </html>
> >
> > Here is my Javascirpt code:
> >
> > function Setup2() {
> > var SVG_Def;
> > var Bezier_Curve_Identification;
> > var Attribute_Name;
> > var coordinate;
> >
> > document.getElementById("My_Text").value = "I'm right here.";
> > SVG_Def = document.getElementById("My_SVG");
> > Bezier_Curve_Identification = SVG.getElementById('Bezier_Curve_1');
> > Bezier_Curve_Identification.setAttributeNS =
> > ("http://www.w3.org/1999/xlink", "'d'", "'M 300, 200 A 20, 20 0,0,1
> > 340,200'");
> > Bezier_Curve_Identification.setAttributeNS =
> > ("http://www.w3.org/1999/xlink", "'style'", "'stroke: blue;
> > stroke-width: 3; fill: none;'");
> > }
> >
> > I hope you can find the errors so I can finish my project.
> >
> >
> > _______________________________________________
> > Exist-open mailing list
> > Exi...@li...
> > https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
|
|
From: Ted H. <meg...@gm...> - 2024-07-14 18:55:17
|
I really didn't want to contact you, but I felt like I had no other choice. I'm trying to use the setAttributeNS command to change a path arc element inside my XHTML. Once I'm successful in doing this, I will store the arc path coordinates inside the eXist database. Here is my XHTML code: <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>SVG_Bezier_Curve</title> <link rel="stylesheet" type="text/css" href=" http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.css "/> <script language = "javascript" src = " http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Bezier_Curve.js"> </script> </head> <body> <input type = "text" id = "My_Text" value = "I was here."></input> <input type = "button" onclick = "Setup2()"/> <p id = "My_Paragraph"></p> <svg id = "My_SVG" xmlns="http://www.w3.org/2000/svg" height="500" width="500"> <path id = "Bezier_Curve_1"/> <path id="Bezier_Curve_2" d="M 300, 200 A 50, 50 0,0,1 400,200" stroke="red" stroke-width="3" fill="none"> </path> </svg> </body> </html> Here is my Javascirpt code: function Setup2() { var SVG_Def; var Bezier_Curve_Identification; var Attribute_Name; var coordinate; document.getElementById("My_Text").value = "I'm right here."; SVG_Def = document.getElementById("My_SVG"); Bezier_Curve_Identification = SVG.getElementById('Bezier_Curve_1'); Bezier_Curve_Identification.setAttributeNS = (" http://www.w3.org/1999/xlink", "'d'", "'M 300, 200 A 20, 20 0,0,1 340,200'"); Bezier_Curve_Identification.setAttributeNS = (" http://www.w3.org/1999/xlink", "'style'", "'stroke: blue; stroke-width: 3; fill: none;'"); } I hope you can find the errors so I can finish my project. |
|
From: Ted H. <meg...@gm...> - 2024-07-03 16:12:07
|
Here is my Javascript code:
var SVG_Data;
var Retrieved_Data;
var Attribute_List;
var Coordinate_List;
var Counter;
function Setup() {
SVG_Data = new XMLHttpRequest();
SVG_Data.open("GET","
http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.xq",
true);
SVG_Data.onreadystatechange = function () {
if (SVG_Data.readyState == 4) {
Retrieved_Data = SVG_Data.responseText;
Retrieved_Data = Retrieved_Data.split("*");
Attribute_List = "";
Coordinate_List = "";
for (Counter = 0; Counter < 8; Counter++) {
Attribute_List = Attribute_List + Retrieved_Data[Counter] + "*";
Counter = Counter + 1;
Coordinate_List = Coordinate_List + Retrieved_Data[Counter] + "*";}
Attribute_List = Attribute_List.split("*");
Coordinate_List = Coordinate_List.split("*");
Coordinate = "<ellipse id = 'My_Ellipse'";
for (Counter = 0; Counter < 4; Counter++) {
Coordinate = Coordinate + " " + Attribute_List[Counter] + " = '" +
Coordinate_List[Counter] + "'";}
Coordinate = Coordinate + ">";
document.getElementById("Image_Box").innerHTML = Coordinate;
}
};
}
SVG_Data.send();
I used the dev tool that you recommended. And it did find the error.
It says uncaught type error. It cannot read properties of undefined. It
says it's reading send.
So now I know that the SVG_Data object doesn't have the send property. How
can I create the send property for the SVG_Data object?
On Mon, Jun 24, 2024 at 12:34 AM Florian Schmitt <
ml-...@fl...> wrote:
> Hi Ted,
>
> the best way to debug your Javascript is using the browser console
> (because it's the browser, not eXist-db which executes that code). If
> you're using Chrome or Edge, check the following help page:
>
>
> https://learn.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/console/
>
> For Firefox, see:
>
> https://firefox-source-docs.mozilla.org/devtools-user/
>
> Especially, search for information about the Console output and how to
> send debug messages to the console.
>
> HTH
> Florian
>
>
> Am 24.06.24 um 02:46 schrieb Ted Hickox:
> > I feel like such an idiot. Thanks for helping me validate my data.
> > Since I know my data is valid, I know that there is something wrong
> > with my Javascript. I'm not sure what that would be, but I will test
> > various things. In case anyone is curious, here is my Javascript.
> >
> > var SVG_Data;
> > var Retrieved_Data;
> > var Attribute_List;
> > var Coordinate_List;
> > var Counter;
> > function Setup() {
> > SVG_Data = new XMLHttpRequest();
> >
> > SVG_Data.open("GET","
> http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.xq <
> http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.xq>",
> true);
> > SVG_Data.onreadystatechange = function () {
> > if (SVG_Data.readyState == 4) {
> > Retrieved_Data = SVG_Data.responseText;
> > Retrieved_Data = Retrieved_Data.split("*");
> > Attribute_List = "";
> > Coordinate_List = "";
> > for (Counter = 0; Counter < 8; Counter++) {
> > Attribute_List = Attribute_List + Retrieved_Data[Counter] + "*";
> > Counter = Counter + 1;
> > Coordinate_List = Coordinate_List + Retrieved_Data[Counter] + "*";}
> > Attribute_List = Attribute_List.split("*");
> > Coordinate_List = Coordinate_List.split("*");
> > Coordinate = "<ellipse id = 'My_Ellipse'";
> > for (Counter = 0; Counter < 4; Counter++) {
> > Coordinate = Coordinate + " " + Attribute_List[Counter] + "
> > = '" + Coordinate_List[Counter] + "'";}
> > Coordinate = Coordinate + ">";
> > document.getElementById("Image_Box").innerHTML = Coordinate;
> > }
> > };
> > }
> > SVG_Data.send();
> >
> > And here is my revised HTML
> >
> > <html xmlns="http://www.w3.org/1999/xhtml
> > <http://www.w3.org/1999/xhtml>"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> > <http://www.w3.org/2001/XMLSchema-instance>"
> > xsi:schemaLocation="http://www.TedTheSpeedlearner.com
> > <http://www.TedTheSpeedlearner.com> SVG_Ellipse_Webpage_XML_Schema.xsd">
> > <head>
> > <title>SVG Ellipse</title>
> > <link rel="stylesheet" type="text/css"
> > href="
> http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.css <
> http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.css>"/>
> > <script language="javascript"
> > src="
> http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.js <
> http://localhost:8080/exist/rest/db/apps/HTML_Student/SVG_Ellipse.js>"/>
> > </head>
> > <body onload="Setup()">
> > <svg id="Image_Box">
> > <ellipse id="My_Ellipse"/>
> > </svg>
> > </body>
> > </html>
> >
> > On Sun, Jun 23, 2024 at 5:57 PM Florian Schmitt
> > <ml-...@fl...
> > <mailto:ml-...@fl...>> wrote:
> >
> > Hi Ted,
> >
> > taka a close look to the validation result. Instead of "ellipse",
> > "Ellipse" is expected. You've defined in your schema that the element
> > name starts with an upper-case "E", which isn't the case in your XML.
> >
> > Thus, replace
> >
> > <ellipse>
> > <X_Center_Coordinate>100</X_Center_Coordinate>
> > <Y_Center_Coordinate>100</Y_Center_Coordinate>
> > <X_Radius_Coordinate>30</X_Radius_Coordinate>
> > <Y_Radius_Coordinate>70</Y_Radius_Coordinate>
> > </ellipse>
> >
> > with
> >
> > <Ellipse>
> > <X_Center_Coordinate>100</X_Center_Coordinate>
> > <Y_Center_Coordinate>100</Y_Center_Coordinate>
> > <X_Radius_Coordinate>30</X_Radius_Coordinate>
> > <Y_Radius_Coordinate>70</Y_Radius_Coordinate>
> > </Ellipse>
> >
> > HTH
> > Florian
> >
> >
> > Am 23.06.2024 um 23:24 schrieb Ted Hickox:
> > > Here is a little update. I attempted to validate my xml code.
> > This is
> > > the result I received:
> > >
> > > image.png
> > >
> > > I'm assuming that the problem is located in my xml code and not
> > in my
> > > xml schema. Here are my xml and xml schema codes
> > ...
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
|
|
From: Julian J. <jul...@ad...> - 2024-06-26 10:01:00
|
Hi Florian,
I’m afraid that doesn’t work in my test, a least not as I would anticipate.
I used exactly your snippet for the expath:package, and tried loading
the XSLT using doc('CMIF-base.xsl') and doc('./CMIF-base.xsl'), neither
of which worked.
Thanks for the suggestion nevertheless!
Best,
Julian
Am 25.06.24 um 17:04 schrieb Florian Schmitt:
> Hi Julian,
>
> maybe expanding your library-package/expath-pkg.xml definition would
> work, too? I didn't test myself, but the EXPath Packaging System
> explicitly allows for referencing XSLT stylesheets:
>
> http://expath.org/spec/pkg#xslt
>
> So, maybe the following would work, too:
>
> ...
> <title>CMIFerator</title>
> <xquery>
> <namespace>http://www.digitale-akademie.de/cmiferator</namespace>
> <file>cmiferator.xqm</file>
> </xquery>
> <xslt>
>
> <import-uri>http://www.digitale-akademie.de/cmiferator/CMIF-base.xsl</import-uri>
>
> <file>CMIF-base.xsl</file>
> </xslt>
> ...
>
> Greetings,
> Florian
>
>
> Am 24.06.24 um 11:18 schrieb Julian Jarosch:
>> Hello everyone,
>>
>> I’m trying to use XSLT stylesheets in an XQuery module in a library
>> package, along the lines of (simplified example):
>>
>> declare variable $template := doc('./CMIF-base.xsl');
>>
>> The current actual code is here:
>>
>> https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25
>>
>>
>> I had successfully tested this as an XQuery module written directly
>> in eXist/eXide. It stopped working when I installed it as a library
>> package, as far as I can tell.
>>
>> By “stopped working” I mean that the variable which is supposed to
>> contain the stylesheet document ($template in the example) remains
>> empty and the transform:transform() function fails because of a
>> missing stylesheet argument.
>>
>> Currently, it seems to me that the cause is with the library package?
>> Is it even possible to include XSLTs in a library package in a manner
>> that they can be loaded into XQuery?
>>
>> Thanks for any guidance – presumably for pointing out an egregious
>> oversight on my end :-)
>>
>> Kind regards,
>> Julian
>>
>>
>>
>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
|
|
From: Florian S. <ml-...@fl...> - 2024-06-25 15:04:12
|
Hi Julian, maybe expanding your library-package/expath-pkg.xml definition would work, too? I didn't test myself, but the EXPath Packaging System explicitly allows for referencing XSLT stylesheets: http://expath.org/spec/pkg#xslt So, maybe the following would work, too: ... <title>CMIFerator</title> <xquery> <namespace>http://www.digitale-akademie.de/cmiferator</namespace> <file>cmiferator.xqm</file> </xquery> <xslt> <import-uri>http://www.digitale-akademie.de/cmiferator/CMIF-base.xsl</import-uri> <file>CMIF-base.xsl</file> </xslt> ... Greetings, Florian Am 24.06.24 um 11:18 schrieb Julian Jarosch: > Hello everyone, > > I’m trying to use XSLT stylesheets in an XQuery module in a library > package, along the lines of (simplified example): > > declare variable $template := doc('./CMIF-base.xsl'); > > The current actual code is here: > > https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25 > > I had successfully tested this as an XQuery module written directly in > eXist/eXide. It stopped working when I installed it as a library > package, as far as I can tell. > > By “stopped working” I mean that the variable which is supposed to > contain the stylesheet document ($template in the example) remains > empty and the transform:transform() function fails because of a > missing stylesheet argument. > > Currently, it seems to me that the cause is with the library package? > Is it even possible to include XSLTs in a library package in a manner > that they can be loaded into XQuery? > > Thanks for any guidance – presumably for pointing out an egregious > oversight on my end :-) > > Kind regards, > Julian > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Julian J. <jul...@ad...> - 2024-06-25 08:25:00
|
Hi Joe, Thanks for the tip! Looks good for deployed packages. In my case, it doesn’t take /db/system/repo – aka library packages – into account. repo:get-root() only returns /db/apps in the databse I’m testing. I haven’t checked if that’s a configuration of our dockerisation of eXist, though. Best, Julian Am 24.06.24 um 15:19 schrieb Joe Wicentowski: > Hi Julian, > > That's a good approach. For some convenience functions, see the > apputils library module in the shared-resources library package. For > example: > > https://github.com/eXist-db/shared-resources/blob/master/content/apputil.xql#L45 > > Joe > > Sent from my iPhone > > > On Mon, Jun 24, 2024 at 7:48 AM Julian Jarosch > <jul...@ad...> wrote: > > Dear Jean-Paul, > > Good idea! But that function evaluates to the collection of the > XQuery which imports the library module. E.g. I’m testing from a > script in /db/xquery which imports my library. I’ve inserted > system:get-module-load-path() into the library but still get > /db/xquery from the testing script. > > Nevertheless, rubber ducking this with you got me thinking about > this section of the documentation > > https://exist-db.org/exist/apps/doc/repo#considerations > > I adapted the documented code snippet into > > util:collection-name(collection('/db/system/repo')//expath:package[@name ="http://www.digitale-akademie.de/cmiferator" <http://www.digitale-akademie.de/cmiferator>]) > > which works for me! It’s a bit inelegant to hard-code > /db/system/repo, but repo:get-root() gives me /db/apps. Perhaps > I’ll get around to optimizing that. For now, I think I’ll test > what I’ve already got. > > Thanks again! > > Best, > Julian > > > Am 24.06.24 um 13:12 schrieb Jean-Paul Rehr: >> Dear Julian, understood. >> >> >Perhaps there is a programmatic way to obtain the current >> package base path (/db/system/repo/cmiferator-0.0.3) and use that >> for loading >> the stylesheet. >> >> You can dynamically get the path of the module from >> system:get-module-load-path() and parse the path into the string >> needed to build your resource path for the XLST file. >> >> Best, >> JPR >> >> >> >> On Mon, Jun 24, 2024 at 12:01 PM Julian Jarosch >> <jul...@ad...> wrote: >> >> Dear Jean-Paul, >> >> Thanks! Yes and no – yes, a library module, but within a >> package that is exclusively declared as a library. See the >> table with types of packages in this section: >> https://exist-db.org/exist/apps/doc/repo#sect-repoxml >> >> “Library package” with type = library and /no target >> specified/ was what I was going for, so far. >> >> This means that the package is not deployed into the /db/apps >> collection. Instead it lives in /db/system/repo. Its >> collection name includes the version number. Currently the >> full path would be >> /db/system/repo/cmiferator-0.0.3/content/CMIF-base.xsl, but >> this will obviously change with the version number. >> >> Perhaps there is a programmatic way to obtain the current >> package base path (/db/system/repo/cmiferator-0.0.3) and use >> that for loading the stylesheet. >> >> Otherwise, I take your point and will consider setting a >> target where to deploy the package within the database >> (/db/apps/cmiferator) and use a fixed, complete resource path >> for loading the stylesheets. (It’s just that initially the >> library package concept seemed a good fit for what I try to >> achieve – make a few XQuery functions available database-wide.) >> >> Best, >> Julian >> >> Am 24.06.24 um 11:43 schrieb Jean-Paul Rehr: >>> Dear Julian, >>> >>> >Is it even possible to include XSLTs in a library package >>> in a manner that they can be loaded into XQuery? >>> >>> I assume by "library package" you mean library module? I do >>> this all the time without an issue. It's just another XML >>> document. >>> >>> However I have a doubt about this path: >>> >>> >doc('./CMIF-base.xsl') >>> >>> Have you tested this with the full explicit path to the >>> document? e.g. "/db/apps/myapp/CMIF-base.xsl" >>> >>> Cheers, >>> JPR >>> >>> >>> On Mon, Jun 24, 2024 at 11:35 AM Julian Jarosch >>> <jul...@ad...> wrote: >>> >>> Hello everyone, >>> >>> I’m trying to use XSLT stylesheets in an XQuery module >>> in a library package, along the lines of (simplified >>> example): >>> >>> declare variable $template := doc('./CMIF-base.xsl'); >>> >>> The current actual code is here: >>> >>> https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25 >>> >>> I had successfully tested this as an XQuery module >>> written directly in eXist/eXide. It stopped working when >>> I installed it as a library package, as far as I can tell. >>> >>> By “stopped working” I mean that the variable which is >>> supposed to contain the stylesheet document ($template >>> in the example) remains empty and the >>> transform:transform() function fails because of a >>> missing stylesheet argument. >>> >>> Currently, it seems to me that the cause is with the >>> library package? Is it even possible to include XSLTs in >>> a library package in a manner that they can be loaded >>> into XQuery? >>> >>> Thanks for any guidance – presumably for pointing out an >>> egregious oversight on my end :-) >>> >>> Kind regards, >>> Julian >>> >>> _______________________________________________ >>> Exist-open mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-open >>> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> >> >> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Joe W. <jo...@gm...> - 2024-06-24 13:20:11
|
Hi Julian, That's a good approach. For some convenience functions, see the apputils library module in the shared-resources library package. For example: https://github.com/eXist-db/shared-resources/blob/master/content/apputil.xql#L45 Joe Sent from my iPhone On Mon, Jun 24, 2024 at 7:48 AM Julian Jarosch <jul...@ad...> wrote: > Dear Jean-Paul, > > Good idea! But that function evaluates to the collection of the XQuery > which imports the library module. E.g. I’m testing from a script in > /db/xquery which imports my library. I’ve inserted > system:get-module-load-path() into the library but still get /db/xquery > from the testing script. > > Nevertheless, rubber ducking this with you got me thinking about this > section of the documentation > > https://exist-db.org/exist/apps/doc/repo#considerations > > I adapted the documented code snippet into > > util:collection-name(collection('/db/system/repo')//expath:package[@name = "http://www.digitale-akademie.de/cmiferator" <http://www.digitale-akademie.de/cmiferator>]) > > which works for me! It’s a bit inelegant to hard-code /db/system/repo, > but repo:get-root() gives me /db/apps. Perhaps I’ll get around to > optimizing that. For now, I think I’ll test what I’ve already got. > > Thanks again! > > Best, > Julian > > > Am 24.06.24 um 13:12 schrieb Jean-Paul Rehr: > > Dear Julian, understood. > > >Perhaps there is a programmatic way to obtain the current package base > path (/db/system/repo/cmiferator-0.0.3) and use that for loading > the stylesheet. > > You can dynamically get the path of the module from system:get-module-load-path() > and parse the path into the string needed to build your resource path for > the XLST file. > > Best, > JPR > > > > On Mon, Jun 24, 2024 at 12:01 PM Julian Jarosch < > jul...@ad...> wrote: > >> Dear Jean-Paul, >> >> Thanks! Yes and no – yes, a library module, but within a package that is >> exclusively declared as a library. See the table with types of packages in >> this section: https://exist-db.org/exist/apps/doc/repo#sect-repoxml >> >> “Library package” with type = library and *no target specified* was what >> I was going for, so far. >> >> This means that the package is not deployed into the /db/apps >> collection. Instead it lives in /db/system/repo. Its collection name >> includes the version number. Currently the full path would be >> /db/system/repo/cmiferator-0.0.3/content/CMIF-base.xsl, but this will >> obviously change with the version number. >> >> Perhaps there is a programmatic way to obtain the current package base >> path (/db/system/repo/cmiferator-0.0.3) and use that for loading the >> stylesheet. >> >> Otherwise, I take your point and will consider setting a target where to >> deploy the package within the database (/db/apps/cmiferator) and use a >> fixed, complete resource path for loading the stylesheets. (It’s just that >> initially the library package concept seemed a good fit for what I try to >> achieve – make a few XQuery functions available database-wide.) >> >> Best, >> Julian >> Am 24.06.24 um 11:43 schrieb Jean-Paul Rehr: >> >> Dear Julian, >> >> >Is it even possible to include XSLTs in a library package in a manner >> that they can be loaded into XQuery? >> >> I assume by "library package" you mean library module? I do this all the >> time without an issue. It's just another XML document. >> >> However I have a doubt about this path: >> >> >doc('./CMIF-base.xsl') >> >> Have you tested this with the full explicit path to the document? e.g. >> "/db/apps/myapp/CMIF-base.xsl" >> >> Cheers, >> JPR >> >> >> On Mon, Jun 24, 2024 at 11:35 AM Julian Jarosch < >> jul...@ad...> wrote: >> >>> Hello everyone, >>> >>> I’m trying to use XSLT stylesheets in an XQuery module in a library >>> package, along the lines of (simplified example): >>> >>> declare variable $template := doc('./CMIF-base.xsl'); >>> >>> The current actual code is here: >>> >>> >>> https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25 >>> >>> I had successfully tested this as an XQuery module written directly in >>> eXist/eXide. It stopped working when I installed it as a library package, >>> as far as I can tell. >>> >>> By “stopped working” I mean that the variable which is supposed to >>> contain the stylesheet document ($template in the example) remains >>> empty and the transform:transform() function fails because of a missing >>> stylesheet argument. >>> >>> Currently, it seems to me that the cause is with the library package? Is >>> it even possible to include XSLTs in a library package in a manner that >>> they can be loaded into XQuery? >>> >>> Thanks for any guidance – presumably for pointing out an egregious >>> oversight on my end :-) >>> >>> Kind regards, >>> Julian >>> _______________________________________________ >>> Exist-open mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-open >>> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > > > _______________________________________________ > Exist-open mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/exist-open > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Julian J. <jul...@ad...> - 2024-06-24 11:47:33
|
Dear Jean-Paul, Good idea! But that function evaluates to the collection of the XQuery which imports the library module. E.g. I’m testing from a script in /db/xquery which imports my library. I’ve inserted system:get-module-load-path() into the library but still get /db/xquery from the testing script. Nevertheless, rubber ducking this with you got me thinking about this section of the documentation https://exist-db.org/exist/apps/doc/repo#considerations I adapted the documented code snippet into util:collection-name(collection('/db/system/repo')//expath:package[@name ="http://www.digitale-akademie.de/cmiferator"]) which works for me! It’s a bit inelegant to hard-code /db/system/repo, but repo:get-root() gives me /db/apps. Perhaps I’ll get around to optimizing that. For now, I think I’ll test what I’ve already got. Thanks again! Best, Julian Am 24.06.24 um 13:12 schrieb Jean-Paul Rehr: > Dear Julian, understood. > > >Perhaps there is a programmatic way to obtain the current package > base path (/db/system/repo/cmiferator-0.0.3) and use that for loading > the stylesheet. > > You can dynamically get the path of the module from > system:get-module-load-path() and parse the path into the string > needed to build your resource path for the XLST file. > > Best, > JPR > > > > On Mon, Jun 24, 2024 at 12:01 PM Julian Jarosch > <jul...@ad...> wrote: > > Dear Jean-Paul, > > Thanks! Yes and no – yes, a library module, but within a package > that is exclusively declared as a library. See the table with > types of packages in this section: > https://exist-db.org/exist/apps/doc/repo#sect-repoxml > > “Library package” with type = library and /no target specified/ > was what I was going for, so far. > > This means that the package is not deployed into the /db/apps > collection. Instead it lives in /db/system/repo. Its collection > name includes the version number. Currently the full path would be > /db/system/repo/cmiferator-0.0.3/content/CMIF-base.xsl, but this > will obviously change with the version number. > > Perhaps there is a programmatic way to obtain the current package > base path (/db/system/repo/cmiferator-0.0.3) and use that for > loading the stylesheet. > > Otherwise, I take your point and will consider setting a target > where to deploy the package within the database > (/db/apps/cmiferator) and use a fixed, complete resource path for > loading the stylesheets. (It’s just that initially the library > package concept seemed a good fit for what I try to achieve – make > a few XQuery functions available database-wide.) > > Best, > Julian > > Am 24.06.24 um 11:43 schrieb Jean-Paul Rehr: >> Dear Julian, >> >> >Is it even possible to include XSLTs in a library package in a >> manner that they can be loaded into XQuery? >> >> I assume by "library package" you mean library module? I do this >> all the time without an issue. It's just another XML document. >> >> However I have a doubt about this path: >> >> >doc('./CMIF-base.xsl') >> >> Have you tested this with the full explicit path to the document? >> e.g. "/db/apps/myapp/CMIF-base.xsl" >> >> Cheers, >> JPR >> >> >> On Mon, Jun 24, 2024 at 11:35 AM Julian Jarosch >> <jul...@ad...> wrote: >> >> Hello everyone, >> >> I’m trying to use XSLT stylesheets in an XQuery module in a >> library package, along the lines of (simplified example): >> >> declare variable $template := doc('./CMIF-base.xsl'); >> >> The current actual code is here: >> >> https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25 >> >> I had successfully tested this as an XQuery module written >> directly in eXist/eXide. It stopped working when I installed >> it as a library package, as far as I can tell. >> >> By “stopped working” I mean that the variable which is >> supposed to contain the stylesheet document ($template in the >> example) remains empty and the transform:transform() function >> fails because of a missing stylesheet argument. >> >> Currently, it seems to me that the cause is with the library >> package? Is it even possible to include XSLTs in a library >> package in a manner that they can be loaded into XQuery? >> >> Thanks for any guidance – presumably for pointing out an >> egregious oversight on my end :-) >> >> Kind regards, >> Julian >> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
|
From: Jean-Paul R. <re...@gm...> - 2024-06-24 11:13:17
|
Dear Julian, understood. >Perhaps there is a programmatic way to obtain the current package base path (/db/system/repo/cmiferator-0.0.3) and use that for loading the stylesheet. You can dynamically get the path of the module from system:get-module-load-path() and parse the path into the string needed to build your resource path for the XLST file. Best, JPR On Mon, Jun 24, 2024 at 12:01 PM Julian Jarosch <jul...@ad...> wrote: > Dear Jean-Paul, > > Thanks! Yes and no – yes, a library module, but within a package that is > exclusively declared as a library. See the table with types of packages in > this section: https://exist-db.org/exist/apps/doc/repo#sect-repoxml > > “Library package” with type = library and *no target specified* was what > I was going for, so far. > > This means that the package is not deployed into the /db/apps collection. > Instead it lives in /db/system/repo. Its collection name includes the > version number. Currently the full path would be > /db/system/repo/cmiferator-0.0.3/content/CMIF-base.xsl, but this will > obviously change with the version number. > > Perhaps there is a programmatic way to obtain the current package base > path (/db/system/repo/cmiferator-0.0.3) and use that for loading the > stylesheet. > > Otherwise, I take your point and will consider setting a target where to > deploy the package within the database (/db/apps/cmiferator) and use a > fixed, complete resource path for loading the stylesheets. (It’s just that > initially the library package concept seemed a good fit for what I try to > achieve – make a few XQuery functions available database-wide.) > > Best, > Julian > Am 24.06.24 um 11:43 schrieb Jean-Paul Rehr: > > Dear Julian, > > >Is it even possible to include XSLTs in a library package in a manner > that they can be loaded into XQuery? > > I assume by "library package" you mean library module? I do this all the > time without an issue. It's just another XML document. > > However I have a doubt about this path: > > >doc('./CMIF-base.xsl') > > Have you tested this with the full explicit path to the document? e.g. > "/db/apps/myapp/CMIF-base.xsl" > > Cheers, > JPR > > > On Mon, Jun 24, 2024 at 11:35 AM Julian Jarosch < > jul...@ad...> wrote: > >> Hello everyone, >> >> I’m trying to use XSLT stylesheets in an XQuery module in a library >> package, along the lines of (simplified example): >> >> declare variable $template := doc('./CMIF-base.xsl'); >> >> The current actual code is here: >> >> >> https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25 >> >> I had successfully tested this as an XQuery module written directly in >> eXist/eXide. It stopped working when I installed it as a library package, >> as far as I can tell. >> >> By “stopped working” I mean that the variable which is supposed to >> contain the stylesheet document ($template in the example) remains empty >> and the transform:transform() function fails because of a missing >> stylesheet argument. >> >> Currently, it seems to me that the cause is with the library package? Is >> it even possible to include XSLTs in a library package in a manner that >> they can be loaded into XQuery? >> >> Thanks for any guidance – presumably for pointing out an egregious >> oversight on my end :-) >> >> Kind regards, >> Julian >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Julian J. <jul...@ad...> - 2024-06-24 10:00:47
|
Dear Jean-Paul, Thanks! Yes and no – yes, a library module, but within a package that is exclusively declared as a library. See the table with types of packages in this section: https://exist-db.org/exist/apps/doc/repo#sect-repoxml “Library package” with type = library and /no target specified/ was what I was going for, so far. This means that the package is not deployed into the /db/apps collection. Instead it lives in /db/system/repo. Its collection name includes the version number. Currently the full path would be /db/system/repo/cmiferator-0.0.3/content/CMIF-base.xsl, but this will obviously change with the version number. Perhaps there is a programmatic way to obtain the current package base path (/db/system/repo/cmiferator-0.0.3) and use that for loading the stylesheet. Otherwise, I take your point and will consider setting a target where to deploy the package within the database (/db/apps/cmiferator) and use a fixed, complete resource path for loading the stylesheets. (It’s just that initially the library package concept seemed a good fit for what I try to achieve – make a few XQuery functions available database-wide.) Best, Julian Am 24.06.24 um 11:43 schrieb Jean-Paul Rehr: > Dear Julian, > > >Is it even possible to include XSLTs in a library package in a manner > that they can be loaded into XQuery? > > I assume by "library package" you mean library module? I do this all > the time without an issue. It's just another XML document. > > However I have a doubt about this path: > > >doc('./CMIF-base.xsl') > > Have you tested this with the full explicit path to the document? e.g. > "/db/apps/myapp/CMIF-base.xsl" > > Cheers, > JPR > > > On Mon, Jun 24, 2024 at 11:35 AM Julian Jarosch > <jul...@ad...> wrote: > > Hello everyone, > > I’m trying to use XSLT stylesheets in an XQuery module in a > library package, along the lines of (simplified example): > > declare variable $template := doc('./CMIF-base.xsl'); > > The current actual code is here: > > https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25 > > I had successfully tested this as an XQuery module written > directly in eXist/eXide. It stopped working when I installed it as > a library package, as far as I can tell. > > By “stopped working” I mean that the variable which is supposed to > contain the stylesheet document ($template in the example) remains > empty and the transform:transform() function fails because of a > missing stylesheet argument. > > Currently, it seems to me that the cause is with the library > package? Is it even possible to include XSLTs in a library package > in a manner that they can be loaded into XQuery? > > Thanks for any guidance – presumably for pointing out an egregious > oversight on my end :-) > > Kind regards, > Julian > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Jean-Paul R. <re...@gm...> - 2024-06-24 09:43:45
|
Dear Julian,
>Is it even possible to include XSLTs in a library package in a manner that
they can be loaded into XQuery?
I assume by "library package" you mean library module? I do this all the
time without an issue. It's just another XML document.
However I have a doubt about this path:
>doc('./CMIF-base.xsl')
Have you tested this with the full explicit path to the document? e.g.
"/db/apps/myapp/CMIF-base.xsl"
Cheers,
JPR
On Mon, Jun 24, 2024 at 11:35 AM Julian Jarosch <jul...@ad...>
wrote:
> Hello everyone,
>
> I’m trying to use XSLT stylesheets in an XQuery module in a library
> package, along the lines of (simplified example):
>
> declare variable $template := doc('./CMIF-base.xsl');
>
> The current actual code is here:
>
>
> https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25
>
> I had successfully tested this as an XQuery module written directly in
> eXist/eXide. It stopped working when I installed it as a library package,
> as far as I can tell.
>
> By “stopped working” I mean that the variable which is supposed to contain
> the stylesheet document ($template in the example) remains empty and the
> transform:transform() function fails because of a missing stylesheet
> argument.
>
> Currently, it seems to me that the cause is with the library package? Is
> it even possible to include XSLTs in a library package in a manner that
> they can be loaded into XQuery?
>
> Thanks for any guidance – presumably for pointing out an egregious
> oversight on my end :-)
>
> Kind regards,
> Julian
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
|
|
From: Julian J. <jul...@ad...> - 2024-06-24 09:34:48
|
Hello everyone,
I’m trying to use XSLT stylesheets in an XQuery module in a library
package, along the lines of (simplified example):
declare variable $template := doc('./CMIF-base.xsl');
The current actual code is here:
https://github.com/digicademy/cmiferator/blob/78b2725bf9fcc163fc48df0a96c436fadeefcef6/library-package/content/cmiferator.xqm#L25
I had successfully tested this as an XQuery module written directly in
eXist/eXide. It stopped working when I installed it as a library
package, as far as I can tell.
By “stopped working” I mean that the variable which is supposed to
contain the stylesheet document ($template in the example) remains empty
and the transform:transform() function fails because of a missing
stylesheet argument.
Currently, it seems to me that the cause is with the library package? Is
it even possible to include XSLTs in a library package in a manner that
they can be loaded into XQuery?
Thanks for any guidance – presumably for pointing out an egregious
oversight on my end :-)
Kind regards,
Julian
|
602 messages has been excluded from this view by a project administrator.
