exist-development — eXist Developer's List

Re: [Exist-development] [Exist-commits] Note: no mail updates

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

All,

changes in SVN can be monitored via the following link (for the time being)

https://sourceforge.net/p/exist/code/commit_browser

wait the page to be initialized, click a line, click the diff-link below. An http-formatted DIFF appears

cheers

Dannes



On 24 Aug 2012, at 22:32 , Dannes Wessels <da...@ex...> wrote:

> maybe we should make our own commits-diff script in the mean while ; probably not too difficult:
> 
> svn diff --old=svn://svn.code.sf.net/p/exist/code/@16971 --new=svn://svn.code.sf.net/p/exist/code/@16972
> 
> a bit more fancy with HTML
> 
> http://wiki.droids-corp.org/index.php/Diff2html

Re: [Exist-development] I am trying to load the DocBook 5 XSLT files into eXist and have entity issues

[Casey J. <cas...@jo...>]

It looks like the system cannot find the referenced DTD's. I think you need
to give eXist some method of looking these up (IE an XML catalog file) I
have never used this method before, but the docs here may help:

*http://exist-db.org/exist/validation.xml#d15897e333*

On Fri, Aug 24, 2012 at 2:45 PM, Loren Cahlander
<lor...@gm...>wrote:

> Hello folks,
>
> Can you take a look at the contents of this tar.bz2 file and tell me what
> changes I need to make to eXist, so that they load?  I do remember that it
> has something to do with entities, but I never got to the point of fixing
> the issues.
>
>
>
> http://sourceforge.net/projects/docbook/files/docbook-xsl/1.77.1/docbook-xsl-1.77.1.tar.bz2/download
>
> I would like to be using these files for the DocBook 5 to XHTML and ePub
> for the eXist documentation project.  If I have this loading, then I can
> use the DocBook 5 format for the eXist documentation project.  I would like
> to use these files, because these XSLT files are being maintained by Bob
> Stayton so we do not have to worry about keeping in sync with any changes
> to the spec.
>
> I can do the work, but would like to know where to make the changes.
>
> Thanks,
> Loren
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>


-- 
--
Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
(585) 348 7399
easydita.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.

[Exist-development] I am trying to load the DocBook 5 XSLT files into eXist and have entity issues

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

Hello folks,

Can you take a look at the contents of this tar.bz2 file and tell me what changes I need to make to eXist, so that they load?  I do remember that it has something to do with entities, but I never got to the point of fixing the issues.


http://sourceforge.net/projects/docbook/files/docbook-xsl/1.77.1/docbook-xsl-1.77.1.tar.bz2/download

I would like to be using these files for the DocBook 5 to XHTML and ePub for the eXist documentation project.  If I have this loading, then I can use the DocBook 5 format for the eXist documentation project.  I would like to use these files, because these XSLT files are being maintained by Bob Stayton so we do not have to worry about keeping in sync with any changes to the spec.

I can do the work, but would like to know where to make the changes.

Thanks,
Loren

[Exist-development] Adding a web proxy to eXist in the Mountain Lion Server

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

Hello folks,

With the upgrade to Mountain Lion, the Apache server is no longer included.  Apache is part of the Server app that is separate.

I was looking for a way to incorporate eXist with the Mac OS X Server configuration base, so that the proxies can be turned on and off from the Server tools.


Adding the following as org.exist-db.plist to /Library/Server/Web/Config/apache2/webapps adds eXist Open Source XML Database to the web app list and performs a proxy to eXist. 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<!-- See man pages for webapp.plist(5) and webappctl(8) for information about this example webapp.plist -->

