exist-development — eXist Developer's List

Re: [Exist-development] Code freeze from 12:00 UTC 2017-03-05

[Dannes W. <da...@ex...>]

good stuff!

eXist-db Native XML Database
http://www.exist-db.org



> On 5 Mar 2017, at 13:05 , Adam Retter <ad...@ex...> wrote:
> 
> Just to remind everyone, that inline with the agreed preparation of
> the release of eXist 3.1.0 there is now a code freeze in place until
> release (estimated to be on 2017-03-07).
> 
> In effect this means that no PRs are to be merged to the following
> repositories during the freeze:
> 
> https://github.com/eXist-db/exist
> https://github.com/eXist-db/documentation
> https://github.com/wolfgangmm/eXide
> https://github.com/eXist-db/dashboard
> https://github.com/eXist-db/shared-resources
> https://github.com/eXist-db/demo-apps
> 
> The only exception will be PRs that address release concerns, such as
> incrementing versioning information. I will prepare and submit PRs for
> those over the next 1-2 days.
> 
> I would ask developers to now move their focus towards testing and
> reporting regressions for the upcoming release.
> 
> -- 
> Adam Retter
> 
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
> 
> ------------------------------------------------------------------------------
> 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

[Exist-development] Code freeze from 12:00 UTC 2017-03-05

[Adam R. <ad...@ex...>]

Just to remind everyone, that inline with the agreed preparation of
the release of eXist 3.1.0 there is now a code freeze in place until
release (estimated to be on 2017-03-07).

In effect this means that no PRs are to be merged to the following
repositories during the freeze:

https://github.com/eXist-db/exist
https://github.com/eXist-db/documentation
https://github.com/wolfgangmm/eXide
https://github.com/eXist-db/dashboard
https://github.com/eXist-db/shared-resources
https://github.com/eXist-db/demo-apps

The only exception will be PRs that address release concerns, such as
incrementing versioning information. I will prepare and submit PRs for
those over the next 1-2 days.

I would ask developers to now move their focus towards testing and
reporting regressions for the upcoming release.

-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] eXist 3.0 installation exception: Unsupported major.minor version 52.0

[Adam R. <ad...@ex...>]

Dmitriy is correct I think.

It is very unlikely that you are actually using Java 8, even if you
have it installed somewhere.

Please try setting the environment variable JAVA_HOME=/opt/jdk1.8.0_121

Also please ensure that if you run `java -version` from your home
folder without an absolute path, that it reports Java 8, if not you
also need to fix your PATH environment variable.

On 26 February 2017 at 13:23, Masoud Vakili <ma...@gm...> wrote:
> no my java is 8;
> /opt/jdk1.8.0_121/bin/java -version
> java version "1.8.0_121"
> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>
> by this, got the error too.
>
> On Sun, Feb 26, 2017 at 4:17 PM, Dmitriy Shabanov <sha...@gm...>
> wrote:
>>
>>
>>
>> On Sun, Feb 26, 2017 at 3:41 PM, Masoud Vakili <ma...@gm...> wrote:
>>>
>>> Hi all;
>>> I am trying to install eXist-db 3.0 on Centos 7 with oracle java 8, but
>>> at the end of installation, below exception will throw:
>>
>>
>> because you use java 7 not 8:
>>
>>>
>>> java -version
>>> java version "1.7.0_80"
>>> Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
>>> Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
>>>
>>
>>
>>
>> --
>> Dmitriy Shabanov
>
>
>
> ------------------------------------------------------------------------------
> 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 Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] eXist 3.0 installation exception: Unsupported major.minor version 52.0

[Masoud V. <ma...@gm...>]

no my java is 8;
/opt/jdk1.8.0_121/bin/java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

by this, got the error too.

On Sun, Feb 26, 2017 at 4:17 PM, Dmitriy Shabanov <sha...@gm...>
wrote:

>
>
> On Sun, Feb 26, 2017 at 3:41 PM, Masoud Vakili <ma...@gm...> wrote:
>
>> Hi all;
>> I am trying to install eXist-db 3.0 on Centos 7 with oracle java 8, but
>> at the end of installation, below exception will throw:
>>
>
> because you use java 7 not 8:
>
>
>> java -version
>> java version "1.7.0_80"
>> Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
>> Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
>>
>>
>
>
> --
> Dmitriy Shabanov
>

Re: [Exist-development] eXist 3.0 installation exception: Unsupported major.minor version 52.0

[Dmitriy S. <sha...@gm...>]

On Sun, Feb 26, 2017 at 3:41 PM, Masoud Vakili <ma...@gm...> wrote:

> Hi all;
> I am trying to install eXist-db 3.0 on Centos 7 with oracle java 8, but at
> the end of installation, below exception will throw:
>

because you use java 7 not 8:


> java -version
> java version "1.7.0_80"
> Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
>
>


-- 
Dmitriy Shabanov

[Exist-development] eXist 3.0 installation exception: Unsupported major.minor version 52.0

[Masoud V. <ma...@gm...>]

Hi all;
I am trying to install eXist-db 3.0 on Centos 7 with oracle java 8, but at
the end of installation, below exception will throw:

java -jar /home/masoud/eXist-db-setup-3.0-acd0c14.jar
Select target path [/opt]
/home/exist/eXist3.0
press 1 to continue, 2 to quit, 3 to redisplay
1
Set Data Directory
Please select a directory where eXist-db will keep its data files. On
Windows, this should be outside the 'Program Files' directory. Please make
sure eXist can write to the directory it is installed in.
Data dir:  [webapp/WEB-INF/data]

