Nabble - eXist

eXist + Groovy 1.5.6 + xmlrpc clash

2008-07-05T13:47:42Z

Hi, I'm just starting to get familiar with eXist. I have a project ahead where i can make good use of an XML database and so I started investigating. I want to load a 100.000 xml documents into the store for purpose of analysing. when using the ant tasks everything works fine.
I would like to use Groovy and the AntBuilder to setup my project solution. But here the problems start.
As soon as I start using Groovy and the AntBuilder there is a clash. The error message reads:
==================================
[store] Found 7 files.
[store] Storing applicationContext.xml ...
Caught: : java.lang.LinkageError: Class org/xml/sax/InputSource violates loader constraints
at exist1.run(exist1.groovy:14)
at exist1.main(exist1.groovy)
==================================
eXist has a dependency on xmlrpc-1.2-patched.jar and this is the offending guy - as far as I can say. I tried using different versions of xmlrpc, but that did not work. I also tried killing the InputSource from the jar - did not help either ( it could not find the xmlrpc any longer ).

The working ant build file is:
-----------------------------------------
<?xml version="1.0"?>
<project name="exist" default="x">
<path id="classpath.core">
<fileset dir="C:/Dokumente und Einstellungen/admin/.groovy/exist">
<include name="*.jar"/>
</fileset>
</path>

<typedef resource="org/exist/ant/antlib.xml" uri="http://exist-db.org/ant">
<classpath refid="classpath.core"/>
</typedef>

<target name="x">
<xdb:store xmlns:xdb="http://exist-db.org/ant" uri="xmldb:exist://localhost:8080/exist/xmlrpc/db/rl1" createcollection="true">
<fileset dir="C:/data/workspace/rloesche/svn-repository/developmentsupport/Technologie/xmls">
<include name="*.xml"/>
</fileset>
</xdb:store>
</target>
</project>
-------------------------------------------------------------------------

the Groovy file that does not work is: ( gives the error messge above )
-------------------------------------------------------------------------
// here are the source files to load
fns ='C:/data/workspace/rloesche/svn-repository/developmentsupport/Technologie/xmls'

// here are all the eXist jars
existpath ='C:/Dokumente und Einstellungen/admin/.groovy/exist'

def ant = new AntBuilder()
ant.taskdef( name:"store", classname:"org.exist.ant.XMLDBStoreTask"){
classpath{
fileset(dir:existpath,includes:"*.jar")
}
}

ant.store(uri:"xmldb:exist://localhost:8080/exist/xmlrpc/db/rl1", createcollection:"true"){
fileset(dir:fns){
include( name:"*.xml")
}
}
------------------------------------------------------------

mY environemtn is:

-Groovy 1.5.6
-Windows XP
-eXist: a current download as of today
-Java 1.5.0

I really would apreciate any help

regards

ralf

From forum: exist-open

Re: simple query not working

2008-07-04T12:12:26Z

Hi

On Fri, Jul 4, 2008 at 7:25 PM, Enric Jaen <enricjaen@...> wrote:
> I reinstalled eXist and now it works.

hmmm that really does make no sense :-)

regards

Dannes

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: simple query not working

2008-07-04T10:25:55Z

I reinstalled eXist and now it works.
Thanks to all who replied.
/Enric

----- Mensaje original ----
De: Enric Jaen <enricjaen@...>
Para: exist-open@...
Enviado: viernes, 4 de julio, 2008 18:49:55
Asunto: Re: simple query not working

I must have an installation problem because if I try the eXist's sandbox with
doc("http://www.functx.com/input/catalog.xml")//product it works,

but if I do the same query in my installed sandbox then it doesn't return nothing.

When I start up server it shows:

xerces-J 2.9.1
Saxon 9.1.0.1

So what is wrong with my installation?

/Enric

----- Mensaje original ----
De: Enric Jaen <enricjaen@...>
Para: exist-open@...
Enviado: viernes, 4 de julio, 2008 17:39:29
Asunto: Re: simple query not working

Sorry in my previous mail I missed a quote.

it's doc("hamlet.xml")//TITLE

but it doesn't work. So, what I am doing wrong?
I am quite confused.
/Enric

----- Mensaje original ----
De: Enric Jaen <enricjaen@...>
Para: exist-open@...
Enviado: viernes, 4 de julio, 2008 17:22:38
Asunto: simple query not working

Hi, I am testing the query panel of the client GUI. If I do
doc("hamlet.xml")//* it works OK, but