<plist version="1.0">
    <dict>
        <key>includeFiles</key>
        <array/>
        <key>launchKeys</key>
        <array/>
        <key>name</key>
        <string>org.exist-db</string>
        <key>displayName</key>
        <!-- Name shown in Server app -->
        <string>eXist Open Source XML Database</string>
        <key>proxies</key>
        <!-- ProxyPass/ProxyPassReverse directives are activated when webapp is started -->
        <dict>
            <key>/exist</key>
            <!-- Sets up a reverse proxy -->
            <dict>
                <key>keysAndValues</key>
                <string/>
                <key>path</key>
                <string>/exist</string>
                <key>urls</key>
                <!-- URLs comprise a proxy_balancer group -->
                <array>
                    <string>http://localhost:8080/exist</string>
                </array>
            </dict>
        </dict>
        <key>requiredModuleNames</key>
        <array>
            <!-- Apache plugin modules are enabled when webapp is started -->
            <string>proxy_module</string>
        </array>
        <key>requiredWebAppNames</key>
        <array>
            <!-- Required web apps are started when this webapp is started -->
        </array>
        <key>startCommand</key>
        <string>/Users/cahlander/eXist-trunk/tools/wrapper/bin/exist.sh start</string>
        <key>stopCommand</key>
        <string>/Users/cahlander/eXist-trunk/tools/wrapper/bin/exist.sh stop</string>
        <key>installationIndicatorFilePath</key>
        <!-- The presence of this file indicates web app is installed -->
        <string>/Users/cahlander/eXist-trunk/VERSION.txt</string>
        <key>sslPolicy</key>
        <!-- Determines webapp SSL behavior -->
        <integer>0</integer>
        <!-- 0: default, UseSSLWhenEnabled -->
        <!-- 1:	UseSSLAlways -->
        <!-- 2:	UseSSLOnlyWhenCertificateIsTrustable -->
        <!-- 3:	UseSSLNever -->
        <!-- 4:	UseSSLAndNonSSL -->
    </dict>
</plist>



It starts, but does not stop.  The entry does show in the advanced settings.  It does not stop from the GUI.

The following command-line entries will work, but I did get a corruption after I stopped and restarted.


sudo webappctl start org.exist-db
sudo webappctl stop org.exist-db

https://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/webappctl.8.html#//apple_ref/doc/man/8/webappctl
https://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/webapp.plist.8.html#//apple_ref/doc/man/8/webapp.plist


Can you take a look at my solution and make any suggestions to improve it?  I would love to add this capability with the other Mac enhancement that was created.

[Exist-development] [WARNING] Disabled old subversion repository

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

I have disabled the old Subversion repository to prevent further confusion.

Details and sign-posting are here:
https://exist.svn.sourceforge.net/svnroot/exist/README---WE-HAVE-MOVED.txt

I would however AVOID doing an svn up if you have changes in a working
copy from the old repository as it may delete your changes.


-- 
Adam Retter

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

Re: [Exist-development] bug in 2.0.x

[Christian F. <chr...@wi...>]

In addition: I only noticed the change [1] of SVN address today, so I
tried the new repository, but revision 19681 behaves equally.

Christian

[1] http://markmail.org/message/aphkzsxwurlm2bfi

On 19.08.2012 21:27, Christian Forster wrote:
> Dear all,
> 
> There seems to be a bug in stable/eXist-2.0.x svn revision 16960. I have
> installed eXist-db Demo Apps (0.1) from the repository. The following
> error occurs when I go this page:
> http://localhost:8080/exist/apps/demo/index.html
> 
> <exception>
> 	<path>/db/demo/modules/view.xql</path>
> 	<message>error found while loading module templates: Error while
> loading module templates.xql: Syntax error within user defined function
> templates:apply: unexpected token: ( [at line 33, column 113]</message>
> </exception>
> 
> Builds are done with both SUN JDK 1.6 and 1.7 on a fresh installation of
> Ubuntu 12.04 amd-64.
> On trunk, the error does not occur.
> 
> Best,
> Christian
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
> 

Re: [Exist-development] [Exist-open] [ANN] update of build scripts

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

Hi Dulip,

> I tested for the version of 16960. It still deletes if I do the follwing
> procedure. I tested this twice.

Can you confirm you're using the new SVN repository address (see
announcement at http://markmail.org/message/aphkzsxwurlm2bfi)?  That's
where Dannes's changes to the build scripts were applied, so I just
want to make sure you're getting them.

Joe

Re: [Exist-development] [Exist-open] [ANN] update of build scripts

[Dulip W. <wit...@as...>]

Hi Dannes,

I tested for the version of 16960. It still deletes if I do the follwing
procedure. I tested this twice.

./build.sh clean (for older version, expected to delete)
svn up
restore from the backup
./build.sh clean
./build.sh 

the files are deleted, May be, should I  have to include another step
(once), to get the update correctly?


Best,
Dulip




On Sun, 2012-08-19 at 10:31 +0200, Dannes Wessels wrote:
> All,
> 
> 
> Last few days I have updated the buildscripts of the exist-db
> extensions;  additionally calling "build.sh clean" does NOT remove
> your precious data anymore :-)
> 
> 
> Upon update, you might want to clean the lib/extensions directory to
> prevent double jar entries.
> 
> 
> regards
> 
> 
> Dannes
> 
> 
> 
> --
> Dannes Wessels
> eXist-db Open Source Native XML Database
> e: da...@ex...  w: http://www.exist-db.org t: #existdb
> 
> 
> 
> 
> 
> 
> 
> 