press 1 to continue, 2 to quit, 3 to redisplay
1
Set Admin Password and Configure Memory
Enter password:  []

Enter password:  []

------------------------------------------

Maximum memory in MB: [2048]

Cache memory in MB: [256]

press 1 to continue, 2 to quit, 3 to redisplay
1
[ Starting to unpack ]
[ Processing package: Sources (1/15) ]
[ Processing package: Core (2/15) ]
[ Processing package: Apps (3/15) ]
[ Processing package: shared (4/15) ]
[ Processing package: bf-XForms (5/15) ]
[ Processing package: dashboard (6/15) ]
[ Processing package: demo (7/15) ]
[ Processing package: doc (8/15) ]
[ Processing package: eXide (9/15) ]
[ Processing package: fundocs (10/15) ]
[ Processing package: markdown (11/15) ]
[ Processing package: monex (12/15) ]
[ Processing package: xqjson (13/15) ]
[ Processing package: xsltforms (14/15) ]
[ Processing package: xsltforms-demo (15/15) ]
[ Unpacking finished ]
[ Starting processing ]
Starting process Setting admin password ... (1/1)
Exception in thread "main" java.lang.UnsupportedClassVersionError:
org/exist/start/Main : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
[ Console installation done ]

java -version
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)

uname -a
Linux foo 3.10.0-327.28.3.el7.x86_64 #1 SMP Thu Aug 18 19:05:49 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux

please help.
thanks

Re: [Exist-development] HTTP ERROR 404, when change /context in eXist-db 3.0

[Masoud V. <ma...@gm...>]

sorry I forgot the explain complately!
when i installed eXist 3.0, I changed contextPath to / (slash); then
started exist and went to localhost:8080 and it redirect to
http://localhost:8080/exist, automatically and received 404 error.


On Sat, Feb 25, 2017 at 4:14 PM, Masoud Vakili <ma...@gm...> wrote:

> Hi all,
> unfortunately, when i installed eXist-db 3.0 in linux (with java oracle
> 1.8.0_112 in fedora25 and centos 7), I got 404 error when I go to
> localhost:8080;
> HTTP ERROR 404
>
> Problem accessing /exist. Reason:
>
>     Not Found
>
> ------------------------------
> Powered by Jetty:// 9.3.9.v20160517 <http://eclipse.org/jetty>
> ------------------------------
>
> it redirects to http://localhost:8080/exist and issued error!
> please help me
> Thanks
>

[Exist-development] HTTP ERROR 404, when change /context in eXist-db 3.0

[Masoud V. <ma...@gm...>]

Hi all,
unfortunately, when i installed eXist-db 3.0 in linux (with java oracle
1.8.0_112 in fedora25 and centos 7), I got 404 error when I go to
localhost:8080;
HTTP ERROR 404

Problem accessing /exist. Reason:

    Not Found

------------------------------
Powered by Jetty:// 9.3.9.v20160517 <http://eclipse.org/jetty>
------------------------------

it redirects to http://localhost:8080/exist and issued error!
please help me
Thanks

Re: [Exist-development] Wrong git tag and version in eXist-db 3.0

[Adam R. <ad...@ex...>]

Also I just realised that the merge to `master` was not done for 3.0 release...

On 11 February 2017 at 09:51, Adam Retter <ad...@ex...> wrote:
>> *almost* all users will use the dmg or jar, so issue will be reported with
>> the correct information. others will run from ‘develop’ which contains the
>> correct information as well. So here is not a real issue.
>
> DMG and Jar must have been built from 3.0 tag in Git... so it has the
> same problem!!!
>
>
>> About the pulled-in PR: these are ONLY github templates, which *by
>> definition* must be in *develop*; so also here there is not a real an
>> serious issue (certainly if you see things from a pragmatic point of viewe)
>
> The problem is that this adds non-critical changes to 3.0.1 which
> increases the risk in 3.0.1 and also muddies the history.
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] Wrong git tag and version in eXist-db 3.0

[Adam R. <ad...@ex...>]

> *almost* all users will use the dmg or jar, so issue will be reported with
> the correct information. others will run from ‘develop’ which contains the
> correct information as well. So here is not a real issue.

DMG and Jar must have been built from 3.0 tag in Git... so it has the
same problem!!!


> About the pulled-in PR: these are ONLY github templates, which *by
> definition* must be in *develop*; so also here there is not a real an
> serious issue (certainly if you see things from a pragmatic point of viewe)

The problem is that this adds non-critical changes to 3.0.1 which
increases the risk in 3.0.1 and also muddies the history.



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] Wrong git tag and version in eXist-db 3.0

[Dannes W. <da...@ex...>]

Adam,

Yes we should make things in order, but it is NOT that bad as you write to the community.

About versions:  So the content of the released material is:

project.name = eXist-db
project.version = 3.0
project.version.numeric = 3.0.4
project.source = develop
project.codename = Berlin

*almost* all users will use the dmg or jar, so issue will be reported with the correct information. others will run from ‘develop’ which contains the correct information as well. So here is not a real issue.


About the pulled-in PR: these are ONLY github templates, which *by definition* must be in *develop*; so also here there is not a real an serious issue (certainly if you see things from a pragmatic point of viewe)

regards

Dannes

Re: [Exist-development] Wrong git tag and version in eXist-db 3.0

[Dannes W. <da...@ex...>]

I middes your mail of last evening, need to read it….

--
eXist-db Native XML Database
http://www.exist-db.org