doc("hamlet.xml)//TITLE doesn't work. What I am doing wrong?
Thanks,
/E.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: simple query not working

2008-07-04T10:00:32Z

> doc("hamlet.xml)//TITLE doesn't work. What I am doing wrong?

Not sure what's wrong, but I would generally recommend to specify the
full path to the document with fn:doc(), e.g.
doc("/db/my/collection/hamlet.xml")//TITLE. Otherwise the path will be
interpreted relative to the current context collection and this may
change depending on how you call the query.

Wolfgang

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: simple query not working

2008-07-04T09:49:55Z

I must have an installation problem because if I try the eXist's sandbox with
doc("http://www.functx.com/input/catalog.xml")//product it works,

but if I do the same query in my installed sandbox then it doesn't return nothing.

When I start up server it shows:

xerces-J 2.9.1
Saxon 9.1.0.1

So what is wrong with my installation?

/Enric

----- Mensaje original ----
De: Enric Jaen <enricjaen@...>
Para: exist-open@...
Enviado: viernes, 4 de julio, 2008 17:39:29
Asunto: Re: simple query not working

Sorry in my previous mail I missed a quote.

it's doc("hamlet.xml")//TITLE

but it doesn't work. So, what I am doing wrong?
I am quite confused.
/Enric

----- Mensaje original ----
De: Enric Jaen <enricjaen@...>
Para: exist-open@...
Enviado: viernes, 4 de julio, 2008 17:22:38
Asunto: simple query not working

Hi, I am testing the query panel of the client GUI. If I do
doc("hamlet.xml")//* it works OK, but

doc("hamlet.xml)//TITLE doesn't work. What I am doing wrong?
Thanks,
/E.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: simple query not working

2008-07-04T08:39:29Z

Sorry in my previous mail I missed a quote.

it's doc("hamlet.xml")//TITLE

but it doesn't work. So, what I am doing wrong?
I am quite confused.
/Enric

----- Mensaje original ----
De: Enric Jaen <enricjaen@...>
Para: exist-open@...
Enviado: viernes, 4 de julio, 2008 17:22:38
Asunto: simple query not working

Hi, I am testing the query panel of the client GUI. If I do
doc("hamlet.xml")//* it works OK, but

doc("hamlet.xml)//TITLE doesn't work. What I am doing wrong?
Thanks,
/E.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

simple query not working

2008-07-04T08:22:38Z

Hi, I am testing the query panel of the client GUI. If I do
doc("hamlet.xml")//* it works OK, but

doc("hamlet.xml)//TITLE doesn't work. What I am doing wrong?
Thanks,
/E.

______________________________________________
Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: SOAP interface and Flex

2008-07-04T04:33:29Z

Thanks Roger for your response, I will answer to eXist list as well, maybe someone else would participate in the discussion or find the its content useful for himself.

I've tried REST API, Roger's suggestion with using CDATA is fine, but I've faced another problem: in Flex I can't send POST data in scalar format, and I need "key - value" format. Perl example in REST API documentation shows pushing xquery without a key.

Have You any idea how to solve the problem? Is there any parameter I could use as a key to make a pair?

I'm starting to believe that any solution of combining Flex with Exist does not exist.

Below I have an example of http service difinition in Flex:

    <mx:HTTPService
        id="exampleService"
        url="http://localhost:8080/exist/rest/db/"
        resultFormat="e4x"
        method="POST"
        contentType="application/xml"    (only this and application/x-www-form-urlencoded are allowed values)
        result="onExampleServiceResult(event)">
        <mx:request xmlns="">
            <exampleKey1>

example value, like xqery code

            </exampleKey1>
        </mx:request>
    </mx:HTTPService>

When I try to remove <exampleKey1> I get an error: Model 'request' contains only scalar content - this is currently unsupported.

This definition works fine (it's GET and doesn't need any parameters):

    <mx:HTTPService
        id="exampleService"
        url="http://localhost:8080/exist/rest/db/clients?_query={query}&_start=1&_howmany={howmany}"
        resultFormat="e4x"
        method="GET"
        result="onExampleServiceResult(event)"/>

Thanks in advance for any help,
Dominik Piekarczyk

On Wed, Jul 2, 2008 at 7:42 PM, Roger Espinosa <roger.espinosa@...> wrote:

How much control do you have in Flex for passing arguments? When constructing REST queries I tend to wrap the XQuery statements in a CDATA block so I don't have to do any encoding.

In your case,

<dateTime>{current-dateTime()}</dateTime>

would simply be

<dateTime>{curretn-dateTime()}</dateTime>

-R

--
--
Dominik Piekarczyk
www.araneo.pl
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: Web scraping with eXist: http vs. httpclient module?

2008-07-04T01:43:11Z

> Sure, I'm up for helping out with documentation. Wolfgang - do you
> have any needs?

Indeed, what eXist lacks most right now are some introductory articles,
which demonstrate from start to end how you develop an eXist-based
website. The existing documentation just describes all the various
interfaces, function modules, indexes and so on, but it does not really
explain how to put everything together.

The XQuery book already fills this gap by providing many well-explained
examples. It should be prominently linked from the eXist main site.
However, there should at least be one start-to-end tutorial which can be
shipped with eXist and which uses one example to explain the very basics
like: how to deploy an XQuery, how to import and use modules, how to
create the necessary indexes and load data, how to generate your HTML
from XQuery, and so on. But most important, it should help people to
understand the big picture, i.e. the "pure eXist/XQuery/XSLT approach".
Certainly, the article could be mirrored on the wiki book or vice versa.

> Also, I've thought of at some point documenting my TEI-based website,
> something like: building a TEI-based site with eXist. James Cummings
> wrote a nice paper for a conference in Kyoto, but I think the
> discussion of apache got in the way a bit of the elegance of a pure
> eXist/XQuery/XSLT approach.

Yes, TEI-based data could be a good starting point. We would also need
some data-centric queries to explain index configurations, but I think
this could be done with TEI as well.

Wolfgang

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: Web scraping with eXist: http vs. httpclient module?

2008-07-04T00:03:43Z

There is an example of using httpclient for page scraping in the
XQuery Wikibook

amongst other examples which use doc() on well-formed XML pages like those from Wikipedia.

I've been working on this book for a year or so now, and would welcome critique, suggestions for examples and contributions of examples. Scripts in the book are (mainly) executable on a server at my University. The book lacks document-centric examples, such as TEI and also needs some attention which I hope to give it this summer. It would be great to have extended articles on design and development such as the one you suggest.

Chris

Joe Wicentowski wrote:

Also, I've thought of at some point documenting my TEI-based website,
something like: building a TEI-based site with eXist.

From forum: exist-open

Re: Having problem indexing/uploading large xml document (450MB)

2008-07-03T23:30:58Z

Hi,

On Fri, Jul 4, 2008 at 8:30 AM, Dannes Wessels <dizzzz@...> wrote:
> You could register the DTD in the 'catalog.xml' ; other files should
> be resolved relative to this catalog.

or switch off validation in conf.xml ;

regards

Dannes

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: Having problem indexing/uploading large xml document (450MB)

2008-07-03T23:30:03Z

HI,

On Fri, Jul 4, 2008 at 4:09 AM, Felipe Hummel <felipehummel@...> wrote:
> It found something wrong in the dblp.dtd, but if I remove the DTD line from
> the dblp.xml, then I get this error:
>
>> Impossible to store a resource /home/felipehummel/workspace/dblp.xml:
>> fatal error at (18,20) : The entity "eacute" was referenced, but not
>> declared.

You could register the DTD in the 'catalog.xml' ; other files should
be resolved relative to this catalog.

regards

Dannes

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: util:import-module?

2008-07-03T23:13:03Z

Thank you Adam
Promise, I'll try to be better as fast as I can...
I am however still kind of stuck with this: I can't dynamically associate the prefix with the namespace.

In more detail:

I have one function that load the module in the prologue. It looks like:
declare function index:load-module()
{
util:import-module (xs:anyURI("http://www.e-Smile.org/header") ,"header", xs:anyURI("modules/header.xqm"))
};

In the body, there is a call to this function followed by a call to another function in the header.xqm module:
{index:load-module()}
{header:info-header()}

that return the error: "XPST0081: No namespace defined for prefix header"

Now, the function util:import-module seem to work. Or at least, it cries when I refer to a module that does not exist or have different namespace in the .xqm file and the first parameter.
I tried a lot of variants of this, again without success (have the header:info-header() in the index:load-module() function, load the module in the prologue without a function, insert the "util:import-module ..." statement in the body,...)

One strange thing though is that if I have an error in my index:load-module() function (e.g. refer to a .xqm file that does not exist), the error returned by the xquery is the same XPST0081: No namspace....
To make the problem with the index:load-module() appear (e.g. source for module modules/headerww.xqm not found in database), I first need to remove the line {header:info-header()} from the body

Sorry again if this is something stupid simple ...
Best regard
Christophe

Adam Retter-3 wrote:

Afraid so,

The hint is in the error message - xs:string is not a sub-type of
xs:anyURI - the function expects URI's for parameters 1 and 3 as
stated in the function documentation.

Try this instead -

et $a:=util:import-module (xs:anyURI("http://www.e-smile.org/header") ,"header",
xs:anyURI("modules/header.xqm"))

2008/7/3 geiser ch. <christophe.geiser@wfp.org>:
>
> Hi all
> I was looking for possibilities to be more dynamic in the way modules are
> loaded, and was happy to see that there was the util:import-module function
> for this.
> I am however unsuccessful in my attempts to run something basic (under
> version 1.2.0):
>
> (:Try to dynamicaly load modules:)
> let $a:=util:import-module ( "http://www.e-smile.org/header" ,"header",
> "modules/header.xqm")
>
> returns the error:
> Error checking function parameter 1 in call
> util:import-module(untyped-value-check[xs:anyURI,
> "http://www.e-smile.org/header"], "header", untyped-value-check[xs:anyURI,
> "modules/header.xqm"]): FORG0001: xs:string(http://www.e-smile.org/header)
> is not a sub-type of xs:anyURI [at line 89, column 9]
>
> As I new to eXist, there might be something stupid I am missing...
> Is there somebody who uses this function with success?
>
> Best regards
> Christophe

From forum: exist-open

Re: Having problem indexing/uploading large xml document (450MB)

2008-07-03T19:09:12Z

Hi, thanks for the anwsers.

I tried to upload dblp.xml through the java admin client (embedded mode), but I got this error:

Impossible to store a resource /home/felipehummel/workspace/dblp.xml: error at (4,74) : Attribute "mdate" must be declared for element type "incollection".

It found something wrong in the dblp.dtd, but if I remove the DTD line from the dblp.xml, then I get this error:

Impossible to store a resource /home/felipehummel/workspace/dblp.xml: fatal error at (18,20) : The entity "eacute" was referenced, but not declared.

Any suggestion?

Thank you

Felipe Hummel

On Thu, Jul 3, 2008 at 4:56 AM, Wolfgang Meier <wolfgang@...> wrote:

> Hi, I'm working with de DBLP xml dataset, which is about 450MB, I went to
> the admin section of eXist, then to the Browse Selection and tried to upload
> the document. It takes a few seconds, and then a blank page shows up with
> just the menu on the left side. The document was not uploaded and of course
> I can't query it.
> What's wrong?

450MB are a bit too much for uploading via web forms. I guess the web
server times out the request or runs out of memory.

Please use the Java admin client for jobs like this. For maximum
performance, you can launch the client in embedded mode, which saves
you the time for uploading the data.

To parse the DBLP fast enough, you should also increase cacheSize in
conf.xml, as well as provide a little more memory to Java. Please read
the following notes though:

http://atomic.exist-db.org/blogs/eXist/WarningBadMemory

Wolfgang

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

REST API: errors returned with incorrect content type

2008-07-03T17:45:14Z

When using the REST API, if the XQuery sent to eXist has a syntax error, eXist used to respond with some HTML that contains the error. I am happy to see that this was changed, and that now eXist just sends the error back as text. But, there is a problem: the content type is set to text/xml, while it should be set to something like text/plain.

The issue with this is that if the content type is text/xml, our code (in Orbeon Forms) tries to parse this as XML, chokes, and the error message is lost.

I am using the latest code in the 1.2.2 stable branch.

Alex

Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/

From forum: exist-open

Re: Web scraping with eXist: http vs. httpclient module?

2008-07-03T16:47:28Z

Sure, I'm up for helping out with documentation. Wolfgang - do you
have any needs?

Also, I've thought of at some point documenting my TEI-based website,
something like: building a TEI-based site with eXist. James Cummings
wrote a nice paper for a conference in Kyoto, but I think the
discussion of apache got in the way a bit of the elegance of a pure
eXist/XQuery/XSLT approach.

- Joe

On Mon, Jun 30, 2008 at 6:51 AM, Adam Retter <adam@...> wrote:

> Its actually the page on the eXist website that is out of date, im not
> sure why it wasnt updated when the last release went out...
>
> Help with documentation is always welcome, personally I would love to
> see a cookbook, a kind of set of pages about achieving different tasks
> with eXist - for example screen-scrapping some html ;-) However there
> may be more pressing documentation needs that perhaps Wolfgang or one
> of the other devs could suggest, if your up for it?
>
> Cheers Adam.

From forum: exist-open

Re: Preview: eXist-db 1.3.0dev

2008-07-03T12:52:14Z

We have switched both the test version of our application and the version supporting the XQuery Wikibook

http://en.wikibooks.org/wiki/XQuery

to 1.3dev. Performance is good and apart from a couple of bugs logged, it is working very well. The fix for temporary document fragments is particularly beneficial for scripts which are transforming and mashing data from other web pages or services, or perform two-pass analysis of data.

We have skipped 1.2 so this version is also fixing problems with function calls in modules. For me, the main work in the changeover has been caused by closer adherence to the XQuery standard, so that some previously implicit type conversions must now be explicit and type checking in function calls is more stringent.

One odd bug logged yesterday is that sessions appear not to be working - everything else can be worked around but that's a bit of a show-stopper.

Chris

From forum: exist-open

Re: util:import-module?

2008-07-03T05:09:43Z

Afraid so,

The hint is in the error message - xs:string is not a sub-type of
xs:anyURI - the function expects URI's for parameters 1 and 3 as
stated in the function documentation.

Try this instead -

et $a:=util:import-module (xs:anyURI("http://www.e-smile.org/header") ,"header",
xs:anyURI("modules/header.xqm"))

2008/7/3 geiser ch. <christophe.geiser@...>:

>
> Hi all
> I was looking for possibilities to be more dynamic in the way modules are
> loaded, and was happy to see that there was the util:import-module function
> for this.
> I am however unsuccessful in my attempts to run something basic (under
> version 1.2.0):
>
> (:Try to dynamicaly load modules:)
> let $a:=util:import-module ( "http://www.e-smile.org/header" ,"header",
> "modules/header.xqm")
>
> returns the error:
> Error checking function parameter 1 in call
> util:import-module(untyped-value-check[xs:anyURI,
> "http://www.e-smile.org/header"], "header", untyped-value-check[xs:anyURI,
> "modules/header.xqm"]): FORG0001: xs:string(http://www.e-smile.org/header)
> is not a sub-type of xs:anyURI [at line 89, column 9]
>
> As I new to eXist, there might be something stupid I am missing...
> Is there somebody who uses this function with success?
>
> Best regards
> Christophe
>
> --
> View this message in context: http://www.nabble.com/util%3Aimport-module--tp18256003p18256003.html
> Sent from the exist-open mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

--
Adam Retter

eXist Developer
{ England }
adam@...
irc://irc.freenode.net/existdb

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

util:import-module?

2008-07-03T03:21:20Z

Hi all
I was looking for possibilities to be more dynamic in the way modules are loaded, and was happy to see that there was the util:import-module function for this.
I am however unsuccessful in my attempts to run something basic (under version 1.2.0):

(:Try to dynamicaly load modules:)
let $a:=util:import-module ( "http://www.e-smile.org/header" ,"header", "modules/header.xqm")

returns the error:
Error checking function parameter 1 in call util:import-module(untyped-value-check[xs:anyURI, "http://www.e-smile.org/header"], "header", untyped-value-check[xs:anyURI, "modules/header.xqm"]): FORG0001: xs:string(http://www.e-smile.org/header) is not a sub-type of xs:anyURI [at line 89, column 9]

As I new to eXist, there might be something stupid I am missing...
Is there somebody who uses this function with success?

Best regards
Christophe

From forum: exist-open

Re: Having problem indexing/uploading large xml document (450MB)

2008-07-03T01:56:28Z

> Hi, I'm working with de DBLP xml dataset, which is about 450MB, I went to
> the admin section of eXist, then to the Browse Selection and tried to upload
> the document. It takes a few seconds, and then a blank page shows up with
> just the menu on the left side. The document was not uploaded and of course
> I can't query it.
> What's wrong?

450MB are a bit too much for uploading via web forms. I guess the web
server times out the request or runs out of memory.

Please use the Java admin client for jobs like this. For maximum
performance, you can launch the client in embedded mode, which saves
you the time for uploading the data.

To parse the DBLP fast enough, you should also increase cacheSize in
conf.xml, as well as provide a little more memory to Java. Please read
the following notes though:

http://atomic.exist-db.org/blogs/eXist/WarningBadMemory

Wolfgang

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: modeling challenges

2008-07-03T00:51:19Z

Christophe

Yes Will's articles are very useful. I often encounter the view that XML data is un-normalised (in the sense of non-redundant) which I assume is because they have seen data transport XML schemas where de-normalisation is common. Read-only XML documents often trade ease of navigation for document size and redundancy because the documents are not intended to be updatable. XML designed for data storage is quite different and should be designed to avoid redundancy in just the same way as a relational database. It seems to me that XML databases are easier to normalise because their non-first normal form structure allows those sneaky bits of denormalisation which occur with 1 to 1.0001 relationships can be represented properly without the pain of another table.

Will discusses the use of the XML schema constructs of key and keyref. These may be useful in a transport use case where the whole of a domain is represented and the task is to check that a generated XML document conforms to its schema before accepting the document. For XML databases they are less useful because they only work in document scope. If the XML database designer organises the logical data storage as files in collections, these constructs have the wrong scope; if she organises all data in a single document, the cost of revalidating the whole database every update would be prohibitive. Hence a rather unsatisfactory set of adhoc mechanisms seem to be used to check if not enforce integrity. eXIst supports triggers which are useful here but I'm ashamed to say I have not used myself.

Chris

geiser ch. wrote:

Hi Chris
Thanks a lot for sharing those thoughts, that is really helpful.
For those who - like me - lack experience in xml modeling, I also came across this article that helped me clarify some concepts:
http://www.xml.com/pub/a/2002/12/04/normalizing.html

Cheers
Christophe

From forum: exist-open

Re: Having problem indexing/uploading large xml document (450MB)

2008-07-02T22:00:04Z

Hi,

Felipe Hummel a écrit :

> Hi, I'm working with de DBLP xml dataset, which is about 450MB, I went
> to the admin section of eXist, then to the Browse Selection and tried to
> upload the document. It takes a few seconds, and then a blank page shows
> up with just the menu on the left side. The document was not uploaded
> and of course I can't query it.
> What's wrong?

See the logs : they should tell you what's going wrong. Possibly a
memory issue.

FYI : eXist's benchmark uses the DBLP without any problem.

Cheers,

p.b.

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: modeling challenges

2008-07-02T20:58:40Z

Hi Chris
Thanks a lot for sharing those thoughts, that is really helpful.
For those who - like me - lack experience in xml modeling, I also came across this article that helped me clarify some concepts:
http://www.xml.com/pub/a/2002/12/04/normalizing.html

Cheers
Christophe

Chris Wallace wrote:

Hi Christophe

These are all good questions. Here are a few thoughts gleaned from the past couple of years working on project which involves quite large number of schemas spanning the range from tabular to hierarchical structured data and teaching both Relational and XML databases. The application ( a faculty information system to support staff, students and administrators) is technically rather benign but is rich in data and needs to be very responsive to changed needs - an 'agile information system'.

I believe ER modelling is just as important for an XML database as it is for relational databases. That is conceptual ER modelling at a high enough level to abstract over the way relationships are implemented. A good tool should be able to generated either a relational model or a multiple-schema model although it would need some hinting. I haven't found such a tool although QSEE has some useful features. Largely I think of XML databases as object-oriented databases but with meaningful keys, no methods (namespaced functions have to do instead) and no inheritance.

The main difference is in the modelling of composition or whole part relationships with parent/child relationships rather than foreign keys, which is the only mechanism for implementing relationships in RDBMS. In my domain, composition relationships account for about 80% of relationships, hence a significant reduction in the database complexity. The remainder of the (associative) relationships have to be represented using foreign keys, and as in RDBMS, any shared data values are usable. However the ability to implement repeated elements in XML means that there is more flexibility in how one-many and especially many-many relationships are implemented. Rather than necessitating a link table, it is common to implement many-many relationships with repeated foreign keys on whichever side of the relationship is most salient - surprisingly often this is an easy decision and reflects the real-world ownership of the relationship. Often the relationships are structured or ordered on one side.

We also make use of repeated elements as primary keys - for example people are identified in our system by name (a key idea is to minimise the distance between real-world data and system data) , but they can have multiple names so people can add names, and promote one to be the preferred name but never 'change' name.

As far as integrity is concerned, I have a rather lax view. In my domain, the database is almost never consistent since changes are made to different entities at different times by different people. I want the database to help in the concurrent development of the content, and if this leads to inconsistencies which have to be analysed on demand, so be it - the web is never consistent either! So I concentrated on the definition of rules covering both simple integrity, business rules and data quality and analysis of the database.

Thanks for the thought-provoking question - I will try to distill my experience for an article in the wiki or elsewhere . I don't know about asset-oriented modelling and will take a look.

Chris Wallace
UWE Bristol

From forum: exist-open

Having problem indexing/uploading large xml document (450MB)

2008-07-02T18:37:09Z

Hi, I'm working with de DBLP xml dataset, which is about 450MB, I went to the admin section of eXist, then to the Browse Selection and tried to upload the document. It takes a few seconds, and then a blank page shows up with just the menu on the left side. The document was not uploaded and of course I can't query it.
What's wrong?

Another question I have, is not really about eXist, but I think someone here can anwser. I'm parsing this DBLP XML dataset (with 450MB) with the Xerces SAX Parser (java). The problem is i'm getting the 64000 entity expansion limit error, with the limit up to 100000 I still get the error, but when I raise the limit again to 150000 or more, the parser takes hours and doens't finish. I also tried to set FEATURE_SECURE_PROCESSING to false, so the parser stop worrying about entity limit, but it still takes hours to index. Anyone knows this problem?

Thanks

Felipe Hummel

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: Preview: eXist-db 1.3.0dev

2008-07-02T12:20:28Z

> Is this the same as what I saw in the 1.2 changelog, or something different?
>
> 7885 by wolfgang_m at 2008-06-19T15:10:48.345+01:00
>
> [performance] reduce memory consumption of in-memory documents constructed
> during a query. If you have a query which constructs thousands of small
> temporary XML fragments, each of those fragments will have its own document
> context...

No, that's not the same. The revision above was indeed ported back to
the eXist-stable-1.2 branch. It will be part of 1.2.4 (not 1.2.3). In
the meantime, you can check out the code from the branch, which is the
basis for all 1.2 releases:

http://exist.svn.sourceforge.net/viewvc/exist/branches/eXist-stable-1.2/

> In any case, for XQuery performance benchmarking would you recommend I use
> the latest snapshot (1.3.0dev)?

If you are querying in-memory XML fragments, then you should test with
1.3. Just watch out for log messages like:

02 Jul 2008 21:18:22,649 [main] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2192) - Stored: 174299:
/db/system/temp/08bbc50be05426c6cdf0a7deba8dba03.xml

If you see those, switching to 1.3 will give you performance benefits.

Wolfgang

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: Preview: eXist-db 1.3.0dev

2008-07-02T12:16:07Z

> Is this the same as what I saw in the 1.2 changelog, or something
> different?
>
> 7885 by wolfgang_m at 2008-06-19T15:10:48.345+01:00

After reading the changelog for 1.3 I see the there has been additional work
after 7885.

Sorry for the noise.
gary

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: Preview: eXist-db 1.3.0dev

2008-07-02T12:01:16Z

Hi,

> No, the temporary fragment issues required more than a fix, rather a
> redesign. I had to change the way in which the query engine handles
> in-memory XML nodes (for more info see:
> http://atomic.exist-db.org/blogs/eXist/InMemoryFragments).

Is this the same as what I saw in the 1.2 changelog, or something different?

7885 by wolfgang_m at 2008-06-19T15:10:48.345+01:00

[performance] reduce memory consumption of in-memory documents constructed
during a query. If you have a query which constructs thousands of small
temporary XML fragments, each of those fragments will have its own document
context...

In any case, for XQuery performance benchmarking would you recommend I use
the latest snapshot (1.3.0dev)?

Thanks! Sorry for my confusion.
gary

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: Preview: eXist-db 1.3.0dev

2008-07-02T11:40:42Z

>> releases. The main solved issue is the "temporary fragment" thingy.
>
> My understanding is that this fix was also ported back to version 1.2.3. Is
> that correct?

No, the temporary fragment issues required more than a fix, rather a
redesign. I had to change the way in which the query engine handles
in-memory XML nodes (for more info see:
http://atomic.exist-db.org/blogs/eXist/InMemoryFragments).

Porting those changes back to 1.2.3 would be possible, but still quite a
lot of work. I think we should rather put this work into testing and
stabilizing 1.3.

Wolfgang

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: Preview: eXist-db 1.3.0dev

2008-07-02T11:34:31Z

Hi Dannes,

> releases. The main solved issue is the "temporary fragment" thingy.

My understanding is that this fix was also ported back to version 1.2.3. Is
that correct?

Thanks,
Gary

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: modeling challenges

2008-07-02T11:18:31Z

Hi Christophe

These are all good questions. Here are a few thoughts gleaned from the past couple of years working on project which involves quite large number of schemas spanning the range from tabular to hierarchical structured data and teaching both Relational and XML databases. The application ( a faculty information system to support staff, students and administrators) is technically rather benign but is rich in data and needs to be very responsive to changed needs - an 'agile information system'.

I believe ER modelling is just as important for an XML database as it is for relational databases. That is conceptual ER modelling at a high enough level to abstract over the way relationships are implemented. A good tool should be able to generated either a relational model or a multiple-schema model although it would need some hinting. I haven't found such a tool although QSEE has some useful features. Largely I think of XML databases as object-oriented databases but with meaningful keys, no methods (namespaced functions have to do instead) and no inheritance.

The main difference is in the modelling of composition or whole part relationships with parent/child relationships rather than foreign keys, which is the only mechanism for implementing relationships in RDBMS. In my domain, composition relationships account for about 80% of relationships, hence a significant reduction in the database complexity. The remainder of the (associative) relationships have to be represented using foreign keys, and as in RDBMS, any shared data values are usable. However the ability to implement repeated elements in XML means that there is more flexibility in how one-many and especially many-many relationships are implemented. Rather than necessitating a link table, it is common to implement many-many relationships with repeated foreign keys on whichever side of the relationship is most salient - surprisingly often this is an easy decision and reflects the real-world ownership of the relationship. Often the relationships are structured or ordered on one side.

We also make use of repeated elements as primary keys - for example people are identified in our system by name (a key idea is to minimise the distance between real-world data and system data) , but they can have multiple names so people can add names, and promote one to be the preferred name but never 'change' name.

As far as integrity is concerned, I have a rather lax view. In my domain, the database is almost never consistent since changes are made to different entities at different times by different people. I want the database to help in the concurrent development of the content, and if this leads to inconsistencies which have to be analysed on demand, so be it - the web is never consistent either! So I concentrated on the definition of rules covering both simple integrity, business rules and data quality and analysis of the database.

Thanks for the thought-provoking question - I will try to distill my experience for an article in the wiki or elsewhere . I don't know about asset-oriented modelling and will take a look.

Chris Wallace
UWE Bristol

geiser ch. wrote:

Hi eXist universe
Coming from an SQL world where plenty of modeling tools exist, I kind of feel that I would need some advice on best modeling approach in an xml environment.
I am about to start building a new web-app and I would like to test the xforms/rest/xquery paradigm and therefore use eXist as a key piece for this. After some research on the web, I am still facing two main difficulties:
- I am still not really sure how to shift from the entity/relationship conceptual framework or how to make it properly fit in an xml hierarchical world. Also, though I see xml schema as a key building blocks in the modeling process, I wish I could stay at a higher conceptual level in the early phase of modeling. I came across the asset object modeling approach (http://www.aomodeling.org/KLEEN%20WhitePaper.pdf) which seems quite interesting in this case (though I could not make the tool work, and there does not seem to be any active user group). Does anybody uses a similar approach or could recommend one? I guess (hope?) I am not the only one experimenting this as a real challenge.
- This is more related to eXist. Is there any best practices or resources on how to structure the xml database re a model (e.g. what would make a good hierarchy of collection, how best to implement multiple relationship, how to enforce relational integrity,...). At this stage I am not so concerned with performance issues, but rather try to come up with a consistent development approach – it often pays off in the long run...
I know there is no simple answer to those questions, but any suggestion / recommendations would be welcome
Thank you
Christophe

From forum: exist-open

Preview: eXist-db 1.3.0dev

2008-07-02T11:18:10Z

All,

A few moments ago I have uploaded a new preview of our current trunk
(snapshot of development code) to http://www.exist-db.nl/files/ . This
release provides some significant changes compared to the 1.2.x
releases. The main solved issue is the "temporary fragment" thingy.

This snapshot contains a few significant performance improvements,
which are also part of the upcoming 1.2.4 release

for more details check the changelog.

As it is bleeding edge stuff, bugs and instabilities can be expected
(the disclaimer :-) ). You can help us to improve the release by
reporting issues (and success stories) on this MailingList.

On behalf of the development team

Dannes Wessels
dizzzz@...
http://exist-db.org

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open

From forum: exist-open

Re: SOAP interface and Flex

2008-07-02T07:52:59Z

Thanks for your answer, Adam. My reply's below:

Have you tried this with a really simple XQuery? e.g.

xquery version "1.0";

<dateTime>{current-dateTime()}</dateTime>

This is a smart idea, no data is included so I don't have to worry about data paths. But the result is the same, unfortunately. I've tried that date function and even just to push <a>b</a> to the client.

I would also recommend that you try this outside of Adobe Flex, do you
have something like Web Service Studio or oXygen (it has a Web Service
test tool). Try connecting to the service and sending your simple
query request from there, the nice thing about this is then that you
can see the SOAP Request and Response.

So I tried. I used SoapUI tool and I've sent some requests. The result is the more less the same: I can connect, get resource, but I still don't have satisfying response while sending xquery.

This is an example of request and response:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:exist">
   <soapenv:Header/>
   <soapenv:Body>
      <urn:xquery>
         <urn:sessionId>4630104</urn:sessionId>

<urn:xquery>eHF1ZXJ5IHZlcnNpb24gIjEuMCI7DQ08ZGF0ZVRpbWU+e2N1cnJlbnQtZGF0ZVRpbWUoKX08L2RhdGVUaW1lPg==</urn:xquery>

      </urn:xquery>
   </soapenv:Body>
</soapenv:Envelope>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <xqueryResponse xmlns="urn:exist">
         <xqueryReturn>
            <collections/>
            <hits>1</hits>
            <queryTime>0</queryTime>
         </xqueryReturn>
      </xqueryResponse>
   </soapenv:Body>
</soapenv:Envelope>

Is this what I was supposed to get as an answer? I expected rather current datetime, like in xquery sandbox. I've tried to broke the base64 data string and the server response with an exception. So it's good.

Also, you may find the REST interface easier than the SOAP interface.
With the REST interface you can GET for simple queries with a
querystring parameter _query or for more complex queries you can POST
an XQuery.

I will probably go to the REST interface. I preferred SOAP, it's much more elegant and handy in Flex.

There is also a SOAPServer in eXist which is different to the default
SOAP Webservices you are using, you can find details in
EXIST_HOME/tools/SOAPServer - this will enable you to write and store
xqueries in the database and expose them as SOAP Webservices.

I don't see it in my folder, but even if - I will rather use REST interface which is documented and I can count for some help from other developers.

Thanks Adam

Thanks Adam :)

Dominik

> Hi all.
>
> This is my first message to the list.
>
> First I'll introduce my idea:
>
> A few days ago I've found eXist to be just ideal combination with Flex and
> it's web services interface. Flex has great tools for working with XML data
> and (in small applications) communication with an XML DB via web services
> could allow me avoiding server side software - it's pretty much, I don't
> have to use yet another language like Java, PHP, and so on.
>
> BUT (the problem) :
>
> Well, I cannot get proper response from xquery operation. I really really
> tried to manage it in many ways.
>
> SOME FACTS:
>
> * xquery is the first web services' operation on my way that does not
> work. Some other do, like getVersion (here's the whole flex's web service
> definition):
>
> <mx:WebService
> wsdl="http://localhost:8080/exist/services/Version?wsdl"
> id="eXistVersionWS"
> result="queryWSResultHandler(event)"
> fault="queryWSFaultHandler(event)"
> useProxy="false">
> <mx:operation name="getVersion" />
> </mx:WebService>
>
> * Another working operations:
> <mx:operation name="connect"
> result="connectQueryWSResultHandler(event)">
> <mx:request xmlns="">
> <userId>admin</userId>
> <password>admin</password> (here I've changed password from
> default null)
> </mx:request>
> </mx:operation>
>
> <mx:operation name="disconnect">
> <mx:request xmlns="">
> <sessionId>{this.sessionId}</sessionId>
> </mx:request>
> </mx:operation>
>
> <mx:operation name="getResourceData">
> <mx:request xmlns="">
> <sessionId>{this.sessionId}</sessionId>
> <path>{inputReourcePath.text}</path>
> <indent>true</indent>
> <xinclude>false</xinclude>
> <processXSLPI>false</processXSLPI>
> </mx:request>
> </mx:operation>
>
> * And this is the problematic operation:
>
> <mx:operation name="xquery"
> result="xqueryQueryWSResultHandler(event)">
> <mx:request xmlns="">
> <sessionId>{this.sessionId}</sessionId>
> <xquery>{encodedInput.text}</xquery>
> </mx:request>
> </mx:operation>
>
> I've checked the request several times, it's encoded properly (I've
> decoded it to be sure), sessionId works fine with getResourceData operation,
> so it's fine. I always get the message:
>
> [RPC Fault faultString="HTTP request error"
> faultCode="Server.Error.Request" faultDetail="Error: [IOErrorEvent
> type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error
> #2032: Stream Error. URL: http://localhost:8080/exist/services/Query"]. URL:
> http://localhost:8080/exist/services/Query"]
>
>
> THE QUESTION(s):
>
> * Is it a problem with a query I'm sending? It's true that these are my
> first steps with xquery language, but I've tried sooo many examples from
> eXist resources and xquery sandbox that it's unlikely I couldn't just have
> one lucky shot :)
> * Could you give me some examples of <xquery> parameter that have to work
> (with existing default examples).
> * Do you see any other mistakes I could make?
> * Has anybody any experiences with combining Flex with such XML DBs? It
> seems to be so natural that it's just strange to me that I don't see any
> working examples.
>
>
>
> Help me, please, I'm stuck. But the idea is too elegant I would like to give
> up.
>
> Greetings
>
> --
> Dominik Piekarczyk
> www.araneo.pl

> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>

--
Adam Retter

eXist Developer
{ England }
adam@...
irc://irc.freenode.net/existdb

From forum: exist-open