-- 
Dulip Withanage
Senior Software developer M.SC 
Karl Jaspers Center
University of Heidelberg
Germany

[Exist-development] bug in 2.0.x

[Christian F. <chr...@un...>]

Dear all,

There seems to be a bug in stable/eXist-2.0.x svn revision 16960. I have
installed eXist-db Demo Apps (0.1) from the repository. The following
error occurs when I go this page:
http://localhost:8080/exist/apps/demo/index.html

<exception>
	<path>/db/demo/modules/view.xql</path>
	<message>error found while loading module templates: Error while
loading module templates.xql: Syntax error within user defined function
templates:apply: unexpected token: ( [at line 33, column 113]</message>
</exception>

Builds are done with both SUN JDK 1.6 and 1.7 on a fresh installation of
Ubuntu 12.04 amd-64.
On trunk, the error does not occur.

Best,
Christian

[Exist-development] [ANN] update of build scripts

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

All,

Last few days I have updated the buildscripts of the exist-db extensions;  additionally calling "build.sh clean" does NOT remove your precious data anymore :-)

Upon update, you might want to clean the lib/extensions directory to prevent double jar entries.

regards

Dannes


--
Dannes Wessels
eXist-db Open Source Native XML Database
e: da...@ex...  w: http://www.exist-db.org t: #existdb

Re: [Exist-development] [Exist-open] SourceForge Repo Clone Complete

[Florent G. <li...@fg...>]

Dannes Wessels wrote:

  Hi,

> Old URL: http://exist.svn.sourceforge.net/svnroot/exist
> New URL: https://svn.code.sf.net/p/exist/code/  
> We need to figure out how to 'switch' your local copies....

  I've just made a diff of my changes, made a new checkout,
applied the patch, and build again.  Everything went fine!

  By the way, I noticed I had some changes in order to build in
Cygwin, which are probably worth checking in.  The following is
at the end of build.sh, right after the var JAVA_ENDORSED_DIRS:

    if uname -a | grep -i cygwin >/dev/null; then
        EXIST_HOME="`cygpath -m $EXIST_HOME`"
        ANT_HOME="`cygpath -m $ANT_HOME`"
        JAVA_ENDORSED_DIRS="`cygpath -m $JAVA_ENDORSED_DIRS`"
        LOCALCLASSPATH="`cygpath -m -p $LOCALCLASSPATH`"
        echo "Modified paths because running on Cygwin:"
        echo "  EXIST_HOME: $EXIST_HOME"
        echo "  ANT_HOME: $ANT_HOME"
        echo "  JAVA_ENDORSED_DIRS: $JAVA_ENDORSED_DIRS"
        echo "  LOCALCLASSPATH: $LOCALCLASSPATH"
    fi

and in bin/functions.d/eXist-settings.sh, in get_exist_home(),
I've changed:

    (cd $(/usr/bin/dirname "$p") ; /bin/pwd)

to:

    if uname -a | grep -i cygwin >/dev/null; then
        (cd $(/usr/bin/dirname "$p") ; cygpath -m `/bin/pwd`)
    else
        (cd $(/usr/bin/dirname "$p") ; /bin/pwd)
    fi

  Regards,

-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/

Re: [Exist-development] [Exist-open] SourceForge Repo Clone Complete