> On 11 Feb 2017, at 10:21 , Adam Retter <ad...@ex...> wrote:
> 
> Guys, please stop merging PRs.

Re: [Exist-development] Wrong git tag and version in eXist-db 3.0

[Adam R. <ad...@ex...>]

Guys, please stop merging PRs. I see that one has been merged, this
just makes the situation even worse :-(

Also, will someone please respond to this email and let me know that
we have a plan to fix this ASAP. I am happy to do the work, all I am
missing is the key for building DMG on MacOSX if someone can provide
that I will fix this all today.

On 9 February 2017 at 19:40, Adam Retter <ad...@ex...> wrote:
> Dear developers,
>
> There seems to have been a problem with creating and releasing eXist-db 3.0.
>
> The Git tag "eXist-3.0" points to commit acd0c14, but should have been
> 9911af8. This leads to concrete problems, with builds of eXist-3.0 tag
> reporting the wrong version, to see what I mean:
>
> $ git clone https://github.com/exist-db/exist.git
> $ git checkout eXist-3.0
> $ cat build.properties
>
> project.name = eXist-db
> project.version = 3.0.RC2
> project.version.numeric = 3.0.3
> project.source = develop
> project.codename = Berlin
>
> ...
>
> So this leads to eXist-3.0 reporting its version as "3.0.RC".
>
> The main problem here is that when users report issues via the mailing
> list or GitHub and they ask us which version they are running, they
> will tell us 3.0.RC2 which is incorrect. It is very likely we will
> then tell them to install the final version of eXist-3.0 which will
> waste their time and ours and not solve anything... especially in a
> few years when we forget and are confused why after upgrading they are
> still running the same version.
>
> I am also going to assume that as releases must always be built from
> git tags, that the actual binary release of eXist-3.0 exhibits exactly
> the same problem as the source base.
>
> So I think we can assume that 3.0 has a critical problem, in so far as
> it identifies itself as the wrong version, which is going to confuse
> everyone.
>
> I think out best option is to immediately create a 3.0.1 release and
> announce that. We should definitely NOT try and fix 3.0 and re-release
> it, having two versions of "3.0" which are different will only add to
> the chaos.
>
> If you agree, this is the process that I would suggest to get to 3.0.1
> so that we don't have any more version issues:
>
> 1) Update build.properties in the develop branch to reflect 3.0.1.RC1
> and commit (should have been does as first commit after 3.0
> release!!!)
>
> 2) Make any **critical** fix commits to develop branch (maybe none,
> although I know Joe Wiz would deeply like to see newer eXide version)
>
> 3) (Assuming you still don't want to do Release Candidates for some
> reason) Update build.properties in develop branch to be 3.0.1 and
> commit
>
> 4) tag (and preferably sign) eXist-3.0.1 as the HEAD of develop branch and push
>
> 5) Update build.properties in develop branch to be 3.0.2.RC1 and commit and push
>
> 6) Checkout the eXist-3.0.1 tag, build the code and release the binary files
>
>
>
> p.s. I get that mistakes happen and that is fine, but let's just get
> this done and sorted ASAP so that we can reduce the window of
> confusion and frustration for both our users and developers.
>
> Cheers Adam.
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

[Exist-development] Wrong git tag and version in eXist-db 3.0

[Adam R. <ad...@ex...>]

Dear developers,

There seems to have been a problem with creating and releasing eXist-db 3.0.

The Git tag "eXist-3.0" points to commit acd0c14, but should have been
9911af8. This leads to concrete problems, with builds of eXist-3.0 tag
reporting the wrong version, to see what I mean:

$ git clone https://github.com/exist-db/exist.git
$ git checkout eXist-3.0
$ cat build.properties

project.name = eXist-db
project.version = 3.0.RC2
project.version.numeric = 3.0.3
project.source = develop
project.codename = Berlin

...

So this leads to eXist-3.0 reporting its version as "3.0.RC".

The main problem here is that when users report issues via the mailing
list or GitHub and they ask us which version they are running, they
will tell us 3.0.RC2 which is incorrect. It is very likely we will
then tell them to install the final version of eXist-3.0 which will
waste their time and ours and not solve anything... especially in a
few years when we forget and are confused why after upgrading they are
still running the same version.

I am also going to assume that as releases must always be built from
git tags, that the actual binary release of eXist-3.0 exhibits exactly
the same problem as the source base.

So I think we can assume that 3.0 has a critical problem, in so far as
it identifies itself as the wrong version, which is going to confuse
everyone.

I think out best option is to immediately create a 3.0.1 release and
announce that. We should definitely NOT try and fix 3.0 and re-release
it, having two versions of "3.0" which are different will only add to
the chaos.

If you agree, this is the process that I would suggest to get to 3.0.1
so that we don't have any more version issues:

1) Update build.properties in the develop branch to reflect 3.0.1.RC1
and commit (should have been does as first commit after 3.0
release!!!)

2) Make any **critical** fix commits to develop branch (maybe none,
although I know Joe Wiz would deeply like to see newer eXide version)

3) (Assuming you still don't want to do Release Candidates for some
reason) Update build.properties in develop branch to be 3.0.1 and
commit

4) tag (and preferably sign) eXist-3.0.1 as the HEAD of develop branch and push

5) Update build.properties in develop branch to be 3.0.2.RC1 and commit and push

6) Checkout the eXist-3.0.1 tag, build the code and release the binary files



p.s. I get that mistakes happen and that is fine, but let's just get
this done and sorted ASAP so that we can reduce the window of
confusion and frustration for both our users and developers.

