exist-development — eXist Developer's List

[Exist-development] optimisation with org.exist.storage.btree.Value

[James F. <jam...@ex...>]

after testing locally I have now committed simple optimisation to
org.exist.storage.btree.Value

all occurrences of the following

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

if (b1 == b2){
 continue;
else {

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

with

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

if (b1 != b2){

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

I would have expected this kind of thing to be optimized by javac but
this doesn't seem to be the case.

benchmark testing with adhoc queries results in varying % of
performance speedup depending upon query

I believe there are more optimisation opportunities here but moving
slowly and gently.

James Fuller

Re: [Exist-development] Metadata in eXist

[Patrick B. <pat...@jo...>]

I'm not sure where it will be stored. This is actually something I was
hoping one of the core developers could advise me on (Wolf?)

Cheers,

Patrick

On Fri, Jul 30, 2010 at 11:53 PM, Dmitriy Shabanov <sha...@gm...>wrote:

> On Fri, Jul 30, 2010 at 9:49 PM, Dan McCreary <dan...@gm...>wrote:
>
>> I am not sure I understand so here is an example use case for photography
>> images.
>>
>> We could create a trigger under /db/images so that all images that are
>> added to specific collections that have an image type (.jpg, .png. gif etc.)
>> such as:
>>
>> /db/images/foo.jpg
>>
>> would have an XML fragment automatically created that might contain
>> information about the image like this<http://www.exif.org/samples/canon-ixus.html>but in XML format?
>>
>> Can we control where and/or how we store the metadata?  If we want the
>> metadata to be backed up it might be in the same collection:
>>
>> /db/images/foo.jpg.meta
>>
>
> As I understand: metadata("/db/images/foo.jpg")/keyOne
>
> My question: is it going to be stored under
> /system/metadata/db/images/foo.jpg.xml ?
>
> --
> Dmitriy Shabanov
>



-- 
Patrick Bosek
Jorsek Software
Cell (585) 820 9634
Office (585) 239 6060
Jorsek.com

[Exist-development] simple optimisation with org.exist.storage.btree.Value

[James F. <jam...@ex...>]

In org.exist.storage.btree.Value all occurrences of the following

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

if (b1 == b2){
  continue;
else {

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

with

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

if (b1 != b2){

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

e.g. I got rid of continue statement and changed operator == to !=

I have been using a simple but intensive query that walks the shakespeare data

declare function local:treewalker ($html) {
let $children := $html/* return
if(empty($children)) then () else for $c in $children return
( element {name($c)}{ $c/@*,
$c/text(),
local:treewalker($c)
})

};

<test>{local:treewalker(//PLAY)}</test>

which resulted in

------
local:treewalker	100 runs ~ 340s

w/ optimization
------
local:treewalker	100 ~234s

I have also done a number of other kinds of queries which confirms
between a 15 - 30% increase in query performance in certain scenarios
which makes me a bit dubious ... all the caveats apply when doing this
kind of adhoc benchmarking but was wondering if someone else wants to
check these things on their own trunk checkout.

James Fuller

Re: [Exist-development] adhoc perf benchmark

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

I have tried running the performance benchmark and it always fails.  I think that the dataset changed from when it was last thoroughly run.

On Aug 2, 2010, at 07:48 AM, Wolfgang Meier wrote:

>> I think there is an Performance benchmark test suite that accompanies eXist-db?
>> 
>> Looking at build/scripts/performance.xml it looks like the ant target
>> could be "benchmark", but thats all I know about this really...
> 
> Correct. It stores some TEI and a pretty large document (700mb). You
> thus need to have enough memory (2G) and a sufficiently large caching
> space (256m) or it will take forever. Also, running all tests at once
> takes quite long (every test is repeated 5 times). I usually comment
> out some parts of performance.xml for this.
> 
> Wolfgang
> 
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] adhoc perf benchmark

[Wolfgang M. <wol...@ex...>]

> e.g.
>
> http://demo.exist-db.org/jgoethe-tei.zip
>
> not there to download from this url

Correct. I have a local copy of those files, so I did not recognize
the URL is failing now. I'll try to move the stuff elsewhere.

Wolfgang

Re: [Exist-development] adhoc perf benchmark

[James F. <jam...@ex...>]

On 2 August 2010 14:48, Wolfgang Meier <wol...@ex...> wrote:
>> I think there is an Performance benchmark test suite that accompanies eXist-db?
>>
>> Looking at build/scripts/performance.xml it looks like the ant target
>> could be "benchmark", but thats all I know about this really...
>
> Correct. It stores some TEI and a pretty large document (700mb). You
> thus need to have enough memory (2G) and a sufficiently large caching
> space (256m) or it will take forever. Also, running all tests at once
> takes quite long (every test is repeated 5 times). I usually comment
> out some parts of performance.xml for this.

ok, I did try using these some time ago but noted that source data was
not available

e.g.

http://demo.exist-db.org/jgoethe-tei.zip

not there to download from this url

J
>
> Wolfgang
>

Re: [Exist-development] adhoc perf benchmark

[Wolfgang M. <wol...@ex...>]

> I think there is an Performance benchmark test suite that accompanies eXist-db?
>
> Looking at build/scripts/performance.xml it looks like the ant target
> could be "benchmark", but thats all I know about this really...

Correct. It stores some TEI and a pretty large document (700mb). You
thus need to have enough memory (2G) and a sufficiently large caching
space (256m) or it will take forever. Also, running all tests at once
takes quite long (every test is repeated 5 times). I usually comment
out some parts of performance.xml for this.

Wolfgang

Re: [Exist-development] adhoc perf benchmark

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

I think there is an Performance benchmark test suite that accompanies eXist-db?

Looking at build/scripts/performance.xml it looks like the ant target
could be "benchmark", but thats all I know about this really...

On 2 August 2010 10:54, James Fuller <jam...@ex...> wrote:
> Gentlemen,
>
> >From time to time (like now), I have a need to understand what changes
> I do that affect eXist performance.
>
> I know all the vagaries of benchmarking, but seeking a simple query
> and dataset that I can run to give me an relative indicator rather
> then heavy degree of precision. Something that I can run relatively
> fast whilst doing iterative development.
>
> I have my own, but was wondering if (Wolf ?) anyone else has ideas or
> example general queries that you use that could represent an adhoc
> benchmark, that can be run under 5m or even less ?
>
> James Fuller
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> 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

[Exist-development] adhoc perf benchmark

[James F. <jam...@ex...>]

Gentlemen,

>From time to time (like now), I have a need to understand what changes
I do that affect eXist performance.

I know all the vagaries of benchmarking, but seeking a simple query
and dataset that I can run to give me an relative indicator rather
then heavy degree of precision. Something that I can run relatively
fast whilst doing iterative development.

I have my own, but was wondering if (Wolf ?) anyone else has ideas or
example general queries that you use that could represent an adhoc
benchmark, that can be run under 5m or even less ?

James Fuller

Re: [Exist-development] [Exist-open] IMPORTANT package management repository committed to trunk

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

James Fuller wrote:

  Hi,

> I have committed the package management repository which lets
> eXist now uses expath repository to resolve external
> dependencies located in repository to be used by xquery and
> other XML technologies. You can add and remove .xar packages
> from eXist.

  Thank you for this integration!  I am in Montreal right now for
Balisage, so I don't have much time/facility to test it in the
following days, but I'll try to post the first comments I have.
For what I've seen so far, it looks great!

  Regards,

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



      

[Exist-development] teamcity build

[James F. <jam...@ex...>]

apologies for the teamcity failed build mail spam, I needed to
understand what teamcity build was doing to replicate locally.

I will now be testing locally and will commit fix once I am 100%
certain all is well ... shouldn't take long.

ta, J

Re: [Exist-development] Metadata in eXist

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

On Fri, Jul 30, 2010 at 9:49 PM, Dan McCreary <dan...@gm...>wrote:

> I am not sure I understand so here is an example use case for photography
> images.
>
> We could create a trigger under /db/images so that all images that are
> added to specific collections that have an image type (.jpg, .png. gif etc.)
> such as:
>
> /db/images/foo.jpg
>
> would have an XML fragment automatically created that might contain
> information about the image like this<http://www.exif.org/samples/canon-ixus.html>but in XML format?
>
> Can we control where and/or how we store the metadata?  If we want the
> metadata to be backed up it might be in the same collection:
>
> /db/images/foo.jpg.meta
>

As I understand: metadata("/db/images/foo.jpg")/keyOne

My question: is it going to be stored under
/system/metadata/db/images/foo.jpg.xml ?

-- 
Dmitriy Shabanov

Re: [Exist-development] Metadata in eXist

[Dan M. <dan...@gm...>]

I am not sure I understand so here is an example use case for photography
images.

We could create a trigger under /db/images so that all images that are added
to specific collections that have an image type (.jpg, .png. gif etc.) such
as:

/db/images/foo.jpg

would have an XML fragment automatically created that might contain
information about the image like
this<http://www.exif.org/samples/canon-ixus.html>but in XML format?

Can we control where and/or how we store the metadata?  If we want the
metadata to be backed up it might be in the same collection:

/db/images/foo.jpg.meta

or

/db/images/foo.jpg.meta.xml

or optionally, perhaps it should it be put in a system folder:

/db/system/meta/db/images/foo.jpg.meta

or

/db/meta/db/images/foo.jpg.meta

Does this make sense?

- Dan

On Fri, Jul 30, 2010 at 12:00 PM, Patrick Bosek <pat...@jo...>wrote:

> So, it seems like we're fairly agreed that a new axis is not the way to go.
> I would tend to agree that is the right decision. So the only question left
> is whether to use key/value or xml fragments. I like Wolfgang's method of
> accessing metadata, it seems very consistent and intuitive. Unless I'm
> missing something, I'm still having a hard time seeing value in choosing
> key/value over xml fragment. Since under Wolfgang's suggestion anyone who
> wanted a key/value type metadata set could simply access them as
>
> metadata("/db/doc.xml")/keyOne
> metadata("/db/doc.xml")/keyTwo
>
>
> This may not allow us to store binary data natively in metadata fields. But
> I would contend that in 99% of cases metadata is being used to aid in
> searching for or classifying another resource in the database.
>
>
> As a side note. I'm planning to begin working on implementing this around
> the 2nd week in August.
>
> Cheers,
>
> Patrick
>
>
> On Fri, Jul 30, 2010 at 6:41 AM, Adam Retter <ad...@ex...> wrote:
>
>> > we need to keep in mind that when data is backed up / archived /
>> > extracted outside the system that metadata moves with it.
>>
>> Completely agree with you. But as was mentioned earlier in terms of
>> thinking of ntfs streams, when the backup is done as well as for
>> example doc1.xml being in the backup you could also have doc1.xmd
>> (containing the metadata)
>>
>> > J
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
>>
>>
>> ------------------------------------------------------------------------------
>> The Palm PDK Hot Apps Program offers developers who use the
>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
>> of $1 Million in cash or HP Products. Visit us here for more details:
>> http://p.sf.net/sfu/dev2dev-palm
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>
>
>
> --
> Patrick Bosek
> Jorsek Software
> Cell (585) 820 9634
> Office (585) 239 6060
> Jorsek.com
>
>
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>


-- 
Dan McCreary
Semantic Solutions Architect
office: (952) 931-9198
cell: (612) 986-1552

Re: [Exist-development] Metadata in eXist

[Patrick B. <pat...@jo...>]

So, it seems like we're fairly agreed that a new axis is not the way to go.
I would tend to agree that is the right decision. So the only question left
is whether to use key/value or xml fragments. I like Wolfgang's method of
accessing metadata, it seems very consistent and intuitive. Unless I'm
missing something, I'm still having a hard time seeing value in choosing
key/value over xml fragment. Since under Wolfgang's suggestion anyone who
wanted a key/value type metadata set could simply access them as

metadata("/db/doc.xml")/keyOne
metadata("/db/doc.xml")/keyTwo


This may not allow us to store binary data natively in metadata fields. But
I would contend that in 99% of cases metadata is being used to aid in
searching for or classifying another resource in the database.


As a side note. I'm planning to begin working on implementing this around
the 2nd week in August.

Cheers,

Patrick

On Fri, Jul 30, 2010 at 6:41 AM, Adam Retter <ad...@ex...> wrote:

> > we need to keep in mind that when data is backed up / archived /
> > extracted outside the system that metadata moves with it.
>
> Completely agree with you. But as was mentioned earlier in terms of
> thinking of ntfs streams, when the backup is done as well as for
> example doc1.xml being in the backup you could also have doc1.xmd
> (containing the metadata)
>
> > J
> >
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Patrick Bosek
Jorsek Software
Cell (585) 820 9634
Office (585) 239 6060
Jorsek.com

Re: [Exist-development] Commit comments????

[Andrzej J. T. <an...@ch...>]

Jens:

Your 5 commits today had no log messages/comments.

I know these were just data or documentation changes, but it would still be appreciated if you always included a short
log message on all commits.  If it's trivial, just prefix the message with the customary "[ignore]" string and note
quickly what was changed.

Thanks!

......Andrzej

> Revision: 12130
>           http://exist.svn.sourceforge.net/exist/?rev=12130&view=rev
> Author:   jenspetersen
> Date:     2010-07-30 14:40:50 +0000 (Fri, 30 Jul 2010)
> 
> Log Message:
> -----------
> 
> 
> Modified Paths:
> --------------
>     trunk/eXist/webapp/biblio/mods/apps/mods/edit/body/01-title.xml
> 
> Modified: trunk/eXist/webapp/biblio/mods/apps/mods/edit/body/01-title.xml

<snip>


-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Exist-development] betterform integration

[Joern T. <joe...@go...>]

Alain,

On Thu, Jul 29, 2010 at 2:13 PM, COUTHURES Alain
<ala...@ag...> wrote:
> Hello James and Joern,
>
> James Fuller a écrit :
>
> On 29 July 2010 13:54, Joern Turner <joe...@go...> wrote:
>
>
> Ok, but did you notice that the links for XSLTForms do not work?
>
>
> though I did the initial integration of xsltforms, I do not maintain
> this area ... refactor as you see fit
>
>
> I can maintain myself XSLTForms within eXist if you're OK about that (I need
> an account for that, I presume ;-) ).
Of course it makes most sense if you do that by yourself.

Hope you don't mind if i step ahead and build a general overview page
on XForms in eXist with links to your docs and the betterFORM docs as
separate pages. This way it's easier for each of us to extend the
information on these pages.

Joern

>
> I saw recently that it didn't work, apparently because of missing config
> files.
>
> I'm now busy with SVG support (I'm preparing my paper for SVG Open 2010 in
> Paris at the end of August!) about graph2svg integration... but I'm also
> preparing the Beta 3 release with native XML documents.
>
> Thanks!
>
>  -Alain
>

Re: [Exist-development] Metadata in eXist

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

> we need to keep in mind that when data is backed up / archived /
> extracted outside the system that metadata moves with it.

Completely agree with you. But as was mentioned earlier in terms of
thinking of ntfs streams, when the backup is done as well as for
example doc1.xml being in the backup you could also have doc1.xmd
(containing the metadata)

> J
>



-- 
Adam Retter

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

Re: [Exist-development] Metadata in eXist

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

On Fri, Jul 30, 2010 at 3:03 PM, James Fuller <jam...@ex...>wrote:

> On 30 July 2010 11:37, Adam Retter <ad...@ex...> wrote:
> >> I like the idea of metadata axis. Your proposal for name/value pairs is
> >> simple and it can accommodate most of variations we may need.
>
> on 2nd thought I think axis is maybe undermining things a little ...
> whereas I completely see the benefit in a standard axis to deal with
> time ... metadata seems to be turning things on their head; we can
> just as easily inject attributes/elements to do the same thing.
>
> we need to keep in mind that when data is backed up / archived /
> extracted outside the system that metadata moves with it.


Keep things as simple as possible & try to use existing ... so, -1
for metadata axis. Yes, it simple, but break second rule.

+1 for mods way.

-- 
Dmitriy Shabanov

Re: [Exist-development] Metadata in eXist

[James F. <jam...@ex...>]

On 30 July 2010 11:37, Adam Retter <ad...@ex...> wrote:
>> I like the idea of metadata axis. Your proposal for name/value pairs is
>> simple and it can accommodate most of variations we may need.

on 2nd thought I think axis is maybe undermining things a little ...
whereas I completely see the benefit in a standard axis to deal with
time ... metadata seems to be turning things on their head; we can
just as easily inject attributes/elements to do the same thing.

we need to keep in mind that when data is backed up / archived /
extracted outside the system that metadata moves with it.

J

Re: [Exist-development] Metadata in eXist

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

> I don't like the idea of a property:: axis. If the metadata is an
> ordinary document, you can just use standard XPath, e.g.
> metadata("/db/my/doc.xml")//mods:titleInfo.

This is no different to having an axis in my vision! Surely better to
keep the existing doc and collection functions, and be able to access
the metadata naturally in a query by using metadata::
In this way you can slowly and easily introduce metadata into existing queries.


> Wolfgang
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> 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] Metadata in eXist

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

> It looks like there is a lot of thought around using key/value pairs. What
> value does key/value provide over using a stored XML (similar to MarkLogic)?
> Because on the inverse of that, I can see a lot of value in being able to
> store more complex structures, as they can be simple key/value pairs at
> their simplest and more complex for users who have that need.

When I said key/value - I meant that the value would be an XML Schema
Data Type - this could be an atomic value, a sequence of values or a
node. But in terms of storage it would be encoded as a value of the
key.

>
> --
> Patrick Bosek
> Jorsek Software
> Cell (585) 820 9634
> Office (585) 239 6060
> Jorsek.com
>
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> 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] Metadata in eXist

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

> I like the idea of metadata axis. Your proposal for name/value pairs is
> simple and it can accommodate most of variations we may need.

Keep in mind that a value would be either an atomic value or a
sequence; of XML Schema Data Type.


>> Accessing this metadata at the moment is possible via the image xquery
>> extension module.
>
>
> Actually the the existing image module gives vary limited metadata: hight,
> width and image type.
> It will really love to have all EXIF properties of an image as searchable
> metadata fields.

Well we could very easily integrate the JpegParser from Apache Tika
into the Image metadata function...

> What will be the format of the metadata if we request all available pairs?
> May be an element with all metadata pairs as attributes.

I am not sure at the moment, some sort of serialized xml format perhaps -

e.g.

/metadata::*

<metadata xmlns="http://exist-db.org/metadata">
   <key name="someKey">
      <value type="xs:string">hello world</value>
   </key>
   <key name="otherValue">
     <value type="node()">
      <a xmlns=""><b/></a>
     </value>
   </key>
</metadata>


-- 
Adam Retter

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

Re: [Exist-development] 4 failing tests on teamcity

[James F. <jam...@ex...>]

On 29 July 2010 22:27, Dannes Wessels <da...@ex...> wrote:
> Hi,
>
> On Thu, Jul 29, 2010 at 10:19 PM, James Fuller
> <jam...@ex...> wrote:
>> note we need to discuss about the lack of java properties being set
>> for unit tests ... its somewhat limiting and the cause of failing
>> tests at the moment on teamcity (though build is fine now).
>>
>> how do people feel if exist.home java property was available via unit
>> tests ... is this too 'unclean' ? I think it maybe, though we probably
>> also want to add some lowlevel unit tests for checking java properties
>> as well ;)
>
> That does quite reasonable. Well, there is one thing to add here: We
> should think of a way where *all* extensions and indexes are built...
> and tested. E.g. the spatial index is not tested on the build server
> while there is a test suite available.

agreed

> So basically we need to have a conf.xml and a
> extensions/local.build.properties in which all these items are
> enabled. Only this way we can detect issues in an early phase (we have
> missed issues in spatial before, waste of our time that was)

it seems like this would also help test configuration parts of the codebase

> anyway...all committers should run the junit suite first before
> committing changes....... with all extensions enabled. I guess just a
> few of us have all these things enabled. New rule for the Manifesto?

I agree and make my apologies not having done so ... in this case I
wanted to illustrate my problem, I will refactor code so that the 4
outstanding tests work today.

ta, J

Re: [Exist-development] 4 failing tests on teamcity

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

Hi,

On Thu, Jul 29, 2010 at 10:19 PM, James Fuller
<jam...@ex...> wrote:
> note we need to discuss about the lack of java properties being set
> for unit tests ... its somewhat limiting and the cause of failing
> tests at the moment on teamcity (though build is fine now).
>
> how do people feel if exist.home java property was available via unit
> tests ... is this too 'unclean' ? I think it maybe, though we probably
> also want to add some lowlevel unit tests for checking java properties
> as well ;)

That does quite reasonable. Well, there is one thing to add here: We
should think of a way where *all* extensions and indexes are built...
and tested. E.g. the spatial index is not tested on the build server
while there is a test suite available.

So basically we need to have a conf.xml and a
extensions/local.build.properties in which all these items are
enabled. Only this way we can detect issues in an early phase (we have
missed issues in spatial before, waste of our time that was)

anyway...all committers should run the junit suite first before
committing changes....... with all extensions enabled. I guess just a
few of us have all these things enabled. New rule for the Manifesto?

cheers

Dannes


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

[Exist-development] 4 failing tests on teamcity

[James F. <jam...@ex...>]

note we need to discuss about the lack of java properties being set
for unit tests ... its somewhat limiting and the cause of failing
tests at the moment on teamcity (though build is fine now).

how do people feel if exist.home java property was available via unit
tests ... is this too 'unclean' ? I think it maybe, though we probably
also want to add some lowlevel unit tests for checking java properties
as well ;)

going to bed now, will pick this up in the morning.

J