[Florent G. <li...@fg...>]

  FYI, I get the following error while "svn update"ing (though I don't really care myself):

Fetching external item into 'eXist-maven/eXist-db/existdb-core/src/main/resource
s/quartz.properties':
svn: warning: W200007: Unsupported external: url of file external 'https://exist
.svn.sourceforge.net/svnroot/exist/trunk/eXist/src/org/exist/scheduler/quartz.pr
operties' is not in repository 'https://svn.code.sf.net/p/exist/code'

  Cheers,

 
-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/




>________________________________
> De : Dannes Wessels <da...@ex...>
>À : eXist dev Mailinglist <exi...@li...>; eXist open Mailinglist <Exi...@li...>; exi...@li... 
>Envoyé le : Mercredi 15 août 2012 10h51
>Objet : Re: [Exist-open] SourceForge Repo Clone Complete
> 
>
>Correcting:
>
>Old URL: http://exist.svn.sourceforge.net/svnroot/exist
>New URL: https://svn.code.sf.net/p/exist/code/   
>
>We need to figure out how to 'switch' your local copies....
>
>cheers
>
>Dannes
>
>
>
>On Wed, Aug 15, 2012 at 11:14 AM, Dannes Wessels <di...@ex...> wrote:
>
>All,
>>
>>please note that the SVN addresses have been changed:
>>
>>old:   http://exist.svn.sourceforge.net/svnroot/exist
>>new: https://svn.code.sf.net/p/exist/code/trunk 
>>
>>see other URLs in the new webGui: https://sourceforge.net/p/exist/code/
>>
>>regards
>>
>>Dannes
>>
>>
>>---------- Forwarded message ----------
>>From: SourceForge.net <nor...@in...>
>>Date: Wed, Aug 15, 2012 at 10:54 AM
>>Subject: SourceForge Repo Clone Complete
>>To: no...@in...
>>
>>
>>
>>Your cloned repository code in project exist is now ready for use.
>>Old repository url: http://exist.svn.sourceforge.net/svnroot/exist 
>>New repository checkout command: svn checkout --username=XXXXX svn+ssh://XX...@sv.../p/exist/code/trunk exist-code 
>>You and any other developers should do a fresh checkout using the new repository location.
>>
>>
>>
>>
>
>
>-- 
>eXist-db Native XML Database - http://exist-db.org
>Join us on linked-in: http://www.linkedin.com/groups?gid=35624
>
>------------------------------------------------------------------------------
>Live Security Virtual Conference
>Exclusive live event will cover all the ways today's security and 
>threat landscape has changed and how IT managers can respond. Discussions 
>will include endpoint security, mobile security and the latest in malware 
>threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>_______________________________________________
>Exist-open mailing list
>Exi...@li...
>https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
>

Re: [Exist-development] [Exist-commits] Fwd: SourceForge Repo Clone Complete

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

hi adam,

Ant 1.7.1 is pretty old..... even on MacOsX the default installed version is newer....

but you found it out, good...

D.

On 15 Aug 2012, at 17:11 , Adam Retter <ad...@ex...> wrote:

> It seems it only happens if I run 'ant' directly in eXist-trunk rather
> than running, build.sh. So panic over ;-)
> 
> I guess its because eXist has Ant version 1.8.2 and CentOS/RHEL6 has Ant 1.71...

--
Dannes Wessels
eXist-db Open Source Native XML Database
e: da...@ex...  w: http://www.exist-db.org t: #existdb

Re: [Exist-development] [Exist-commits] Fwd: SourceForge Repo Clone Complete

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

It seems it only happens if I run 'ant' directly in eXist-trunk rather
than running, build.sh. So panic over ;-)

I guess its because eXist has Ant version 1.8.2 and CentOS/RHEL6 has Ant 1.71...