Cheers Adam.


-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] eXist-db 3.0 release date

[Dannes W. <da...@ex...>]

Strong rumors (....) point to a release before/around  February 8.... XML Prague 

Regards

Dannes

--
www.exist-db.org

> On 29 Jan 2017, at 12:40, Masoud Vakili <ma...@gm...> wrote:
> 
> what is eXist-db 3.0 Schedule?
> when is its release date?

[Exist-development] eXist-db 3.0 release date

[Masoud V. <ma...@gm...>]

Hi all;
what is eXist-db 3.0 Schedule?
when is its release date?

thanks

Re: [Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Adam R. <ad...@ex...>]

> 4. uploaded the QT3-test-suite to /db/QT3-test-suite, to reflect the
> $path variable defined in fots.xq line 12, but eXide complained of a
> syntax error on this line:
>
>     > error found while executing expression:
> org.exist.xquery.XPathException: err:XPST0003 expecting semicolon ';',
> found ':' [at line 12, column 46]
>
> 5. I worked around the error by deleting the "external" keyword from
> line 12. Odd that the "external" keyword would raise an error, no?
> The line in question:
>
>     https://github.com/adamretter/fots-basex/blob/exist/fots.xq#L12


XQuery 1.0 only allowed you to declare a variable as either static,
i.e. with a known value or as external. XQuery 3.0 allowed you to do
that but also to specify a default value for an external variable if
no value is given to be injected from an external context.

I suspect that eXist hasn't been updated to 3.0 spec here and that the
problem is not the `external` keyword but rather the default value
that appears after that.


> Anyway, next, eXide reported an error that I haven't been able to overcome yet:
>
>> error found while loading module fots: Error while loading module fots.xqm: error found while loading module env: Error while loading module fots-environment.xqm: prefix 'file' bind to 'http://exist-db.org/xquery/file'
>
> I took a look at fots.xqm, and it imports the expath file module:
>
>   https://github.com/adamretter/fots-basex/blob/exist/fots-environment.xqm#L16
>
> Thinking that your implementation of the expath file module might do
> the trick, I cloned
> https://github.com/adamretter/exist-expath-file-module and built the
> xar as directed in the readme. But when I tried to deploy the .xar
> file via Dashboard > Package Manager, I got this error:
>
>> Inconsistent package descriptor, the JAR file is not in the package: ntinuations-library_2.11-1.0.1.jar
>
> The closest name I can find to this is in
> target/file-module-1.0-SNAPSHOT-bin/lib/scala-continuations-library_2.11-1.0.1.jar,
> but I don't know how to overcome the error.  Can you suggest a way
> forward?  I've pasted in my console log from the maven builds here:
> http://pastebin.com/y54v4q3s.


Ah right! Yes so unfortunately I also had problems with generating
Xar's; I am using Claudius's XAR plugin for Maven, but unfortunately
it seems to scramble the names of the Xar files inside the exist.xml
file of the Xar package.

You can manually fix it by editing the exist.xml file inside the Xar
and ensuring that each <jar> entry correctly matches the name of a Jar
file in the package. You will see that most have lost the first few
characters from their file name due to some bug in the plugin.

> Should I keep trying to get the expath file module installed &
> registered with the namespace prefix "file" (I fear this would collide
> with eXist's own file module with this namespace prefix), or should I
> drop the idea of installing the expath file module and just adapt the
> code to use eXist's file module?

You can likely use the EXPath module, but you will need to unregister
the eXist file module from conf.xml and restart first.

> Thanks for any guidance,
> Joe
>
> On Tue, Jan 19, 2016 at 5:02 AM, Adam Retter <ad...@ex...> wrote:
>> Hey Joe,
>>
>> Good question!
>>
>> Ultimately it is down to a lack of resources to be able to do this.
>> However, the good news is that you could help ;-)
>>
>> Leo from BaseX started a test-suite harness for the W3C XQuery Test
>> Suite, he wrote it in XQuery for BaseX. I started porting it over to
>> eXist early last year, but never had the time or pressing need to
>> complete it. My branch with the changes for eXist is here -
>> https://github.com/adamretter/fots-basex/tree/exist. Whilst a work in
>> progress, I think I was able to get some tests running. The nice thing
>> is that EXPath uses the same Test Suite format as W3C, so if we can
>> get a test harness working, we can run many tests :-)
>>
>> Perhaps this is something you would like to pick up and work on? I
>> could certainly offer guidance if you get stuck... but well I think
>> you are probably a pretty good XQuery programmer ;-)
>>
>> Cheers Adam.
>>
>> On 19 January 2016 at 04:33, Joe Wicentowski <jo...@gm...> wrote:
>>> Hi all,
>>>
>>> I notice eXist isn't included in this round of tests.  I'd be
>>> interested to know what are the barriers or obstacles to running the
>>> tests and participating in these exercises?
>>>
>>> I imagine the release of eXist 3.0 is a higher priority for the
>>> project than passing a not-yet-final spec, among others.  But I think
>>> that eXist's presence at some point would help the WG's work and
>>> strengthen the spec's goal of being supported by many implementations.
>>> Even if eXist doesn't promise complete XQ3.1 coverage (heck, they keep
>>> adding new features like templates!), the areas it does support are, I
>>> think, quite well developed - and this hard work would be worth
>>> celebrating through inclusion in these tests.
>>>
>>> Joe
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: O'Neil Delpratt <on...@sa...>
>>> Date: Mon, Jan 18, 2016 at 9:40 AM
>>> Subject: Reporting on QT3 test results for the 3.1 Specs
>>> To: pub...@w3...
>>>
>>>
>>> Dear All,
>>>
>>> I have re-generated the reports on the implementation results received
>>> for the QT3 test suite. See update:
>>> http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html
>>> We now have three implementations for XQuery 3.1, with one being
>>> anonymous. However we only have one for XPath 3.1.
>>>
>>> We have been working on the main page today. Specifically the stats on
>>> the optional features. We found that there were some overlap reported
>>> in the passes and failures. For example under ‘staticTyping’ it is
>>> reported that there are 75 test not being passed by any
>>> implementation. Under the 'higherOrderFunction’ feature we have 18
>>> test passed by no implementation. If you inspect the
>>> higherOrderFunction tests more closely we will see that 17 of these
>>> tests depend on staticTyping therefore the underlying reason for the
>>> higherOrderFunction failures is to do with staticTyping. With what I
>>> have said in mind we think it helpful to show the combination of
>>> optional features for the test case.
>>>
>>> I welcome feedback on your preference of presentation on the Optional
>>> Features section. I find 2) much more useful:
>>>
>>> 1) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optFeatures
>>> 2) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optComboFeatures
>>>
>>>
>>> Using 1) or 2) we observe that we have 75 tests with dependency on
>>> staticTyping not being passed by any implementation (including those
>>> with combinations of other dependencies).  I would like to ask if it
>>> still merits having tests on static typing?
>>>
>>> kind regards,
>>>
>>>
>>> -------------------------------
>>> O'Neil Delpratt
>>> Software Developer, Saxonica Limited
>>> Email: on...@sa...
>>> Twitter: https://twitter.com/ond1
>>> Tel: +44 118 946 5894
>>> Web: http://www.saxonica.com
>>> Saxonica Community site: http://dev.saxonica.com
>>> Bug tracking site: https://saxonica.plan.io/
>>>
>>> ------------------------------------------------------------------------------
>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>> Monitor end-to-end web transactions and take corrective actions now
>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Joe W. <jo...@gm...>]

