exist-development Mailing List for eXist-db (Page 2)

exist-development — eXist Developer's List

You can subscribe to this list here.

2009	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (22)	Nov (85)	Dec (20)
2010	Jan (47)	Feb (127)	Mar (268)	Apr (78)	May (47)	Jun (38)	Jul (131)	Aug (221)	Sep (187)	Oct (54)	Nov (111)	Dec (84)
2011	Jan (152)	Feb (106)	Mar (94)	Apr (90)	May (53)	Jun (20)	Jul (24)	Aug (37)	Sep (32)	Oct (70)	Nov (22)	Dec (15)
2012	Jan (33)	Feb (110)	Mar (24)	Apr (1)	May (11)	Jun (8)	Jul (12)	Aug (37)	Sep (39)	Oct (81)	Nov (38)	Dec (50)
2013	Jan (23)	Feb (53)	Mar (23)	Apr (5)	May (19)	Jun (16)	Jul (16)	Aug (9)	Sep (21)	Oct (1)	Nov (2)	Dec (8)
2014	Jan (16)	Feb (6)	Mar (27)	Apr (1)	May (10)	Jun (1)	Jul (4)	Aug (10)	Sep (19)	Oct (22)	Nov (4)	Dec (6)
2015	Jan (3)	Feb (6)	Mar (9)	Apr	May (11)	Jun (23)	Jul (14)	Aug (10)	Sep (10)	Oct (9)	Nov (18)	Dec (4)
2016	Jan (5)	Feb (5)	Mar	Apr (2)	May (15)	Jun (2)	Jul (8)	Aug (2)	Sep (6)	Oct	Nov	Dec
2017	Jan (2)	Feb (12)	Mar (22)	Apr (6)	May	Jun	Jul (1)	Aug (1)	Sep (5)	Oct (2)	Nov	Dec
2018	Jan (2)	Feb	Mar	Apr	May	Jun (5)	Jul (3)	Aug	Sep (7)	Oct (19)	Nov	Dec
2021	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec
2022	Jan	Feb	Mar	Apr	May	Jun (3)	Jul	Aug	Sep	Oct	Nov	Dec

Flat | Threaded

<< < 1 2 3 4 .. 128 > >> (Page 2 of 128)

[Exist-development] How to run a specific group of eXist tests?

From: Stanislav <st...@gm...> - 2018-09-26 15:43:16

Hi guys,

I know that invoking
*./build.sh test*

runs all test,
but is there a way to run only a specific group of tests ?

(Asking this, because on my laptop it takes ~28 min. to run the complete
test suite)

/Stanislav

[Exist-development] Need some explanation on classes NodePath and QName

From: Stanislav <st...@gm...> - 2018-09-11 19:49:39

Hi guys,

Stanislav here (I am new to this list).
It started with this:
* [Exist-open] Are more elaborate xpath expressions allowed in Lucene's
index config <text match='...'/>
<https://sourceforge.net/p/exist/mailman/message/36392026/>*

Then I went to clone, build and then debug/trace exist,
and it turned out NodePath and QName are not suited to handle 'more
elaborate xpath expressions'

I started modifying them (locally).
I introduced (a minimalist) change - namely that QName should honor its
nameType which could be any of { UNKNOWN, ELEMENT, ATTRIBUTE }
and changed QName.compareTo() and .equals() methods to compare also this
field.
Alas, this prevented exist from normal startup as line 214 of
ConfigurationImpl.java consists of:

Node attr = attrs.getNamedItem("key");

which in turn invokes NamedNodeMapImpl.getNamedItem():

@Override
public Node getNamedItem(final String name) {
    try {
        return getNamedItem(new QName(name));
    } catch (final QName.IllegalQNameException e) {
        throw new DOMException(DOMException.INVALID_CHARACTER_ERR,
"Invalid name");
    }
}

And the problem is the newly created new QName(name) has its nameType set
(by default) to ELEMENT,
while the one stored in the map is of nameType ATTRIBUTE -- and the newly
modified QName.equals() method discerns between those two, as their
nameType(s) are different.

I am not sure what would be the right question in this situation, so I will
try with:
How come?

Kindly,
/Stanislav

Re: [Exist-development] Changing exist-db admin password

From: David L. <dav...@oe...> - 2018-09-06 17:07:44

Hi Adam,

Firstly, thanks for the quick response.

> I believe the mechanism used is typically to take the source code of the version you are using, and then build a version where the password checks are disabled. You then use that version to extract the data.
Hahaha. Ok. 

Is that process described somewhere (or can you summarise)? or is there a grep/sed that might help me reconstruct it.

> Coincidentally I just noticed you are in Oxford. I will be there next week for the XML Summer School at St. Edmund Hall. I might be able to spare an hour if I I could be of some assistance?
Thanks for the offer. I’m in Oxford next Friday (otherwise, I’m in London), and in an ideal world, I’d have things working by then (and that day’s a bit crammed). If I can’t progress, though, I might just take you up on that!