On 15 August 2012 16:07, Adam Retter <ad...@ex...> wrote:
> Looks like this probably also exists with the old code base.
>
> Does anyone know why this happens with ant ?
>
> On CentOS ant version 1.7.1-13.el6 is installed as part of the base
> system, could this be conflicting, how do we avoid this?
>
> The problem will also appear on Redhat Enterprise Linux 6.
>
>
> On 15 August 2012 15:58, Adam Retter <ad...@ex...> wrote:
>> I cant do a clean build of eXist from the new svn repo. On a new
>> CentOS 6 machine if I try a fresh checkout and build I get the error -
>>
>> /home/dev/eXist-trunk/build/scripts/build-impl.xml:729: The following
>> error occurred while executing this line:
>> /home/dev/eXist-trunk/extensions/modules/build.xml:225:
>> java.lang.NoSuchMethodError:
>> org.apache.tools.ant.taskdefs.Get.setRetries(I)V
>>
>> Any ideas?
>>
>>
>>
>> On 15 August 2012 10:14, Dannes Wessels <di...@ex...> wrote:
>>> All,
>>>
>>> please note that the SVN addresses have been changed:
>>>
>>> old:   http://exist.svn.sourceforge.net/svnroot/exist
>>> new: https://svn.code.sf.net/p/exist/code/trunk
>>>
>>> see other URLs in the new webGui: https://sourceforge.net/p/exist/code/
>>>
>>> regards
>>>
>>> Dannes
>>>
>>> ---------- Forwarded message ----------
>>> From: SourceForge.net <nor...@in...>
>>> Date: Wed, Aug 15, 2012 at 10:54 AM
>>> Subject: SourceForge Repo Clone Complete
>>> To: no...@in...
>>>
>>>
>>> Your cloned repository code in project exist is now ready for use.
>>>
>>> Old repository url: http://exist.svn.sourceforge.net/svnroot/exist
>>>
>>> New repository checkout command: svn checkout --username=XXXXX
>>> svn+ssh://XX...@sv.../p/exist/code/trunk exist-code
>>>
>>> You and any other developers should do a fresh checkout using the new
>>> repository location.
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Exist-commits mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-commits
>>>
>>
>>
>>
>> --
>> 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



-- 
Adam Retter

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

Re: [Exist-development] [Exist-commits] Fwd: SourceForge Repo Clone Complete

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

Looks like this probably also exists with the old code base.

Does anyone know why this happens with ant ?

On CentOS ant version 1.7.1-13.el6 is installed as part of the base
system, could this be conflicting, how do we avoid this?

The problem will also appear on Redhat Enterprise Linux 6.


On 15 August 2012 15:58, Adam Retter <ad...@ex...> wrote:
> I cant do a clean build of eXist from the new svn repo. On a new
> CentOS 6 machine if I try a fresh checkout and build I get the error -
>
> /home/dev/eXist-trunk/build/scripts/build-impl.xml:729: The following
> error occurred while executing this line:
> /home/dev/eXist-trunk/extensions/modules/build.xml:225:
> java.lang.NoSuchMethodError:
> org.apache.tools.ant.taskdefs.Get.setRetries(I)V
>
> Any ideas?
>
>
>
> On 15 August 2012 10:14, Dannes Wessels <di...@ex...> wrote:
>> All,
>>
>> please note that the SVN addresses have been changed:
>>
>> old:   http://exist.svn.sourceforge.net/svnroot/exist
>> new: https://svn.code.sf.net/p/exist/code/trunk
>>
>> see other URLs in the new webGui: https://sourceforge.net/p/exist/code/
>>
>> regards
>>
>> Dannes
>>
>> ---------- Forwarded message ----------
>> From: SourceForge.net <nor...@in...>
>> Date: Wed, Aug 15, 2012 at 10:54 AM
>> Subject: SourceForge Repo Clone Complete
>> To: no...@in...
>>
>>
>> Your cloned repository code in project exist is now ready for use.
>>
>> Old repository url: http://exist.svn.sourceforge.net/svnroot/exist
>>
>> New repository checkout command: svn checkout --username=XXXXX
>> svn+ssh://XX...@sv.../p/exist/code/trunk exist-code
>>
>> You and any other developers should do a fresh checkout using the new
>> repository location.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Exist-commits mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-commits
>>
>
>
>
> --
> 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] [Exist-commits] Fwd: SourceForge Repo Clone Complete

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

I cant do a clean build of eXist from the new svn repo. On a new
CentOS 6 machine if I try a fresh checkout and build I get the error -