Okay, I used util:eval-inline, and got past the issue with "declare
context item".  I've committed my work thus far here:

  https://github.com/joewiz/fots-basex/

It still gets caught up in cardinality issues surrounding the
check:error() function, which I haven't yet figured out.  That said,
the logs show that quite a few tests are actually running.  Here's the
exist.log logging: http://pastebin.com/3P8nzXmm.

It dies on this:

  fn:collection('http://www.w3.org/2010/09/qt-fots-catalog/integers')

I asked about this on xquery-talk, since I have no idea what this is!

If anyone wants to participate, you can check out qt3 with cvs:

# install cvs on macos with homebrew, and prepare a directory
$ brew install cvs
$ mkdir qt3
$ cd qt3

# connect
$ cvs -d :pserver:ano...@de...:/sources/public login
# enter password "anonymous" (sans quote)

# checkout
$ cvs -d :pserver:ano...@de...:/sources/public checkout
2011/QT3-test-suite
# wait for lengthy download to complete

Joe

On Thu, Sep 8, 2016 at 2:45 PM, Joe Wicentowski <jo...@gm...> wrote:
> If eXist doesn't support "declare context item", then perhaps I need
> to modify the test suite's "eval" behavior to use
> util:eval-with-context() and somehow get the context item fed into the
> $eval-context-item parameter.  The relevant function docs:
>
>   http://exist-db.org/exist/apps/fundocs/view.html?uri=http://exist-db.org/xquery/util#eval-with-context.4
>
> Joe
>
> On Thu, Sep 8, 2016 at 2:40 PM, Joe Wicentowski <jo...@gm...> wrote:
>>> I'm not familiar with this "declare context item" declaration or
>>> whether eXist supports it.
>>
>> Just a link to the spec for this declaration:
>>
>>   https://www.w3.org/TR/xquery-31/#id-context-item-declarations
>>
>> (for context :)
>>
>> Joe

Re: [Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Joe W. <jo...@gm...>]

If eXist doesn't support "declare context item", then perhaps I need
to modify the test suite's "eval" behavior to use
util:eval-with-context() and somehow get the context item fed into the
$eval-context-item parameter.  The relevant function docs:

  http://exist-db.org/exist/apps/fundocs/view.html?uri=http://exist-db.org/xquery/util#eval-with-context.4

Joe

On Thu, Sep 8, 2016 at 2:40 PM, Joe Wicentowski <jo...@gm...> wrote:
>> I'm not familiar with this "declare context item" declaration or
>> whether eXist supports it.
>
> Just a link to the spec for this declaration:
>
>   https://www.w3.org/TR/xquery-31/#id-context-item-declarations
>
> (for context :)
>
> Joe

Re: [Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Joe W. <jo...@gm...>]

> I'm not familiar with this "declare context item" declaration or
> whether eXist supports it.

Just a link to the spec for this declaration:

  https://www.w3.org/TR/xquery-31/#id-context-item-declarations

(for context :)

Joe

Re: [Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Joe W. <jo...@gm...>]

