Nabble - exist-open

Re: Creating collection from xquery

2009-12-05T18:06:27Z

Tomek,

> I need to crate collections and few documents from xquery (executed via
> apache cocoon`s xquerygenerator), can anyone explain me how to achieve
> this ? I know that there is xmldb:remove() function which I
> successfully used to remove documents from collection, but I cannot find
> way to create collection and add new empty documents ?

I believe xmldb:create-collection() will do what you need. See
http://demo.exist-db.org/exist/functions/xmldb/create-collection.

Cheers,
Joe

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Creating collection from xquery

2009-12-05T14:29:28Z

Hi.
I need to crate collections and few documents from xquery (executed via
apache cocoon`s xquerygenerator), can anyone explain me how to achieve
this ? I know that there is xmldb:remove() function which I
successfully used to remove documents from collection, but I cannot find
way to create collection and add new empty documents ?

Regards,
Tomek Piechowicz

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

user authentication issue in 1.4

2009-12-05T07:35:43Z

I have another issue, which has to do with user authentication.

I have a simple application consisting of 3 files.

main.xql
login-panel.xqm
search-panel.xqm

After a user logs in, he is taken to a search screen. After hitting the search button he should be brought back to the same search screen. When run from eXist 1.2 this works. However, when run from eXist 1.4 he is logged out of the application.

Re: ArrayIndexOutOfBoundsException error

2009-12-03T23:47:39Z

Thomas,

parts of the eXist team, including myself, are currently in Austria
for a ski trip and our internet connection is not the best. But it
would be nice if you could send your test case to me. I'll look into
it if the connection allows.

Wolfgang

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: ArrayIndexOutOfBoundsException error

2009-12-03T19:10:31Z

Allister,

It is a simple code that runs in one part of the project ok, but when
the same code is called in a context of recursive function it throws
the error. That is why I assembled a piece of code and the data so the
situation can be reproduced in action.

Bellow is the function:

declare function summary:enum-summary-update( $data-enum-elements as
node()*, $summary as node() )as node()* {
let $enum_id := distinct-values( $data-enum-elements/@enum_id )
let $deleted := update delete $summary/*[ exists(@enum_id) and
not( @enum_id = $enum_id)]
return for $i in $enum_id
let $enum-nodes := $data-enum-elements[@enum_id = $i ]
let $values := distinct-values( $enum-nodes )
let $count := if( exists($enum-nodes/@count ) ) then sum(
$enum-nodes/@count) else count( $enum-nodes )
let $obsolete := $summary/*[ @enum_id = $i and not(. = $values) ]

return (
for $v in $values
let $node := $summary/*[ @enum_id = $i and . = $v ]
return (
if( $node ) then (
update value $node/@count with $count
)else (
update insert element { local-name(
$enum-nodes[1] ) } {
attribute enum_id {$i},
attribute count { $count},
string($v)
} into $summary
)
)
, (: delete orphans :)
update delete $obsolete
)
};

Regards,
Thomas

------

Thomas White

Mobile:+44 7711 922 966
Skype: thomaswhite
gTalk: thomas.0007
Linked-In:http://www.linkedin.com/in/thomaswhite0007
facebook: http://www.facebook.com/thomas.0007

summary:enum-summary-update( $data-enum-elements as node()*, $summary
as node() )as node()* {
let $enum_id := distinct-values( $data-enum-elements/@enum_id )
let $deleted := update delete $summary/*[ exists(@enum_id) and not(
@enum_id = $enum_id)]
return for $i in $enum_id
let $enum-nodes := $data-enum-elements[@enum_id = $i ]
let $values := distinct-values( $enum-nodes )
let $count := if( exists($enum-nodes/@count ) ) then sum(
$enum-nodes/@count) else count( $enum-nodes )
let $obsolete := $summary/*[ @enum_id = $i and not(. = $values) ]

return (
for $v in $values
let $node := $summary/*[ @enum_id = $i and . = $v ]
return (
if( $node ) then (
update value $node/@count with $count
)else (
update insert element { local-name( $enum-nodes[1] ) } {
attribute enum_id {$i},
attribute count { $count},
string($v)
} into $summary
)
)
, (: delete orphans :)
update delete $obsolete
)
};
2009/12/4 Alister Pillow <gspringtech@...>

>
> Can you post the code to the list? Is it XQuery?
> On 04/12/2009, at 8:09 AM, Thomas White wrote:
>
> > I really hope somebody will be able to look at this issue - a simple code
> > that was working some time ago, now throws this error. It is a showstopper
> > for me now.
> >
> > Regards,
> > Thomas
> >
> >
> > "Thomas White" <thomas.0007@...> wrote in message
> > news:hf82uf$n91$1@......
> >> I just checked and the code gives the same error in 1.4.x branch as well.
> >> Any takers?
> >>
> >> Thomas
> >>
> >>
> >> "Thomas White" <thomas.0007@...> wrote in message
> >> news:hf724p$q4k$1@......
> >>> Build from the trunk.
> >>>
> >>> I have created an test where the error bellow can be replicated.
> >>> Please contact me, to email you the code and the data.
> >>>
> >>> Regards,
> >>> Thomas
> >
> >
> >
> >
> > ------------------------------------------------------------------------------
> > Join us December 9, 2009 for the Red Hat Virtual Experience,
> > a free event focused on virtualization and cloud computing.
> > Attend in-depth sessions from your desk. Your couch. Anywhere.
> > http://p.sf.net/sfu/redhat-sfdev2dev
> > _______________________________________________
> > Exist-open mailing list
> > Exist-open@...
> > https://lists.sourceforge.net/lists/listinfo/exist-open
>

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: ArrayIndexOutOfBoundsException error

2009-12-03T17:36:06Z

Can you post the code to the list? Is it XQuery?
On 04/12/2009, at 8:09 AM, Thomas White wrote:

> I really hope somebody will be able to look at this issue - a simple code
> that was working some time ago, now throws this error. It is a showstopper
> for me now.
>
> Regards,
> Thomas
>
>
> "Thomas White" <thomas.0007@...> wrote in message
> news:hf82uf$n91$1@......
>> I just checked and the code gives the same error in 1.4.x branch as well.
>> Any takers?
>>
>> Thomas
>>
>>
>> "Thomas White" <thomas.0007@...> wrote in message
>> news:hf724p$q4k$1@......
>>> Build from the trunk.
>>>
>>> I have created an test where the error bellow can be replicated.
>>> Please contact me, to email you the code and the data.
>>>
>>> Regards,
>>> Thomas
>
>
>
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: ArrayIndexOutOfBoundsException error

2009-12-03T13:39:15Z

I really hope somebody will be able to look at this issue - a simple code
that was working some time ago, now throws this error. It is a showstopper
for me now.

Regards,
Thomas

"Thomas White" <thomas.0007@...> wrote in message
news:hf82uf$n91$1@......

>I just checked and the code gives the same error in 1.4.x branch as well.
> Any takers?
>
> Thomas
>
>
> "Thomas White" <thomas.0007@...> wrote in message
> news:hf724p$q4k$1@......
>> Build from the trunk.
>>
>> I have created an test where the error bellow can be replicated.
>> Please contact me, to email you the code and the data.
>>
>> Regards,
>> Thomas

Re: Exist-open Digest, Vol 44, Issue 11

2009-12-03T11:20:00Z

Joe,

Awesome, thanks.

I had pinned it down in IE before, using some special <meta> tags but could not figure firefox. this is an interesting page about how to make IE8 do different rendering modes:
http://msdn.microsoft.com/en-us/library/cc288325(VS.85).aspx

After your response, I found this page which goes into detail:
http://en.wikibooks.org/wiki/XQuery/eXist_Crib_sheet

Finally, I have an XQuery that might return XHTML or XML, so I used the util:declare-option function, based off your example to dynamically declare the doctype:

let $decl := util:declare-option("exist:serialize", "method=xhtml media-type=text/html omit-xml-declaration=no indent=yes doctype-public=-//W3C//DTD XHTML 1.0 Transitional//EN doctype-system=http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"),

thanks,
andrew

On Thu, Dec 3, 2009 at 2:04 PM, Joe Wicentowski <joewiz@...> wrote:

Andrew,

> Has anyone been successful getting eXist XQuery code to return XHTML with
> the appropriate <!DOCTYPE> set?
>
> I cannot get the HTML coming out of exist to render in strict mode, it
> defaults to quirks without a <!DOCTYPE> for XHTML and strict.

Here's what I use:

declare option exist:serialize "method=xhtml media-type=text/html
omit-xml-declaration=no indent=yes
doctype-public=-//W3C//DTD XHTML 1.0 Transitional//EN
doctype-system=http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";

Cheers,
Joe

Re: Exist-open Digest, Vol 44, Issue 11

2009-12-03T11:04:29Z

Andrew,

> Has anyone been successful getting eXist XQuery code to return XHTML with
> the appropriate <!DOCTYPE> set?
>
> I cannot get the HTML coming out of exist to render in strict mode, it
> defaults to quirks without a <!DOCTYPE> for XHTML and strict.

Here's what I use:

declare option exist:serialize "method=xhtml media-type=text/html
omit-xml-declaration=no indent=yes
doctype-public=-//W3C//DTD XHTML 1.0 Transitional//EN
doctype-system=http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";

Cheers,
Joe

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: Exist-open Digest, Vol 44, Issue 11

2009-12-03T09:08:46Z

Team,

Has anyone been successful getting eXist XQuery code to return XHTML with the appropriate <!DOCTYPE> set?

I cannot get the HTML coming out of exist to render in strict mode, it defaults to quirks without a <!DOCTYPE> for XHTML and strict.

Help?
Thanks,
Andrew

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: Question about caching of indexes?

2009-12-03T09:07:12Z

This group never ceases to amaze me!

Thanks Andrzej and all the developers who work so tirelessly.

gary

> and now....
>
> The shrink threshold is configurable in eXist's conf.xml file.
>
> There is a new parameter for the <db-connection> element, called:
> cacheShrinkThreshold. The default value has stayed the
> same at 10,000. However, if you set this parameter to -1 (or any negative
> number), then caches will never be shrunk
> based on load levels.
>
> So to turn off cache idle time shrinkage, just do cacheShrinkThreshold="-
> 1".
>
> In SVN Trunk as of a few minutes ago.
>
> You're welcome, Gary! LOL
>
> --
> Andrzej Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com

Re: Question about caching of indexes?

2009-12-03T08:29:18Z

Gary asked, beating me to the punch:

> I was wondering if this idle time is configurable, or where I may be able to tweak the code to turn this off. I have
> a case where the application could be idle for a while and cause a slow response while the cache repopulates.

...to which Wolfgang replied:

> This is not configurable (though it would be nice if it were). You
> could edit org.exist.storage.DefaultCacheManager and set the constant
> SHRINK_THRESHOLD to Integer.MAX_VALUE. This will make sure that caches
> never shrink.

and now....

The shrink threshold is configurable in eXist's conf.xml file.

There is a new parameter for the <db-connection> element, called: cacheShrinkThreshold. The default value has stayed the
same at 10,000. However, if you set this parameter to -1 (or any negative number), then caches will never be shrunk
based on load levels.

So to turn off cache idle time shrinkage, just do cacheShrinkThreshold="-1".

In SVN Trunk as of a few minutes ago.

You're welcome, Gary! LOL

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

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: web app not recognizing changes to stored xquery file

2009-12-03T07:25:17Z

Normally I use webdav - but I've also tried with the Java client and the same thing is happening.

James Fuller-4 wrote:

On Thu, Dec 3, 2009 at 1:00 PM, Swami Kevala <swami.kevala@gmail.com> wrote:
>
> Hi,
>
> I have an xquery application stored in my eXist 1.4 database. There is one
> module called 'search-fns.xqm'. If I alter the code in that file and load
> the web application, the change is reflected - but if I then make any other
> subsequent change to that file, the change is not reflected in the
> application.

How are you loading xquery file into database when making these
changes ? e.g. via java client, webdav, etc ?

Jim Fuller

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: Lucene and XQuery

2009-12-03T06:13:25Z

Thanks Joe for the quick reply. I have searched the mailing list
before posting, but haven't found a definite answer to my questions.

I'll go with the suggested parsing of a string or maybe an alternative
gui solution for searching multiple fields.

Thanks again for the help.

Regards,
Vilmos.

On 12/3/09, Joe Wicentowski <joewiz@...> wrote:

> Vilmos,
>
>> This way only one field can be set to be searched. I'm interested in
>> forming full lucene queries like:
>> title:"The Right Way" AND text:go
>> (http://lucene.apache.org/java/2_4_0/queryparsersyntax.html)
>
> Lucene's fielded search capabilities are not yet available in eXist.
> Several people have recently asked about this, though - you might
> find it worthwhile to search the mailing list archives to see those
> dialogs.
>
>> As described in the documentations, the ft:query can take any lucene's
>> default query syntax, but when I try to run this:
>> //*[ft:query(., SPEECH:"boil")]
>> it gives no results
>
> This doesn't work because you're using fielded search syntax.
>
>> however when specified like this it works:
>> //*[ft:query(SPEECH, "boil")]
>
> This works because you're using the supported QName-based search syntax.
>
>> This is fine if only one field is included in the search. What if I
>> need a more complex query that include multiple fields (title:"The
>> Right Way" AND text:go)?
>
> Let's distinguish between syntax and the query itself. You could
> write a query that works in eXist today that searches both the title
> elements and the text elements of documents... something like:
>
> //*[ft:query(title, "The Right Way")][ft:query(text, "go")]
>
> You can also describe this query in XML, as described in
> http://exist-db.org/lucene.html#N10352. But as to parsing the syntax
> of (title:"The Right Way" AND text:go) into this query, this is up to
> you to implement.
>
> Joe
>

Re: Lucene and XQuery

2009-12-03T05:48:28Z

Vilmos,

> This way only one field can be set to be searched. I'm interested in
> forming full lucene queries like:
> title:"The Right Way" AND text:go
> (http://lucene.apache.org/java/2_4_0/queryparsersyntax.html)

Lucene's fielded search capabilities are not yet available in eXist.
Several people have recently asked about this, though - you might
find it worthwhile to search the mailing list archives to see those
dialogs.

> As described in the documentations, the ft:query can take any lucene's
> default query syntax, but when I try to run this:
> //*[ft:query(., SPEECH:"boil")]
> it gives no results

This doesn't work because you're using fielded search syntax.

> however when specified like this it works:
> //*[ft:query(SPEECH, "boil")]

This works because you're using the supported QName-based search syntax.

> This is fine if only one field is included in the search. What if I
> need a more complex query that include multiple fields (title:"The
> Right Way" AND text:go)?

Let's distinguish between syntax and the query itself. You could
write a query that works in eXist today that searches both the title
elements and the text elements of documents... something like:

//*[ft:query(title, "The Right Way")][ft:query(text, "go")]

You can also describe this query in XML, as described in
http://exist-db.org/lucene.html#N10352. But as to parsing the syntax
of (title:"The Right Way" AND text:go) into this query, this is up to
you to implement.

Joe

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: web app not recognizing changes to stored xquery file

2009-12-03T04:59:21Z

On Thu, Dec 3, 2009 at 1:00 PM, Swami Kevala <swami.kevala@...> wrote:
>
> Hi,
>
> I have an xquery application stored in my eXist 1.4 database. There is one
> module called 'search-fns.xqm'. If I alter the code in that file and load
> the web application, the change is reflected - but if I then make any other
> subsequent change to that file, the change is not reflected in the
> application.

How are you loading xquery file into database when making these
changes ? e.g. via java client, webdav, etc ?

Jim Fuller

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Lucene and XQuery

2009-12-03T04:45:43Z

Hi all!

I have set up a lucene search according to the documentation on this
site: http://en.wikibooks.org/wiki/XQuery/Lucene_Search and
http://demo.exist-db.org/lucene.xml

I am querying lucene from XQuery according to the example:
for $m in //SPEECH[ft:query(., "boil bubble")]
order by ft:score($m) descending
return $m

This way only one field can be set to be searched. I'm interested in
forming full lucene queries like:
title:"The Right Way" AND text:go
(http://lucene.apache.org/java/2_4_0/queryparsersyntax.html)

As described in the documentations, the ft:query can take any lucene's
default query syntax, but when I try to run this:
//*[ft:query(., SPEECH:"boil")]
it gives no results, however when specified like this it works:
//*[ft:query(SPEECH, "boil")]

This is fine if only one field is included in the search. What if I
need a more complex query that include multiple fields (title:"The
Right Way" AND text:go)?

Is there a way to search the database based only on the lucene's search query?

Thanks in advanced for the replies.

Regards,
Vilmos Somogyi

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

web app not recognizing changes to stored xquery file

2009-12-03T04:00:47Z

Hi,

I have an xquery application stored in my eXist 1.4 database. There is one module called 'search-fns.xqm'. If I alter the code in that file and load the web application, the change is reflected - but if I then make any other subsequent change to that file, the change is not reflected in the application.

Only if I make changes to any of the other .xqm or .xql files, all the changes (including the change to the search-fns.xqm file) are recognized when refreshing the web app.

This has only just recently started happening a few days after moving to version 1.4.

Kind Regards

Swami Kevala

Re: ArrayIndexOutOfBoundsException error

2009-12-03T02:12:32Z

I just checked and the code gives the same error in 1.4.x branch as well.
Any takers?

Thomas

"Thomas White" <thomas.0007@...> wrote in message
news:hf724p$q4k$1@......
> Build from the trunk.
>
> I have created an test where the error bellow can be replicated.
> Please contact me, to email you the code and the data.
>
> Regards,
> Thomas

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

ArrayIndexOutOfBoundsException error

2009-12-02T16:52:41Z

Build from the trunk.

I have created an test where the error bellow can be replicated.
Please contact me, to email you the code and the data.

Regards,
Thomas

java.lang.ArrayIndexOutOfBoundsException: 15
at
org.exist.storage.RangeIndexSpec.indexTypeToXPath(RangeIndexSpec.java:106)
at org.exist.dom.NodeProxy.getIndexType(NodeProxy.java:388)
at org.exist.dom.NewArrayNodeSet.getIndexType(NewArrayNodeSet.java:1125)
at
org.exist.xquery.GeneralComparison.quickNodeSetCompare(GeneralComparison.java:580)
at org.exist.xquery.GeneralComparison.eval(GeneralComparison.java:383)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.Predicate.selectByNodeSet(Predicate.java:495)
at org.exist.xquery.Predicate.evalPredicate(Predicate.java:361)
at org.exist.xquery.LocationStep.processPredicate(LocationStep.java:258)
at org.exist.xquery.LocationStep.applyPredicate(LocationStep.java:245)
at org.exist.xquery.LocationStep.eval(LocationStep.java:421)
at org.exist.xquery.pragmas.Optimize.eval(Optimize.java:169)
at org.exist.xquery.ExtensionExpression.eval(ExtensionExpression.java:71)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.LetExpr.eval(LetExpr.java:155)
at org.exist.xquery.ForExpr.eval(ForExpr.java:312)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.ForExpr.eval(ForExpr.java:312)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:137)
at org.exist.xquery.DynamicTypeCheck.eval(DynamicTypeCheck.java:61)
at org.exist.xquery.FunctionCall.evalFunction(FunctionCall.java:274)
at org.exist.xquery.FunctionCall.eval(FunctionCall.java:201)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:102)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:100)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.LetExpr.eval(LetExpr.java:155)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.ForExpr.eval(ForExpr.java:312)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:102)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:137)
at org.exist.xquery.DynamicTypeCheck.eval(DynamicTypeCheck.java:61)
at
org.exist.xquery.FunctionCall$DeferredFunctionCallImpl.execute(FunctionCall.java:344)
at
org.exist.xquery.DeferredFunctionCall.realize(DeferredFunctionCall.java:51)
at
org.exist.xquery.DeferredFunctionCall.isEmpty(DeferredFunctionCall.java:178)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:84)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:102)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:137)
at org.exist.xquery.DynamicTypeCheck.eval(DynamicTypeCheck.java:61)
at
org.exist.xquery.FunctionCall$DeferredFunctionCallImpl.execute(FunctionCall.java:344)
at
org.exist.xquery.DeferredFunctionCall.realize(DeferredFunctionCall.java:51)
at
org.exist.xquery.DeferredFunctionCall.isEmpty(DeferredFunctionCall.java:178)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:84)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:102)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:137)
at org.exist.xquery.DynamicTypeCheck.eval(DynamicTypeCheck.java:61)
at
org.exist.xquery.FunctionCall$DeferredFunctionCallImpl.execute(FunctionCall.java:344)
at
org.exist.xquery.DeferredFunctionCall.realize(DeferredFunctionCall.java:51)
at
org.exist.xquery.DeferredFunctionCall.isEmpty(DeferredFunctionCall.java:178)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:84)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:102)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:137)
at org.exist.xquery.DynamicTypeCheck.eval(DynamicTypeCheck.java:61)
at
org.exist.xquery.FunctionCall$DeferredFunctionCallImpl.execute(FunctionCall.java:344)
at
org.exist.xquery.DeferredFunctionCall.realize(DeferredFunctionCall.java:51)
at
org.exist.xquery.DeferredFunctionCall.isEmpty(DeferredFunctionCall.java:178)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:84)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:102)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:137)
at org.exist.xquery.DynamicTypeCheck.eval(DynamicTypeCheck.java:61)
at
org.exist.xquery.FunctionCall$DeferredFunctionCallImpl.execute(FunctionCall.java:344)
at
org.exist.xquery.DeferredFunctionCall.realize(DeferredFunctionCall.java:51)
at
org.exist.xquery.DeferredFunctionCall.isEmpty(DeferredFunctionCall.java:178)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:84)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at
org.exist.xquery.ConditionalExpression.eval(ConditionalExpression.java:102)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.UserDefinedFunction.eval(UserDefinedFunction.java:137)
at org.exist.xquery.DynamicTypeCheck.eval(DynamicTypeCheck.java:61)
at org.exist.xquery.FunctionCall.evalFunction(FunctionCall.java:274)
at org.exist.xquery.FunctionCall.eval(FunctionCall.java:201)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.SequenceConstructor.eval(SequenceConstructor.java:83)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.EnclosedExpr.eval(EnclosedExpr.java:70)
at org.exist.xquery.ElementConstructor.eval(ElementConstructor.java:271)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at
org.exist.xquery.DynamicCardinalityCheck.eval(DynamicCardinalityCheck.java:71)
at org.exist.xquery.functions.system.AsUser.eval(AsUser.java:83)
at org.exist.xquery.InternalFunctionCall.eval(InternalFunctionCall.java:55)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:56)
at org.exist.xquery.DebuggableExpression.eval(DebuggableExpression.java:63)
at org.exist.xquery.LetExpr.eval(LetExpr.java:208)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.LetExpr.eval(LetExpr.java:206)
at org.exist.xquery.BindingExpression.eval(BindingExpression.java:158)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.PathExpr.eval(PathExpr.java:241)
at org.exist.xquery.AbstractExpression.eval(AbstractExpression.java:61)
at org.exist.xquery.XQuery.execute(XQuery.java:227)
at org.exist.xquery.XQuery.execute(XQuery.java:182)
at
org.exist.xmldb.LocalXPathQueryService.execute(LocalXPathQueryService.java:185)
at org.exist.http.servlets.XQueryServlet.process(XQueryServlet.java:416)
at org.exist.http.servlets.XQueryServlet.doGet(XQueryServlet.java:173)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:224)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
at org.exist.http.urlrewrite.Forward.doRewrite(Forward.java:44)
at
org.exist.http.urlrewrite.XQueryURLRewrite.doRewrite(XQueryURLRewrite.java:426)
at
org.exist.http.urlrewrite.XQueryURLRewrite.doFilter(XQueryURLRewrite.java:297)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:915)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: Xprocxq in latest SVN

2009-12-02T14:44:20Z

I wonder if this 'request:get-parameter-names()' is working now.

I have a full data instance in xforms to sent to an xproc file in db for processing, and it is not handy and elegant to use ?bindings.

Claudius Teodorescu

Re: eXist on FLOSS weekly podcast

2009-12-02T13:27:52Z

On 2 Dec 2009, at 21:19, Mike Sokolov wrote:

> I really shouldn't ask, but:
>
> empty-sosofo?
>>
(specification of a sequence of flow objects)

<empty/> in other words.
--
Sebastian Rahtz
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

Sólo le pido a Dios
que el futuro no me sea indiferente

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: eXist on FLOSS weekly podcast

2009-12-02T13:19:41Z

I really shouldn't ask, but:

empty-sosofo?

Sebastian Rahtz wrote:

On 2 Dec 2009, at 20:36, Wolfgang Meier wrote:

It is DSSSL, a predecessor of XSLT
(http://en.wikipedia.org/wiki/Document_Style_Semantics_and_Specification_Language).
It was based on a subset of scheme and thus very powerful. I'm not
sure why XSL did win over it ;-)


a) because the DSSSL monster was divided into XSLT and XSL FO, and James Clark actually _implemented_
XSLT fully. No-one ever finished implementing DSSSL (though James tried hard), but we had several
good implementations of XSL within the first year.

b) because XSL was expressed in XML and it suddenly made sense...

that said, DSSSL was ace. What's not to love about this?

(root
  (make sequence
  (make empty-element gi: "hr")
  (make element gi: "table"  attributes: (list (list "border" ""))
                (process-children))))
(element name
   (make element gi: "tr" 
         (process-children-trim)))
(element rname
   (make element gi: "td" 
      (make element gi: "font" attributes: (list (list "Face" "Symbol"))
             (process-children-trim))))
(element sname (empty-sosofo))

(element count
   (make element gi: "td" 
         (process-children-trim)))

--
Sebastian Rahtz      
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

Sólo le pido a Dios
que el futuro no me sea indiferente





------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: eXist on FLOSS weekly podcast

2009-12-02T13:13:23Z

On Dec 2, 2009, at 12:36 PM, Wolfgang Meier wrote:
>
> It is DSSSL, a predecessor of XSLT
> (http://en.wikipedia.org/wiki/Document_Style_Semantics_and_Specification_Language).
> It was based on a subset of scheme and thus very powerful. I'm not
> sure why XSL did win over it ;-)

Angle brackets can move faster through the tubes!
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Error reporting is missing the debug data from the function where the error it occurs

2009-12-02T13:05:07Z

I am using the code from the trunk.

I noticed if there is an error in a nested function calls, the function
stack dump misses the debug data for the last function, like function name
and the line number, where the error acctually occured. I guess the debug
data is there, but it gets lost somewhere.

Regards,
Thomas

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: eXist on FLOSS weekly podcast

2009-12-02T12:46:36Z

On 2 Dec 2009, at 20:36, Wolfgang Meier wrote:
>
> It is DSSSL, a predecessor of XSLT
> (http://en.wikipedia.org/wiki/Document_Style_Semantics_and_Specification_Language).
> It was based on a subset of scheme and thus very powerful. I'm not
> sure why XSL did win over it ;-)
>

a) because the DSSSL monster was divided into XSLT and XSL FO, and James Clark actually _implemented_
XSLT fully. No-one ever finished implementing DSSSL (though James tried hard), but we had several
good implementations of XSL within the first year.

b) because XSL was expressed in XML and it suddenly made sense...

that said, DSSSL was ace. What's not to love about this?

(root
(make sequence
(make empty-element gi: "hr")
(make element gi: "table" attributes: (list (list "border" ""))
(process-children))))
(element name
(make element gi: "tr"
(process-children-trim)))
(element rname
(make element gi: "td"
(make element gi: "font" attributes: (list (list "Face" "Symbol"))
(process-children-trim))))
(element sname (empty-sosofo))

(element count
(make element gi: "td"
(process-children-trim)))

--
Sebastian Rahtz
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

Sólo le pido a Dios
que el futuro no me sea indiferente

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: eXist on FLOSS weekly podcast

2009-12-02T12:36:06Z

Thanks Joe and Jens! It already feels funny to see and hear yourself
recorded, but reading your own words in a transcription is really a
strange experience ;-)

> I am sure I mixed Randal Schwartz and Leo Laporte up a few times. What is this thing I hear as "DISL"?

It is DSSSL, a predecessor of XSLT
(http://en.wikipedia.org/wiki/Document_Style_Semantics_and_Specification_Language).
It was based on a subset of scheme and thus very powerful. I'm not
sure why XSL did win over it ;-)

Wolfgang

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: eXist on FLOSS weekly podcast

2009-12-02T09:02:12Z

Thanks for the suggestion, Joe: that seemed like a nice way to while away a lazy afternoon!

A preliminary transcription of the first half of the interview, for anyone to use as they please; The afternoon is over: I will do the rest later, if there is any interest.

I am sure I mixed Randal Schwartz and Leo Laporte up a few times. What is this thing I hear as "DISL"?

You can easily skip the first part without missing anything important: start at 13:20.

Jens

PS: I noticed an unusually high incidence of the word "efficient" in Wolfgang's speak. Is there, after all, a connection between eXist and the reputed fuel efficiency of the Opel Kadett?

On Dec 2, 2009, at 2:04 PM, Joe Wicentowski wrote:

>> I had the (real) pleasure to be interviewed by Randal Schwartz and Leo
>> Laporte during their FLOSS weekly show last week:
>
> That was a great interview, Wolfgang! Randal and Leo were clearly
> deeply impressed with eXist.
>
> There were so many great quotes and exchanges - perhaps it'd be worth
> folks transcribing them for a post on the exist-db.org site. Here's a
> 'chapter' breakdown of the show (based on the audio podcast,
> http://twit.tv/floss97):
>
> Chatter until 6m:45s

RS: you know, Leo, we've had a few shows in the last month or two that have been - sort-of - anybody can understand what we are talking about because it's just a distro or a general technology or something. I decided just to mix up the pitches just a little bit: today's show is a high-end technical, geeko, massive TLA, three-letter acronyms, mass-out [?] show. We have brought on the Wolfgang Meier, a good German man who, many years ago actually, almost all the way back to 2000, created this thing called 'eXist-db' - now, if that is not already geeky enough, eXist-db is an XML database which means that instead of having traditional rows and columns like you'd have in an SQL database, it actually stores the documents, as far as I can tell, stores the documents, in their native XML shape, which is more hierarchical than rectangular, and there is all sorts of XSLT involved and and XQuery language and REST and SOAP and - I tell you, I think we're going to have more acronyms than we've had in a show in a long time, so if your eyes start glazing over, I'll know, it's no problem! [… 8'07] No, I think you will all enjoy it, but before we get to that though,

> 8:10 ad for the show sponsor

I want to give you one more acronym: SYNC - we should come up with what that means! Ah, "Say your next command" - how about that? [… lenghty praise for Ford SYNC, an in-car communications and entertainment system developed by Ford and Microsoft]

> 12:07 wolfgang enters

RS: Alright, are you ready to go to Germany?

LL: Yeah, I think he's in Frankfurt. Wolfgang Meier on the line, are you in Frankfurt?

WM: Yeah, sure: close to Frankfurt, actually.

RS: That's probably all I'll be able to figure out, so ….

LL: How close to Frankfurt - is there a name, just for the five people that probably live near you.

WM: Rüsselsheim.

RS: I've been to Darmstadt.

WM: Actually - ah, yeah, that's not too far away, just 20 kilometer or so.

RS: I've been to Darmstadt, so I know a little bit about that.

WM: Yeah, Rüsselsheim is quite famous right now because it is the headquarters of Opel, the company which General Motors tried to sell. Oh, well, they didn't sell it right now, but they were supposed to do it, so ….

RS: Well, we have another connection because my very first car was an Opel Kadett!

WM: Ah, right, OK!

RS: I know how to fix, I can tune that car! I can fix that car, because I had to - I was an impoverished student.

LL: So this whole show can be about: things about Germany […] but let's not: let's talk about eXist-db.

> 13:20 about background

Are you the chief developer on this, Wolfgang, or is there a large team working on it?

WM: I created the project, quite some time ago, actually it's now nearly ten years, and I have been working on it for the few few years, more or less on my own, but then, well, new people started to contribute and I think that right now we have about, well we have a core team working together every day like, oh, five-six people, and then there are, I don't know, and then there are ten-twenty-thirty more people are contributing to certain areas - certain features or extensions, indexes …. query features, whatever.

LL: So what was the problem you were trying to solve at the beginning? What problem were you trying to solve? What was missing that had you start this?

WM: Oh, when I started the project in, around 2000, summer 2000, yeah, well, XML had already been released as a specification, but not much more, so in the beginning we just had XML documents, and I was working with SGML before that, and well, we had XML documents and we used at that time still, eh, that horrible stylesheet language called "DISL" [?] which was a scheme dialect, but there wasn't much more, no way to query those documents, and I had lots of those documents and I thought about how, how I could query them efficiently. And I ended up in my summer holiday reading a few papers about efficient indexing of XML and it was all quite new at that time and I decided to implement, some of the procedures and algorithms I found in those papers, and, yeah, that's how it started and over time, it evolved, and as more and more standards came into the XML family, so now it is a whole stack of standards, but it all grew over the years.

> 15:45 relational databases vs xml databases

LL: OK, so you started with something that was just really efficient with indexing because you read this paper on it, now, me of the things that I am familiar with in terms of XML is that it sort-of doesn't shape well in traditional databases, because it's all about hierarchical data, rather than, you know, rows and columns, now is that one of the problems you were trying to solve initially with this indexing [?], that is, how do you get efficient indexing, because it is triangular rather than square?

WM: Yeah, well, the huge advantage of XML databases in general is that, well, you don't need to shred [?] your XML document into relational tables anymore, but, what the database does, it takes the model of your document., basically the tree model, behind it, and directly stores that into an efficient data structure, so you can query that immediately, without creating a mapping scheme or anything, you just put your data into the database and then start writing your queries, so it's very good for a rapid prototyping approach, you don't need all this mapping to and from tables. [16'41] So that one advantage all XML databases have and that's why they are used, in eXIst in particular, I was interested in how to address nodes within that document tree so I could efficiently access them at any time without loading the entire document back into memory, because that is what you don't want, if you have really large documents.

LL: Well, you could address those with XPath. Did XPath exist at that time?

WM: Yeah, XPath already existed in a rough version, I think, but well, the problem just is, like, XPath, the core expressions in XPath are like: well, find me all title tags which are descendants of chapters, things like that, so basically what eXist does, it applies a so-called numbering scheme to the document tree, and this numbering scheme allows you, if you have the number of the title, you can immediately tell if this number can actually be a descendant of any chapter, so it is just by comparing those numeric node document id's that you can resolve those path expressions.

RS: Right, so you start with an XML document, you can query it with XPath, and then you, then as data matured, as specifications matured, you added SQL to it, I understand, right?

WM: [18'20] Ah yeah, later on there were those, ah, other attempts to create a query language and we finally ended up with XQuery, which is a rather complete, functional language, I think, which means it is not just a query language like SQL is, we use XQuery pretty much, ah, as a server-side web development language. I have written, ah, quite a few web sites, just using XQuery and things like XSLT. So it is more, it's not like just a query language, but it is also a replacement for things like PHP or JSP or whatever. The good thing is that you can use XML and related standards to create an entire web site and you don't need to bother with any other high-level languages.

LL: So let me understand this then, so you can start with XML documents as your data source, you would use XQL to pull out pieces of that, XQuery language, and then you would also maybe process that with some XSLT perhaps, or is that to Perl [?] to XQL?, and then it would spit out entire web pages, the browser couldn't tell that you've got all this machinery behind the scenes, is that a description?

WM: Yeah, sure, for example, our entire web site is powered like that. All the tools on the web site, even the tools to try out XQuery stuff or to look up the function documentation, whatever, it is all just XQuery running in the background, on the server, on the database, and that XQuery directly has access to the XML documents stored in the database and all the indexes and stuff.

RS: Well, this seems a bit unusual, compared to traditional approaches, like PHP and MySQL, so would someone coming from a PHP world be completely confused by all this? Is there a transition path, or is it actually pretty natural, once you start playing with it - of course you'll say yes to that - but tell me how I would get from the PHP world to where you are talking about.

WM: Oh, we have quite a lot of users who start with PHP or even Perl or whatever they learned first, and then they discover eXist or another XML database, and, well, they start programming to the database, they - we offer SOAP interfaces or REST-style interfaces, XML-RPC, eXist has six-seven different network interfaces, you can use it from, so people still continue to write PHP scripts, until at some point, they start to create more and more complex XQueries, and finally discover, OK, basically I could just replace my entire PHP script that I had previously with my XQuery. So it is a step-by-step learning process, I think.

RS: So this would be similar to taking, say, a traditional database with stored procedures [21'46], say postgres, and discovering that I can move a little more of my application into the postgres stored procedures, rather than computing it in my view code, I can push that more and more into the data processing code, until eventually, my entire, my entire program is one line of PHP, one line of Perl, that say: go, take this data and give it the URL content for it, right?

WM: Yeah, exactly, a little bit like that, except that, well it is not just XQuery, but it is the entire XML stack you have available, like, you can combine it with XForms to create web-based forms, and it is very natural for XForms to interact with an XML database, well, because your form, it would just send an XML document back to the database which would store it or process it, with XQuery or whatever. Also very natural, I think, for people coming from Perl or PP is that eXist allows you, in the same way as SQL to have stored procedures, it allows you to store those XQueries into the database, and then you can map them to an URI or whatever, so basically you end up with RESTful, with a RESTful architecture, where URI's do directly translate to queries running in the background, which access the database, from there, it is rather easy to create a modularized application.

RS: Wow!

LL: So let us bring this back to something I can relate to again, so let's say you had a blog and you wanted to manage your blog, using this system, I could store an XML doc that had abstract, posting, subject, date, body, reference URL or something, repeated over and over again in an XML doc, with one particular schema, and then generate some SQL pages that would extract this and provide the view for the typical blog visitor, but I could also have another URL published, that would directly execute XQL to go give me the RSS feed for that blog? Does that make sense? [24'01]

WM: Yeah, sure: absolutely. If you look at our own blog or wiki, it works like that. It stores all the entries and feeds as ATOM - ATOM is another XML standard - it directly stores that stuff as a ATOM feed and what you are editing on the Wiki page is actually the ATOM entry, and it is one XQuery which does the entire rendering to display, display of the translation of the ATOM feed into a web page, and you can also certainly directly click on the feed link and get the live ATOM feed back.

LL: Would … this all sounds expensive, in performance-wise - am I going to get the same sort of throughput out of a box that I would get if I just had a LAMP-stack on that?

> 25:10 overhead of xml databases vs. lamp stack

WM: Ahem, [25'00], well it depends, I mean there are [laughter, all three], there is certainly a price you have to pay, but I think that is a price you have to pay for the entire technology. In the beginning of XML, people used to believe that you could really replace your good old MySQL or Oracle database with an XML database, ahem, that might be true, but I never really believed that it is always useful, I think there are lots of use cases where the good old relational database is still, well, a very good choice, if you have well-structured data which you can easily manage, where you can define a good, fixed schema which you do not need to change afterwards, then why switch to an XML database? It doesn't make much sense, doesn't help much, but if your application is going to be more complex and need to mix heavily-structured, well-structured data with less regularly structured data, if you have a mixture of text-like documents with, well, table-like dat, then it makes a lot of sense to use an XML database, and in that case, you certainly have to pay a price for all the processing power XQuery has to offer and for the simplicity of its use, well, I think that if you do it in an intelligent way, you will always be able to, get enough performance out of it, and --- yeah.

> 27:10 exist vs other new "nosql" dbs

LL: So this puts you in the same league, I guess, as these, new-fangled, document-based systems like CouchDB and Mongo and things like that. Are you exchanging ideas with them now or are you saying, well, it took you six years to get to the party, but we're already here, or where are you with all those guys?

WM: [27'15] Well, I am very interesting in those technologies and I really be very certainly watching them and what they do, and I think, there are a few interesting developments we can benefit from, for example if I look at some of the, just key-value-based storage backends, then I could also think of using those backends if they are very efficient, within eXist, why not, so I think we are learning from them, and, I am also interested in incorporating other people's open source code,if possible, so that's an interesting development, but the entire XML thing is a lot about standards, and there is not just one standard: XML's got a lot of other standards around it which have developed throughout the years, I mean, let's say there is ATOM for content publishing, there are standards like TEI, the Text Encoding Initiative which is heavily used within the humanities - there are lots of other XML-based standards, and I think that's the big advantage of the whole XML thing, that you have all those standards working together, and in the end it should all be, well, it should all integrate into one framework which is as easy as possible to use for the end-user, that's our role.

LL: So it seems like you would be, then, as you are saying, if I understand this, to take this existing XML standards and use appropriate XSLT and XQuery against those incoming and outgoing documents to, and, like, this database is closer to all that, being an all-native XML database, so for those applications we're going to place some existing standards that make sense to you, something like this, whereas, you know, the other key-value-pair databases like Mongo and things like that, they're going to be a further distance in mapping?

WM: [29'32] Yeah, sure, I think that key-value-pair databases, for example, are extremely efficient, if you have, well, a limited, if you have limited requirements where you just need an extremely fast data throughput, but if you have a scenario with, well, a database which has been, a dataset which has been growing over the years and which incorporates highly-structured text documents and combines it with other data and things like that, then we are certainly better off looking into XML standards and all the tools that help you process those standards. [30'25]

> 31:35 transaction support
> 32:08 security, roles
> 34:15 architecture, java
> 34:48 hosting, deployment
> 35:44 development platform
> 36:08 example sites
> 36:25 state dept office of the historian site, history.state.gov
> 37:20 competitor products: oracle, ibm, ms, ml
> 38:25 how did eXist win over the state dept
> 39:25 the main guy behind the state dept website
> 41:00 standards, xml, tei
> 41:45 lucene
> 42:50 xquery
> 43:20 applications besides the humanities
> 44:45 randall's overall judgment about exist
> 45:40 last words
> 46:35 thanks, close of interview with wolfgang
> 46:59 post-interview discussion about exist begins
> 47:13 history.state.gov, exist, xquery
> 50:23 "brought down" state dept website
> 51:45 thanksgiving wishes, closing
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: Question about caching of indexes?

2009-12-02T08:41:01Z

Hi Gary,

> I was wondering if this idle time is configurable, or where I may be able to
> tweak the code to turn this off. I have a case where the application could
> be idle for a while and cause a slow response while the cache repopulates.

This is not configurable (though it would be nice if it were). You
could edit org.exist.storage.DefaultCacheManager and set the constant
SHRINK_THRESHOLD to Integer.MAX_VALUE. This will make sure that caches
never shrink.

Wolfgang

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: namespace issues

2009-12-02T08:39:06Z

You previously mentioned:

> but it sounds like that would be bad because i'd have a wildcard like
> /*:root/dh:docheader/

Is there a reason your queries have to begin with /*:root? Why not
just query directly for //*:company ?

> what would be the most performant way to structure the document to be able
> to query all documents for company and report with the condition that each
> report type's root element will be in a different namespace?

I'm not quite sure in what respect you mean "performant", but you can
query all documents for company with //*:company or
distinct-values(//*:company) . Based on the returns of that query,
you can produce your report about the matching documents.
For example,

for $company in //*:company
let $report := $company/parent::*
return local:create-report($report)

Joe

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: Multi-modules in one namespace not working.

2009-12-02T08:37:23Z

The multi-source per module feature is indeed missing in eXist. I
remember some XQTS tests are failing because of that.

> If anyone can give me a starting point in the code where the modules get loaded (import module ...), I'd be happy to take some time to look into it myself.

Module are imported via XQueryContext.importModule. Right now this
method simply returns if a module is already registered for the
namespace.

We would probably just need to load the second module and merge it's
function and variable declarations into the already existing Module
instance (ExternalModuleImpl).

Wolfgang

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: Question about caching of indexes?

2009-12-02T08:30:14Z

Hi Wolfgang,

>
> Also, the cache manager may reset all caches to their minimum default
> if the db has been idle for a while.
>
> Wolfgang
>

I was wondering if this idle time is configurable, or where I may be able to
tweak the code to turn this off. I have a case where the application could
be idle for a while and cause a slow response while the cache repopulates.

Thanks!
gary

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: Multi-modules in one namespace not working.

2009-12-02T08:15:42Z

If anyone can give me a starting point in the code where the modules get loaded (import module ...), I'd be happy to take some time to look into it myself. I'm having trouble figuring out how eXist handles compiled .xq modules as opposed to pure Java modules at the API level.

Jason Smith
________________________________________
From: Jason Smith [jsmith@...]
Sent: Wednesday, December 02, 2009 8:16 AM
To: Leif-Jöran Olsson
Cc: exist-open@...
Subject: Re: [Exist-open] Multi-modules in one namespace not working.

Certainly! I'm glad to have someone look at it.

http://www.w3.org/TR/xquery/#doc-xquery-ModuleImport

It's pretty clearly supported by the syntax. I think.

The error occurs only because I attempt to run a function from the second module. If I don't attempt to call that function, no error occurs. eXist accepts the syntax perfectly well. It just doesn't load the functions from the second module.

Jason Smith
________________________________________
From: Leif-Jöran Olsson [ljo@...]
Sent: Wednesday, December 02, 2009 7:25 AM
To: Jason Smith
Cc: exist-open@...
Subject: Re: [Exist-open] Multi-modules in one namespace not working.

Den 2009-12-02 15:05, Jason Smith skrev:
> According to my reading of the XQuery 1.0 spec (which is always
> suspect), this should work.

Could you please give an url to the section you are reading?

>The exception I get looks like this:

>org.exist.xquery.XPathException: Function itg:fts() is not defined in
>namespace 'http://www.infotrustgroup.com/ccm/extensions' [at line 2,
>column 1]

And you mean you don't get this exception if you just specify either of
the modules with one module hint?

Cheers,
Leif-Jöran
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: namespace issues

2009-12-02T08:02:50Z

i don't think i stated my problem very well, let me try again.

my application starts with a page that lists all compays and all documents available with in each company. Each type of document (invoice, purchase order, packing slip, etc) will have its own namespace. This query will have to run across all documents and return the company and report name.

<root xmlns="http://SalesInvoice.mycompany.com">
<dh:docheader xmlns:dh="http://docheader.mycompany.com">
<company>280</company>
<report>invoice</report>
</docheader>
<morestuff>invoicedata</morestuff>
</root>

<root xmlns="http://PurchaseOrder.mycompany.com">
<dh:docheader xmlns:dh="http://docheader.mycompany.com">
<company>280</company>
<report>invoice</report>
</docheader>
<morestuff>invoicedata</morestuff>
</root>

<root xmlns="http://SalesInvoice.mycompany.com">
<dh:docheader xmlns:dh="http://docheader.mycompany.com">
<company>270</company>
<report>invoice</report>
</docheader>
<morestuff>invoicedata</morestuff>
</root>

what would be the most performant way to structure the document to be able to query all documents for company and report with the condition that each report type's root element will be in a different namespace?

On Dec 2, 2009 10:42am, Wolfgang Meier <wolfgang@...> wrote:

> > Thanks, that is what i thought. I need to be alble to query on company and
>
>
> > report_name across all documents. I was wondering from a performance
>
>
> > standpoint what is the best way to do that? I've got several ideas, but not
>
>
> > sure what would be the best way.
>
>
>
>
>
> Queries will be as fast with a namespace as they are without. Just
>
>
> using wildcards for the namespace prefix can cost performance for some
>
>
> types of expressions.
>
>
>
>
>
> > i could have a node with a common namespace across all documents
>
>
> > http://SalesInvoice.mycompany.com">
>
>
> > http://docheader.mycompany.com">
>
>
> > 280
>
>
> > invoice
>
>
> >
>
>
> > invoicedata
>
>
> >
>
>
> > but it sounds like that would be bad because i'd have a wildcard like
>
>
> > /*:root/dh:docheader/
>
>
>
>
>
> No, the wildcard is not necessary here. You can define an arbitrary
>
>
> prefix for for any namespace in your query. The prefix does not need
>
>
> to correspond to the prefix used in the document. For example:
>
>
>
>
>
> declare namespace dh="http://docheader.mycompany.com";
>
>
> declare namespace invoice="http://SalesInvoice.mycompany.com";
>
>
>
>
>
> /invoice:root/dh:docheader
>
>
>
>
>
> will work for above document.
>
>
>
>
>
> Wolfgang
>
>
>

Re: namespace issues

2009-12-02T07:42:58Z

> Thanks, that is what i thought. I need to be alble to query on company and
> report_name across all documents. I was wondering from a performance
> standpoint what is the best way to do that? I've got several ideas, but not
> sure what would be the best way.

Queries will be as fast with a namespace as they are without. Just
using wildcards for the namespace prefix can cost performance for some
types of expressions.

> i could have a node with a common namespace across all documents
> <root xmlns="http://SalesInvoice.mycompany.com">
> <dh:docheader xmlns:dh="http://docheader.mycompany.com">
> <company>280</company>
> <report>invoice</report>
> </docheader>
> <morestuff>invoicedata</morestuff>
> </root>
> but it sounds like that would be bad because i'd have a wildcard like
> /*:root/dh:docheader/

No, the wildcard is not necessary here. You can define an arbitrary
prefix for for any namespace in your query. The prefix does not need
to correspond to the prefix used in the document. For example:

declare namespace dh="http://docheader.mycompany.com";
declare namespace invoice="http://SalesInvoice.mycompany.com";

/invoice:root/dh:docheader

will work for above document.

Wolfgang

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open