/home/dev/eXist-trunk/build/scripts/build-impl.xml:729: The following
error occurred while executing this line:
/home/dev/eXist-trunk/extensions/modules/build.xml:225:
java.lang.NoSuchMethodError:
org.apache.tools.ant.taskdefs.Get.setRetries(I)V

Any ideas?



On 15 August 2012 10:14, Dannes Wessels <di...@ex...> wrote:
> All,
>
> please note that the SVN addresses have been changed:
>
> old:   http://exist.svn.sourceforge.net/svnroot/exist
> new: https://svn.code.sf.net/p/exist/code/trunk
>
> see other URLs in the new webGui: https://sourceforge.net/p/exist/code/
>
> regards
>
> Dannes
>
> ---------- Forwarded message ----------
> From: SourceForge.net <nor...@in...>
> Date: Wed, Aug 15, 2012 at 10:54 AM
> Subject: SourceForge Repo Clone Complete
> To: no...@in...
>
>
> Your cloned repository code in project exist is now ready for use.
>
> Old repository url: http://exist.svn.sourceforge.net/svnroot/exist
>
> New repository checkout command: svn checkout --username=XXXXX
> svn+ssh://XX...@sv.../p/exist/code/trunk exist-code
>
> You and any other developers should do a fresh checkout using the new
> repository location.
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Exist-commits mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-commits
>



-- 
Adam Retter

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

Re: [Exist-development] SourceForge Repo Clone Complete

[Hungerburg <pc...@my...>]

Am 2012-08-15 12:12, schrieb Dannes Wessels:
> You command is a fresh checkout, right? The URL should work for ReadOnly
> access to the new repository (but some of Adam's recent fixes are not
> migrated yet)

Dannes, the fresh checkout worked alright. I prefer stable over trunk 
and I guess that 2.0.x is where maintenance gets performed. The build 
with openJDK6 worked out OK too. eXist is now running, everything fine 
so far, below my commands from the terminal:

$ svn checkout svn://svn.code.sf.net/p/exist/code/stable/eXist-2.0.x
$ echo "include.module.xslfo = true" > extensions/local.build.properties
$ export JAVA_HOME=/usr/lib/jvm/default-java
$ export EXIST_HOME=/opt/eXist-2.0.x
$ unset DISPLAY # must not point at remote host by ssh
$ ./build.sh svn-download # to make the build system
$ ./build.sh svn-prepare  # tag releases with the revision
$ ./build.sh
$ ./build.sh -f build/scripts/jarsigner.xml
$ bin/startup.sh

Pointing the browser at http://...:8080/exist/admin/admin.xql I notice, 
that I cannot set the password of admin from the WEB panel, because that 
requires a group to be set, and there are no groups to select from 
there! (Like stated there though, the RPC client works.)

Creating a new user, I notice, that I cannot create new groups, not from 
the RPC client, but can do from the WEB admin panel ;)

> About OpenJDK6 ... the old statement still applies: It might work (it
> will certainly), but we don;t test against it ourself, hence support is
> limited from our side. JDK7/OpenJDK7 wil make it different.....

Does that say, that I should rather use OpenJDK 7 instead of 6? I would 
like to share my experiences, and if I understand you correctly, using 
openJDK6 will make them worthless… So should I better start from scratch 
with 7?

-- 
peter

Re: [Exist-development] SourceForge Repo Clone Complete

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

Hi Peter

On Wed, Aug 15, 2012 at 12:06 PM, Hungerburg <pc...@my...> wrote:

>  I just did, on a new machine,
>
> $ svn checkout svn://svn.code.sf.net/p/exist/code/stable/eXist-2.0.x
>
> now trying to compile with openJDK ubuntu 6b24, should that work?
>

You command is a fresh checkout, right? The URL should work for ReadOnly
access to the new repository (but some of Adam's recent fixes are not
migrated yet)

About OpenJDK6 ... the old statement still applies: It might work (it will
certainly), but we don;t test against it ourself, hence support is limited
from our side. JDK7/OpenJDK7 wil make it different.....

cheers

Dannes


-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

Re: [Exist-development] SourceForge Repo Clone Complete

[Hungerburg <pc...@my...>]