Hi Adam (or anyone else interested in getting the XQuery 3.1 test
suite running in eXist so we could report the eXist community's hard
work at supporting XQuery 3.1 features, as several other
implementations do at
https://dev.w3.org/2011/QT3-test-suite/ReportingResults31/),

I was able to get past the file module import problem simply by
commenting out this line:

  https://github.com/adamretter/fots-basex/blob/exist/fots-environment.xqm#L16

Luckily, it appears, the expath file:exists() function is basically
the same as exist's.

I'm now able to run fots.xq, and I see the output of quite a few tests
in exist.log.  But I encounter an error with the following test:

> 2016-09-08 15:05:31,148 [eXistThread-110] INFO  (LogFunction.java [eval]:151) - (Line: 97 /db/apps/fots-basex/fots.xqm) doc-uri=/db/QT3-test-suite/fn/abs.xml
> 2016-09-08 15:05:31,149 [eXistThread-110] INFO  (LogFunction.java [eval]:151) - (Line: 129 /db/apps/fots-basex/fots.xqm) query=declare base-uri "/db/QT3-test-suite/fn/"; declare context item := doc('/db/QT3-test-suite/fn/abs/e0.xml'); abs(xs:unsignedShort(.)) instance of xs:unsignedShort

Pasting this query into eXide, e.g.,

```
xquery version "3.1";

declare base-uri "/db/QT3-test-suite/fn/";
declare context item := doc('/db/QT3-test-suite/fn/abs/e0.xml');
abs(xs:unsignedShort(.)) instance of xs:unsignedShort
```

... eXide raises an error:

> Cannot compile xquery: exerr:ERROR org.exist.xquery.XPathException: err:XPST0003 unexpected token: declare [at line 4, column 1]

I'm not familiar with this "declare context item" declaration or
whether eXist supports it.  Do you by chance know if this is supported
in eXist, or how to work around this error?

Thanks,
Joe

On Thu, Sep 8, 2016 at 1:58 PM, Joe Wicentowski <jo...@gm...> wrote:
> Hi Adam,
>
> I was just starting to look at this again, having received a note that
> the xquery working group has updated several of the tests for 3.1, and
> I encountered a roadblock that I'd be grateful for your help with.
> For context, I've done the following:
>
> 1. checked out the qt3 test suite from the w3c's cvs server as
> documented at https://dev.w3.org/2011/QT3-test-suite/
> 2. cloned your exist branch of Leo Worteler's fots-basex repo
> https://github.com/adamretter/fots-basex/tree/exist
> 3. uploaded the fots-basex directory to /db/apps/fots-basex
> 4. uploaded the QT3-test-suite to /db/QT3-test-suite, to reflect the
> $path variable defined in fots.xq line 12, but eXide complained of a
> syntax error on this line:
>
>     > error found while executing expression:
> org.exist.xquery.XPathException: err:XPST0003 expecting semicolon ';',
> found ':' [at line 12, column 46]
>
> 5. I worked around the error by deleting the "external" keyword from
> line 12. Odd that the "external" keyword would raise an error, no?
> The line in question:
>
>     https://github.com/adamretter/fots-basex/blob/exist/fots.xq#L12
>
> Anyway, next, eXide reported an error that I haven't been able to overcome yet:
>
>> error found while loading module fots: Error while loading module fots.xqm: error found while loading module env: Error while loading module fots-environment.xqm: prefix 'file' bind to 'http://exist-db.org/xquery/file'
>
> I took a look at fots.xqm, and it imports the expath file module:
>
>   https://github.com/adamretter/fots-basex/blob/exist/fots-environment.xqm#L16
>
> Thinking that your implementation of the expath file module might do
> the trick, I cloned
> https://github.com/adamretter/exist-expath-file-module and built the
> xar as directed in the readme. But when I tried to deploy the .xar
> file via Dashboard > Package Manager, I got this error:
>
>> Inconsistent package descriptor, the JAR file is not in the package: ntinuations-library_2.11-1.0.1.jar
>
> The closest name I can find to this is in
> target/file-module-1.0-SNAPSHOT-bin/lib/scala-continuations-library_2.11-1.0.1.jar,
> but I don't know how to overcome the error.  Can you suggest a way
> forward?  I've pasted in my console log from the maven builds here:
> http://pastebin.com/y54v4q3s.
>
> Should I keep trying to get the expath file module installed &
> registered with the namespace prefix "file" (I fear this would collide
> with eXist's own file module with this namespace prefix), or should I
> drop the idea of installing the expath file module and just adapt the
> code to use eXist's file module?
>
> Thanks for any guidance,
> Joe
>
> On Tue, Jan 19, 2016 at 5:02 AM, Adam Retter <ad...@ex...> wrote:
>> Hey Joe,
>>
>> Good question!
>>
>> Ultimately it is down to a lack of resources to be able to do this.
>> However, the good news is that you could help ;-)
>>
>> Leo from BaseX started a test-suite harness for the W3C XQuery Test
>> Suite, he wrote it in XQuery for BaseX. I started porting it over to
>> eXist early last year, but never had the time or pressing need to
>> complete it. My branch with the changes for eXist is here -
>> https://github.com/adamretter/fots-basex/tree/exist. Whilst a work in
>> progress, I think I was able to get some tests running. The nice thing
>> is that EXPath uses the same Test Suite format as W3C, so if we can
>> get a test harness working, we can run many tests :-)
>>
>> Perhaps this is something you would like to pick up and work on? I
>> could certainly offer guidance if you get stuck... but well I think
>> you are probably a pretty good XQuery programmer ;-)
>>
>> Cheers Adam.
>>
>> On 19 January 2016 at 04:33, Joe Wicentowski <jo...@gm...> wrote:
>>> Hi all,
>>>
>>> I notice eXist isn't included in this round of tests.  I'd be
>>> interested to know what are the barriers or obstacles to running the
>>> tests and participating in these exercises?
>>>
>>> I imagine the release of eXist 3.0 is a higher priority for the
>>> project than passing a not-yet-final spec, among others.  But I think
>>> that eXist's presence at some point would help the WG's work and
>>> strengthen the spec's goal of being supported by many implementations.
>>> Even if eXist doesn't promise complete XQ3.1 coverage (heck, they keep
>>> adding new features like templates!), the areas it does support are, I
>>> think, quite well developed - and this hard work would be worth
>>> celebrating through inclusion in these tests.
>>>
>>> Joe
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: O'Neil Delpratt <on...@sa...>
>>> Date: Mon, Jan 18, 2016 at 9:40 AM
>>> Subject: Reporting on QT3 test results for the 3.1 Specs
>>> To: pub...@w3...
>>>
>>>
>>> Dear All,
>>>
>>> I have re-generated the reports on the implementation results received
>>> for the QT3 test suite. See update:
>>> http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html
>>> We now have three implementations for XQuery 3.1, with one being
>>> anonymous. However we only have one for XPath 3.1.
>>>
>>> We have been working on the main page today. Specifically the stats on
>>> the optional features. We found that there were some overlap reported
>>> in the passes and failures. For example under ‘staticTyping’ it is
>>> reported that there are 75 test not being passed by any
>>> implementation. Under the 'higherOrderFunction’ feature we have 18
>>> test passed by no implementation. If you inspect the
>>> higherOrderFunction tests more closely we will see that 17 of these
>>> tests depend on staticTyping therefore the underlying reason for the
>>> higherOrderFunction failures is to do with staticTyping. With what I
>>> have said in mind we think it helpful to show the combination of
>>> optional features for the test case.
>>>
>>> I welcome feedback on your preference of presentation on the Optional
>>> Features section. I find 2) much more useful:
>>>
>>> 1) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optFeatures
>>> 2) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optComboFeatures
>>>
>>>
>>> Using 1) or 2) we observe that we have 75 tests with dependency on
>>> staticTyping not being passed by any implementation (including those
>>> with combinations of other dependencies).  I would like to ask if it
>>> still merits having tests on static typing?
>>>
>>> kind regards,
>>>
>>>
>>> -------------------------------
>>> O'Neil Delpratt
>>> Software Developer, Saxonica Limited
>>> Email: on...@sa...
>>> Twitter: https://twitter.com/ond1
>>> Tel: +44 118 946 5894
>>> Web: http://www.saxonica.com
>>> Saxonica Community site: http://dev.saxonica.com
>>> Bug tracking site: https://saxonica.plan.io/
>>>
>>> ------------------------------------------------------------------------------
>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>> Monitor end-to-end web transactions and take corrective actions now
>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb

Re: [Exist-development] Fwd: Reporting on QT3 test results for the 3.1 Specs

[Joe W. <jo...@gm...>]

Hi Adam,

I was just starting to look at this again, having received a note that
the xquery working group has updated several of the tests for 3.1, and
I encountered a roadblock that I'd be grateful for your help with.
For context, I've done the following:

1. checked out the qt3 test suite from the w3c's cvs server as
documented at https://dev.w3.org/2011/QT3-test-suite/
2. cloned your exist branch of Leo Worteler's fots-basex repo
https://github.com/adamretter/fots-basex/tree/exist
3. uploaded the fots-basex directory to /db/apps/fots-basex
4. uploaded the QT3-test-suite to /db/QT3-test-suite, to reflect the
$path variable defined in fots.xq line 12, but eXide complained of a
syntax error on this line:

    > error found while executing expression:
org.exist.xquery.XPathException: err:XPST0003 expecting semicolon ';',
found ':' [at line 12, column 46]

5. I worked around the error by deleting the "external" keyword from
line 12. Odd that the "external" keyword would raise an error, no?
The line in question:

    https://github.com/adamretter/fots-basex/blob/exist/fots.xq#L12

Anyway, next, eXide reported an error that I haven't been able to overcome yet:

> error found while loading module fots: Error while loading module fots.xqm: error found while loading module env: Error while loading module fots-environment.xqm: prefix 'file' bind to 'http://exist-db.org/xquery/file'

I took a look at fots.xqm, and it imports the expath file module:

  https://github.com/adamretter/fots-basex/blob/exist/fots-environment.xqm#L16

Thinking that your implementation of the expath file module might do
the trick, I cloned
https://github.com/adamretter/exist-expath-file-module and built the
xar as directed in the readme. But when I tried to deploy the .xar
file via Dashboard > Package Manager, I got this error:

> Inconsistent package descriptor, the JAR file is not in the package: ntinuations-library_2.11-1.0.1.jar

The closest name I can find to this is in
target/file-module-1.0-SNAPSHOT-bin/lib/scala-continuations-library_2.11-1.0.1.jar,
but I don't know how to overcome the error.  Can you suggest a way
forward?  I've pasted in my console log from the maven builds here:
http://pastebin.com/y54v4q3s.