David

> 
> On 6 September 2018 at 15:32, David Lewis <dav...@oe...> wrote:
> I have an old install of exist-db (v2.2) on a headless Linux system that I’d like to get the data out from, and I can’t find the admin password. I have root command-line access.
> 
> Is it possible to either change the password or get a data dump from the command line?
> 
> Thanks,
> 
> David
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
> 
> 
> 
> -- 
> Adam Retter
> 
> eXist Core Developer
> { United Kingdom / United States }
> ad...@ex...

Re: [Exist-development] Changing exist-db admin password

From: Adam R. <ad...@ex...> - 2018-09-06 16:56:46

I believe the mechanism used is typically to take the source code of the
version you are using, and then build a version where the password checks
are disabled. You then use that version to extract the data.

Coincidentally I just noticed you are in Oxford. I will be there next week
for the XML Summer School at St. Edmund Hall. I might be able to spare an
hour if I I could be of some assistance?

On 6 September 2018 at 15:32, David Lewis <dav...@oe...> wrote:

> I have an old install of exist-db (v2.2) on a headless Linux system that
> I’d like to get the data out from, and I can’t find the admin password. I
> have root command-line access.
>
> Is it possible to either change the password or get a data dump from the
> command line?
>
> Thanks,
>
> David
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>

-- 
Adam Retter

eXist Core Developer
{ United Kingdom / United States }
ad...@ex...

[Exist-development] Changing exist-db admin password

From: David L. <dav...@oe...> - 2018-09-06 10:20:21

I have an old install of exist-db (v2.2) on a headless Linux system that I’d like to get the data out from, and I can’t find the admin password. I have root command-line access.

Is it possible to either change the password or get a data dump from the command line?

Thanks,

David

[Exist-development] I have an update on the xqDoc XAR

From: Loren C. <lor...@gm...> - 2018-07-31 04:04:42

Attachments: signature.asc

I figured out that the problem that I had was due to the xqdoc extension in eXist-db.  I had a conflict of classes.

If you removed extensions/xqdoc from eXist-db (5.0 base)

Perform mvn install on xqdoc-core and mvn package on xqDoc

Install the xqDoc xar file

Run the following in eXide


xquery version "1.0";

import module namespace xqdoc = "https://xqdoc.org/exist-db/ns/xqDoc/my-java-module";
let $nl := "&#10;"
let $test := fn:string-join(
    (
'xquery version "1.0";',
'',
'module namespace s="http://example.com/s";',
'',
'declare function s:hello() as xs:string {',
'    "hello world"',
'};'
), $nl)
return xqdoc:parse($test)


Resulting in

<?xml version="1.0" encoding="UTF-8"?>
<xqdoc:xqdoc xmlns:xqdoc="http://www.xqdoc.org/1.0">
    <xqdoc:control>
        <xqdoc:date>Mon Jul 30 21:43:23 EDT 2018</xqdoc:date>
        <xqdoc:version>1.1</xqdoc:version>
    </xqdoc:control>
    <xqdoc:module type="library">
        <xqdoc:uri>http://example.com/s</xqdoc:uri>
        <xqdoc:name/>
        <xqdoc:body xml:space="preserve">xquery version "1.0";

module namespace s="http://example.com/s";

declare function s:hello() as xs:string {
    "hello world"
};
</xqdoc:body>
    </xqdoc:module>
    <xqdoc:functions>
        <xqdoc:function>
            <xqdoc:name>hello</xqdoc:name>
            <xqdoc:signature>declare function hello() as xs:string</xqdoc:signature>
            <xqdoc:body xml:space="preserve">declare function s:hello() as xs:string{
    "hello world"
};</xqdoc:body>
        </xqdoc:function>
    </xqdoc:functions>
</xqdoc:xqdoc>


My plans are to move the functionality of the xqDoc extension into the xqDoc XAR file
Come up with a structure to have the parsed xqDoc grouped by the individual applications as well as the shared scripts like FunctX.
Rework the design of the fundocs
Utilize the restxq annotations to create a swagger view
Improve the function doc view utilizing called functions that are recorded in the xqDoc file to make a hyperlinks to the documentation for the called function
http://demo.easymetahub.com:8005/get-module.xqy?module=http://simple.example.com <http://demo.easymetahub.com:8005/get-module.xqy?module=http://simple.example.com>
Change it to a polymer2 application

There is a need to come up with a comprehensive set of test cases for the xqdoc-core project, so that there is a thorough test of all XQuery 3.1 capabilities.

I would like to get feedback from people to make sure that it is a comprehensive source documentation app.  I would also like to get ideas of how to incorporate example code for the functions to show developers how to utilize the functions.  I also remember talk of having the documentation of a function to utilize markdown in place of html.

Loren