Dear eXistentialists,
Unicode 5.1 becomes official on April 4 (it has been in a frozen beta for a while) and it incorporates a number of new characters that I use extensively (early Cyrillic). Currently an "order by" operation in eXist does not sort these correctly, which is fair enough, I suppose, since it is not yet April 4, but I am writing to enquire whether anyone knows what happens next. Does eXist rely on java to do the sorting, so that it won't operate correctly until java is updated? Or does eXist handle it separately? If eXist depends on java (that is, on Sun), does anyone have any experience concerning how long it takes Sun to catch up to this sort of upgrade? I can implement my own sorting as a work-around, if necessary, but if I can anticipate a fairly quick update from either Sun or the eXist team (depending on who is handling the sorting), I'll save myself the effort and try to be patient.
Thank you for any advice.
Sincerely,
David
djbpitt+xml@...

Once I've got a error "Impossible to store a resource
/home/hoge/hoge.xml: networking error" when I attempt to
store large(6M) file to database by Admin Client
connected type=Remote
(URL xmldb:exist://localhost:8080/exist/xmlrpc),
the database became impossible to shutdown.
---Error messages at shutdown---
$ bin/shutdown.sh
WARN: The following JAR file entries from 'org/exist/start/start.config' aren't available (this may NOT be a problem):
/usr/local/exist/test/classes
Shutting down database instance at
xmldb:exist://localhost:8080/exist/xmlrpc/db
ERROR: shutdown failed
org.xmldb.api.base.XMLDBException: shutdown failed
at org.exist.xmldb.RemoteDatabaseInstanceManager.shutdown(RemoteDatabaseInstanceManager.java:40)
at org.exist.xmldb.RemoteDatabaseInstanceManager.shutdown(RemoteDatabaseInstanceManager.java:27)
at org.exist.ServerShutdown.main(ServerShutdown.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.exist.start.Main.invokeMain(Main.java:128)
at org.exist.start.Main.run(Main.java:405)
at org.exist.start.Main.main(Main.java:59)
Caused by: org.apache.xmlrpc.XmlRpcException: org.apache.xmlrpc.XmlRpcException: Invalid password for user admin
at org.apache.xmlrpc.XmlRpcClient$Worker.execute(XmlRpcClient.java:457)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:163)
at org.exist.xmldb.RemoteDatabaseInstanceManager.shutdown(RemoteDatabaseInstanceManager.java:38)
... 9 more
[B@...: org.apache.xmlrpc.XmlRpcException: Invalid password for user admin
at org.apache.xmlrpc.XmlRpcClient$Worker.execute(XmlRpcClient.java:457)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:163)
at org.exist.xmldb.RemoteDatabaseInstanceManager.shutdown(RemoteDatabaseInstanceManager.java:38)
at org.exist.xmldb.RemoteDatabaseInstanceManager.shutdown(RemoteDatabaseInstanceManager.java:27)
at org.exist.ServerShutdown.main(ServerShutdown.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.exist.start.Main.invokeMain(Main.java:128)
at org.exist.start.Main.run(Main.java:405)
at org.exist.start.Main.main(Main.java:59)
Caused by: org.apache.xmlrpc.XmlRpcException: org.apache.xmlrpc.XmlRpcException: Invalid password for user admin
at org.apache.xmlrpc.XmlRpcClient$Worker.execute(XmlRpcClient.java:457)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:163)
at org.exist.xmldb.RemoteDatabaseInstanceManager.shutdown(RemoteDatabaseInstanceManager.java:38)
at org.exist.xmldb.RemoteDatabaseInstanceManager.shutdown(RemoteDatabaseInstanceManager.java:27)
at org.exist.ServerShutdown.main(ServerShutdown.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.exist.start.Main.invokeMain(Main.java:128)
at org.exist.start.Main.run(Main.java:405)
at org.exist.start.Main.main(Main.java:59)
----------------------
Is it bug?
OS：Debian Etch
eXist ver.: 1.2.0
State: In the state of being installed
moriyasu

Hello eXist list,
I would like to enable XSLT 2 support in my installation of eXist (a
standalone installation). The instructions at http://atomic.exist-db.org/HowTo/XSLT2/
indicate that eXist has been tested with Saxon 8.7.3. I see that
Saxon is currently at release 9.0.4, and the release notes indicate
several improvements including security updates. The initial test I
did using xsl:analyze-string worked perfectly in eXist after
installing 9.0.4.
Would anyone recommend against using 9.0.4?
Many thanks,
Joe

Google has extended the deadline for student applications until
Monday, April 7, 2008
We hope this will convince a few more people to apply. So far we
received 6 proposals. I think that a detailed application which
concentrates on concrete development steps will still have a realistic
chance to be accepted.
Wolfgang

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

CountryState

JavaScript is required for this form.

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details