Should I keep trying to get the expath file module installed &
registered with the namespace prefix "file" (I fear this would collide
with eXist's own file module with this namespace prefix), or should I
drop the idea of installing the expath file module and just adapt the
code to use eXist's file module?

Thanks for any guidance,
Joe

On Tue, Jan 19, 2016 at 5:02 AM, Adam Retter <ad...@ex...> wrote:
> Hey Joe,
>
> Good question!
>
> Ultimately it is down to a lack of resources to be able to do this.
> However, the good news is that you could help ;-)
>
> Leo from BaseX started a test-suite harness for the W3C XQuery Test
> Suite, he wrote it in XQuery for BaseX. I started porting it over to
> eXist early last year, but never had the time or pressing need to
> complete it. My branch with the changes for eXist is here -
> https://github.com/adamretter/fots-basex/tree/exist. Whilst a work in
> progress, I think I was able to get some tests running. The nice thing
> is that EXPath uses the same Test Suite format as W3C, so if we can
> get a test harness working, we can run many tests :-)
>
> Perhaps this is something you would like to pick up and work on? I
> could certainly offer guidance if you get stuck... but well I think
> you are probably a pretty good XQuery programmer ;-)
>
> Cheers Adam.
>
> On 19 January 2016 at 04:33, Joe Wicentowski <jo...@gm...> wrote:
>> Hi all,
>>
>> I notice eXist isn't included in this round of tests.  I'd be
>> interested to know what are the barriers or obstacles to running the
>> tests and participating in these exercises?
>>
>> I imagine the release of eXist 3.0 is a higher priority for the
>> project than passing a not-yet-final spec, among others.  But I think
>> that eXist's presence at some point would help the WG's work and
>> strengthen the spec's goal of being supported by many implementations.
>> Even if eXist doesn't promise complete XQ3.1 coverage (heck, they keep
>> adding new features like templates!), the areas it does support are, I
>> think, quite well developed - and this hard work would be worth
>> celebrating through inclusion in these tests.
>>
>> Joe
>>
>>
>> ---------- Forwarded message ----------
>> From: O'Neil Delpratt <on...@sa...>
>> Date: Mon, Jan 18, 2016 at 9:40 AM
>> Subject: Reporting on QT3 test results for the 3.1 Specs
>> To: pub...@w3...
>>
>>
>> Dear All,
>>
>> I have re-generated the reports on the implementation results received
>> for the QT3 test suite. See update:
>> http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html
>> We now have three implementations for XQuery 3.1, with one being
>> anonymous. However we only have one for XPath 3.1.
>>
>> We have been working on the main page today. Specifically the stats on
>> the optional features. We found that there were some overlap reported
>> in the passes and failures. For example under ‘staticTyping’ it is
>> reported that there are 75 test not being passed by any
>> implementation. Under the 'higherOrderFunction’ feature we have 18
>> test passed by no implementation. If you inspect the
>> higherOrderFunction tests more closely we will see that 17 of these
>> tests depend on staticTyping therefore the underlying reason for the
>> higherOrderFunction failures is to do with staticTyping. With what I
>> have said in mind we think it helpful to show the combination of
>> optional features for the test case.
>>
>> I welcome feedback on your preference of presentation on the Optional
>> Features section. I find 2) much more useful:
>>
>> 1) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optFeatures
>> 2) http://dev.w3.org/2011/QT3-test-suite/ReportingResults31/report.html#optComboFeatures
>>
>>
>> Using 1) or 2) we observe that we have 75 tests with dependency on
>> staticTyping not being passed by any implementation (including those
>> with combinations of other dependencies).  I would like to ask if it
>> still merits having tests on static typing?
>>
>> kind regards,
>>
>>
>> -------------------------------
>> O'Neil Delpratt
>> Software Developer, Saxonica Limited
>> Email: on...@sa...
>> Twitter: https://twitter.com/ond1
>> Tel: +44 118 946 5894
>> Web: http://www.saxonica.com
>> Saxonica Community site: http://dev.saxonica.com
>> Bug tracking site: https://saxonica.plan.io/
>>
>> ------------------------------------------------------------------------------
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb

Re: [Exist-development] What are the plans for a release candidate 2?

[Dannes W. <da...@ex...>]

yes, an RC2 has been generated for internal testing, some issues have been found that need a fix….

> On 17 Aug 2016, at 15:41 , Loren Cahlander <lor...@gm...> wrote:
> 
> It has been quite some time since RC1.  Are we due for a RC2?

[Exist-development] What are the plans for a release candidate 2?

[Loren C. <lor...@gm...>]

It has been quite some time since RC1.  Are we due for a RC2?

Loren Cahlander

Re: [Exist-development] collection function performance

[Masoud V. <ma...@gm...>]

no any idea?

On Mon, Jul 25, 2016 at 8:29 AM, Masoud Vakili <ma...@gm...> wrote:

> now, about 320,000 documents and 3,000 sub collections.
>
> On Sun, Jul 24, 2016 at 6:59 PM, Joe Wicentowski <jo...@gm...> wrote:
>
>> Just curious - about how many documents/subcollections are in the
>> collection in question?
>>
>> On Sun, Jul 24, 2016 at 10:16 AM, Masoud Vakili <ma...@gm...>
>> wrote:
>>
>>> default value is 128mb and in the bellow link said
>>>
>>>> Usually this setting does not need to be changed unless you really have
>>>> more than a few thousand collections in the db. Increase it carefully,
>>>> maybe up to 128M.
>>>
>>> http://exist-db.org/exist/apps/doc/configuration.xml
>>>
>>> I changed it to 256mb, but it had no effect. continue increasing?
>>>
>>> On Sun, Jul 24, 2016 at 6:30 PM, Wolfgang Meier <wol...@ex...>
>>> wrote:
>>>
>>>> > this function is high dependence on documents count. when The number
>>>> of documents is large, the collection function not optimized and will be
>>>> slow (200ms).
>>>> > how can I improve its execution?
>>>>
>>>> Please try to increase the collectionCache setting in conf.xml
>>>>
>>>> Wolfgang
>>>
>>>
>>>
>>
>