Am 2012-08-15 11:51, schrieb Dannes Wessels:
> Correcting:
>
> Old URL: http://exist.svn.sourceforge.net/svnroot/exist
> New URL: https://svn.code.sf.net/p/exist/code/
>
> We need to figure out how to 'switch' your local copies....

I just did, on a new machine,

$ svn checkout svn://svn.code.sf.net/p/exist/code/stable/eXist-2.0.x

now trying to compile with openJDK ubuntu 6b24, should that work?

-- 
peter

Re: [Exist-development] SourceForge Repo Clone Complete

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

Correcting:

Old URL: http://exist.svn.sourceforge.net/svnroot/exist
New URL: https://svn.code.sf.net/p/exist/code/

We need to figure out how to 'switch' your local copies....

cheers

Dannes


On Wed, Aug 15, 2012 at 11:14 AM, Dannes Wessels <di...@ex...>wrote:

> All,
>
> please note that the SVN addresses have been changed:
>
> old:   http://exist.svn.sourceforge.net/svnroot/exist
> new: https://svn.code.sf.net/p/exist/code/trunk
>
> see other URLs in the new webGui: https://sourceforge.net/p/exist/code/
>
> regards
>
> Dannes
>
> ---------- Forwarded message ----------
> From: SourceForge.net <nor...@in...>
> Date: Wed, Aug 15, 2012 at 10:54 AM
> Subject: SourceForge Repo Clone Complete
> To: no...@in...
>
>
> Your cloned repository code in project exist is now ready for use.
>
> Old repository url: http://exist.svn.sourceforge.net/svnroot/exist
>
> New repository checkout command: svn checkout --username=XXXXX svn+ssh://
> XX...@sv.../p/exist/code/trunk exist-code
>
> You and any other developers should do a fresh checkout using the new
> repository location.
>
>
>
>


-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

[Exist-development] Fwd: SourceForge Repo Clone Complete

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

All,

please note that the SVN addresses have been changed:

old:   http://exist.svn.sourceforge.net/svnroot/exist
new: https://svn.code.sf.net/p/exist/code/trunk

see other URLs in the new webGui: https://sourceforge.net/p/exist/code/

regards

Dannes

---------- Forwarded message ----------
From: SourceForge.net <nor...@in...>
Date: Wed, Aug 15, 2012 at 10:54 AM
Subject: SourceForge Repo Clone Complete
To: no...@in...


Your cloned repository code in project exist is now ready for use.

Old repository url: http://exist.svn.sourceforge.net/svnroot/exist

New repository checkout command: svn checkout --username=XXXXX svn+ssh://
XX...@sv.../p/exist/code/trunk exist-code

You and any other developers should do a fresh checkout using the new
repository location.

[Exist-development] Fwd: SourceForge Project Upgrade Notification

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

All,

currently the sfnet servers are being upgraded. You might want to hold commits for a moment.....

D.



Begin forwarded message:

> From: SourceForge.net <nor...@in...>
> Subject: SourceForge Project Upgrade Notification
> Date: 14 August 2012 22:37:10 GMT+02:00
> To: no...@in...
> Reply-To: no...@in...
> 
> Your project, eXist-db, has been upgraded.
> 
> Your source code repositories are currently being migrated to the new setup. You will recieve another email when that import is complete. That means that you and any other developers should do a fresh checkout using the new repository location when it is ready (see the "code" tab). Please be aware that large repositories may take a long time.
> 
> Please report any issues to us as at https://sourceforge.net/p/forge/site-support/new/  Thanks!

[Exist-development] Problem with Elements and ElementImpl

[Alister P. <gsp...@gm...>]

Hi,

I'd really appreciate some help in understanding the difference between in-memory elements (directly constructed elements in an xquery) and elements stored in the database and represented by NodeProxy. 

The problem (again) is in the AbstractCompressFunction which behaves differently depending on whether the "<entry>" is directly constructed, or stored in the database.

In the compressElement method, this statement:
System.out.println("*** COUNT: " + element.getChildNodes().getLength() + ", E: " + element + " --- " + element.getChildNodes());
produces 
*** COUNT: 1, E: in-memory#element {entry} {in-memory#attribute {name} {test-doc.xml}  in-memory#attribute {type} {uri} in-memory#text {/test/test-doc.xml} }  --- [in-memory#text {/test/test-doc.xml} ]
for a directly constructed element,

and this:
*** COUNT: 3, E: <entry name="test-doc.xml" type="uri">/test/test-doc.xml</entry> --- [ name="test-doc.xml",  type="uri", /test/test-doc.xml]
for an <entry> stored in the database.


In the compressElement method, the second case throws an error because the child count is >1. 

Am I using NodeProxy incorrectly? Should I cast to something other than Element?

The first case is the result of this patch:
Index: extensions/modules/src/org/exist/xquery/modules/compression/AbstractCompressFunction.java
===================================================================
--- extensions/modules/src/org/exist/xquery/modules/compression/AbstractCompressFunction.java	(revision 16905)
+++ extensions/modules/src/org/exist/xquery/modules/compression/AbstractCompressFunction.java	(working copy)
@@ -37,6 +37,7 @@
 import org.exist.dom.DefaultDocumentSet;
 import org.exist.dom.DocumentImpl;
 import org.exist.dom.MutableDocumentSet;
+import org.exist.dom.NodeProxy;
 import org.exist.security.PermissionDeniedException;
 import org.exist.storage.lock.Lock;
 import org.exist.storage.serializers.Serializer;
@@ -123,6 +124,12 @@
                             Element element = (Element) item;
                             compressElement(os, element, useHierarchy, stripOffset);
                         }
+			else if (item instanceof NodeProxy)
+			{
+			    NodeProxy nodeproxy = (NodeProxy) item;
+			    Element element = (Element) nodeproxy.getNode();                         
+			    compressElement(os, element, useHierarchy, stripOffset);
+		        }
                         else
                         {
                             compressFromUri(os, ((AnyURIValue)item).toXmldbURI(), useHierarchy, stripOffset, "", null);
@@ -206,6 +213,7 @@
             if(!(element.getNodeName().equals("entry") || element.getNamespaceURI().length() > 0))
                 throw new XPathException(this, "Item must be type of xs:anyURI or element enry.");
 
+	    System.out.println("*** CHILDNODES COUNT: " + element.getChildNodes().getLength() + ", E: " + element + " --- " + element.getChildNodes());
             if(element.getChildNodes().getLength() > 1)
                 throw new XPathException(this, "Entry content is not valid XML fragment.");
 

[Exist-development] xml comment parsing

[Hungerburg <pc...@my...>]

I noticed from the log, when opening/saving an xsd file with a comment

<!-- see asdf.cgi&page=123 -->

a warning:

[eXistThread-28] WARN  (CommentImpl.java [serialize]:53) - 
org.exist.xquery.XPathException: XPST0003 : Invalid character (=) in 
entity name (page) or missing ;

If I understand http://www.w3.org/TR/REC-xml/#sec-comments fully, this 
comment should not produce such a warning. Although I am not positively 
sure what exactly "Parameter entity references" are.

The warning does not do any harm, as far as I can tell. But maybe 
something lies lurking there, so I tell you.

Thank You

Peter

Re: [Exist-development] Errors from Stress tests on xquery update

[Casey J. <cas...@jo...>]

I will add the test to the eXstress github, this is the only way I know how
to reproduce this. Although it may be possible to use timers to achive the
same result. IE: Running two threads in parallel that both select out nodes
to be operated on. Then one thread waits 500ms and removes the nodes, and
the other waits 1500ms to perform it's operation.

I would assume this could create the same situation.

On Wed, Jul 18, 2012 at 2:47 PM, Wolfgang Meier <wol...@ex...>wrote:

> > Thanks. I will test this workaround. So would you consider this to be a
> bug
> > that will be eventually fixed in eXist, or will developers always need
> to be
> > aware of this when using the update methods?
>
> There seems to be a bug. eXist does allow dirty reads, which means it
> is possible for node references to become invalid during a query.
> Nevertheless a started transaction must not abort.
>
> I have received another test from someone else which fails for similar
> reasons. We have to figure out what causes this. It's not easy though.
> If you have a reproducible test, I'll be happy to compare it to the
> other scenario I have.
>
> Wolfgang
>



-- 
--
Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
(585) 348 7399
easydita.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.