exist-development — eXist Developer's List

Re: [Exist-development] Communication channels

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

> Wolfgang - I'm unable to use IRC at work, so you won't see me on IRC
> often.  But I mostly use the mailing list anyway, which I assume is
> still an equally preferred means of communicating?

Absolutely. The mailing list is the preferred communication medium and
should be used for all serious discussions. But it's certainly nice to
have a quick chat now and then or ask a quick question to a particular
person. IRC is ideal for this. It is quick, but if you miss anything,
you can read it up in the transcript.

Wolfgang

Re: [Exist-development] Communication channels

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

Dannes & other Mac OS X folks,

> In Adium (beta only?) i am able to connect to IRC as well. So.. count me in

I haven't used Adium's IRC support - I guess it's beta only at this
point.  But the IRC client I have used on OS X is Colloquy -
http://colloquy.info/.  They have an iPhone app too ($1.99).

Wolfgang - I'm unable to use IRC at work, so you won't see me on IRC
often.  But I mostly use the mailing list anyway, which I assume is
still an equally preferred means of communicating?

Joe

Re: [Exist-development] Communication channels

[Leif-Jöran O. <lj...@ex...>]

Den 2010-04-15 17:52, Dannes Wessels skrev:
> Hi,
> 
> On 15 Apr 2010, at 16:21 , Wolfgang Meier wrote:
> 
>> I would thus like to encourage all developers to drop gtalk
>> communications and again use the IRC channel
>> if you want to discuss or ask something which is not of a
>> strictly private nature.

Yes, I agree to stick to the irc for non-privacy needing issues.

Re: [Exist-development] Communication channels

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

Hi,

On 15 Apr 2010, at 16:21 , Wolfgang Meier wrote:

> I would thus like to encourage all developers to drop gtalk communications and again use the IRC channel
> if you want to discuss or ask something which is not of a strictly private nature.

In Adium (beta only?) i am able to connect to IRC as well. So.. count me in :-)

Kind regards

Dannes

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

Re: [Exist-development] Ideas for Exist

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

Hi Tony,

I think your email got through to the list. I guess we were all just
busy coding on other things.
I'll try to comment on some ideas at least and maybe someone else
wants to jump in as well. I would certainly like to encourage you to
realize some of those ideas.

> I think it could help Exist to put some high-profile examples of success
> stories “in the wild”.
>
> Companies Using Exist

We used to have a "powered by eXist" page for a long time, but there
were several problems with it. Just to mention the most important
ones:

* the list has to be maintained and users need to be constantly
encouraged to add and update their data. Our old list had too many
dead links.

* in most cases, we do not really know what people are using eXist
for. All we see is the questions they ask on the mailing list and we
can only guess what they are doing. Most people even use anonymous
addresses.

* unless you invest a lot of time into it, it is usually hard to get
any references from the bigger, commercial users. Many companies do
not want to disclose their use of open source software or every public
reference has to be approved at higher levels in the hierarchy. This
requires many emails or phone calls, for which we do not have the
time. I just heard from one company which deployed eXist on some 2.500
service laptops, but you'll probably have a hard time to get an
official statement about that ;-)

We thus decided to deactivate the page for now. We would need some
kind of dedicated "marketing person" to hunt for references.
Personally, this is too much for me.

> Exist Apps (sub-projects)
>
> I have tons of ideas for this!
>
> I think eXist could be seen as a platform in and of itself for developing
> all sorts of things traditionally done with other tools. If we were to get
> the ball rolling and start some basic “sub projects” that are essentially
> pre-configured apps for Exist, I think it could go a long way towards
> lowering the barrier of adoption for anybody on the fence.

Agreed. One of the core topics we identified during our user meeting
in Prague was the need for an easy packaging and deployment mechanism,
which would allow users to create and distribute small plugins as well
as entire applications in a well-defined format. Think of it as an
"app store" where you download a self-contained package and drop it
into your own repository. eXist would take care of the deployment,
configuration and initialization.

We could also provide tools for users to auto-generate the necessary
code skeleton to get started with their own apps.

> Wiki (AtomicWiki)
>
> We actaully already have the first Exist App underway! The AtomicWiki is
> great example of how you can build a very useful tool for collaboration
> using Exist.

AtomicWiki is a personal hobby project. I have a lot of pending
changes but never find the time to complete them and make a second
release :-) Maybe I should reserve half a day per week during the next
months to work on the rough edges.

> Bug Tracker
>
> This is something I've wanted to do for a long time: a custom bug tracker.

Yes. It would certainly be a great demo, even if you never finished it ;-)

> Academic Documents (LaTeX/LaTeXML, BibTeX/BibTeXML)
>
> There's lots of academic whitepapers out there, and it would be pretty cool
> if researchers had an easy-to-use, customizable tool for trackin them all.
>
> Referencing existing documents could be tracked using BibTeXML. Feeds could
> even be generated, allowing researchers to have an always-up-to-date list of
> their publications.

I think the primary standard format for bibliographic references in
XML today is MODS. I recently did a complete rewrite of eXist's MODS
interface. The idea was to reuse this as a basis for further
customizations or extensions:

http://demo.exist-db.org/exist/biblio/index.xml

It would be rather easy to integrate full texts into this. What's
missing is a facility to import and index binary resources (including
LaTeX docs).

> eBooks Library
>
> I have to say, I'm getting pretty excited about the rising interest in
> eBooks lately. I hate lugging my textbooks around for classes, and I have
> always found it more mentally exhausting reading a physical book instead of
> a screen.

I know several people on this list use XQuery to generate ePub from
TEI or docbook documents stored in eXist.

Wolfgang

Re: [Exist-development] Communication channels

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

sounds good to me

J

On Thu, Apr 15, 2010 at 4:21 PM, Wolfgang Meier <wol...@ex...> wrote:
> Hi guys,
>
> in the past we had quite an active community in IRC. This worked well.
> Most development discussions were public and could be followed by
> interested users. Unfortunately, service likes gtalk or jabber have
> made communication much more difficult. I often need to copy and paste
> text because person A asks a question in channel X which I forward to
> person B in channel Y and copy the answer back to A. This is annoying
> and doesn't help to build up a community.
>
> At the same time, people visiting the irc channel get the impression
> that the project is inactive. We should thus either close down the
> channel - or reanimate it. I would thus like to encourage all
> developers to drop gtalk communications and again use the IRC channel
> if you want to discuss or ask something which is not of a strictly
> private nature.
>
> Wolfgang
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>

[Exist-development] Communication channels

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

Hi guys,

in the past we had quite an active community in IRC. This worked well.
Most development discussions were public and could be followed by
interested users. Unfortunately, service likes gtalk or jabber have
made communication much more difficult. I often need to copy and paste
text because person A asks a question in channel X which I forward to
person B in channel Y and copy the answer back to A. This is annoying
and doesn't help to build up a community.

At the same time, people visiting the irc channel get the impression
that the project is inactive. We should thus either close down the
channel - or reanimate it. I would thus like to encourage all
developers to drop gtalk communications and again use the IRC channel
if you want to discuss or ask something which is not of a strictly
private nature.

Wolfgang

Re: [Exist-development] get data from DBF

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

On Thu, 2010-04-15 at 14:38 +0400, Evgeny Gazdovsky wrote:
> Hello!
> 
> Are anybody recomned open source xBase (DBF) JDBC Driver
> to use with eXist's SQL module? Can't find.
> 
> Or is better implement DBF module to read DBF directly?
> I'd found a couple of free libs.
> One of them http://sourceforge.net/projects/dans-dbf-lib (LGPL)
> 
> Will the module usefull for any except me.
> Just I use java binding.

I have several project that use dbf as store back-end. But I'm not sure
that this will be useful ...

-- 
Cheers,

Dmitriy Shabanov

PS you should know 1C ...

[Exist-development] get data from DBF

[Evgeny G. <gaz...@gm...>]

Hello!

Are anybody recomned open source xBase (DBF) JDBC Driver
to use with eXist's SQL module? Can't find.

Or is better implement DBF module to read DBF directly?
I'd found a couple of free libs.
One of them http://sourceforge.net/projects/dans-dbf-lib (LGPL)

Will the module usefull for any except me.
Just I use java binding.

---------
Evgeny

Re: [Exist-development] Enhancements to the configuration documentation

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

On 14 April 2010 17:16, Loren Cahlander <lor...@gm...> wrote:

> Hello folks,
>
> I have been working on enhancing the configuration documentation for eXist
> on trunk (Courtesy of the U.S. Department of State).  It is in an interim
> state, but I would like some feedback.
>
>

Hello Loren,

a few observations/suggestions:

* I think we should roll all the extension configurations into a single page
and make sure its called something like 'extension-configuration.xml'  or
perhaps better, merge/replace existing extensions.xml page ... when someone
is seeking docs they don't want to go to several places to get a complete
picture of things

* could replace Introduction/Glossary with a brief Overview of each
configuration ... these need writing ... if I have a moment between xproc
dev to do will contribute

otherwise this is yet again another real contribution, excellent start.

J

[Exist-development] Releasing 1.4.1

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

In Alistair's thread in exist-open, Wolfgang wrote:

> I see it's time to release 1.4.1. Guys, please port all your critical
> fixes to 1.4.x so we can get this finished.

Okay, I've just finished porting my changes to 1.4.x.

Joe

[Exist-development] Enhancements to the configuration documentation

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

Hello folks,

I have been working on enhancing the configuration documentation for eXist on trunk (Courtesy of the U.S. Department of State).  It is in an interim state, but I would like some feedback.

Please check out:

http://localhost:8080/exist/configuration.xml
http://localhost:8080/exist/config-cache.xml
http://localhost:8080/exist/config-compression.xml
http://localhost:8080/exist/config-context.xml
http://localhost:8080/exist/config-counter.xml
http://localhost:8080/exist/config-datetime.xml
http://localhost:8080/exist/config-example.xml
http://localhost:8080/exist/config-file.xml
http://localhost:8080/exist/config-fluent.xml
http://localhost:8080/exist/config-openid.xml
http://localhost:8080/exist/config-versioning.xml
http://localhost:8080/exist/config-xqdoc.xml
http://localhost:8080/exist/config-xslt.xml

I still have more to do, but am looking for feedback.  I will take all feedback and improve what I already have and port the enhanced documentation to the 1.4 branch on Sunday (Leaving out the new features like OpenID).

Loren

Re: [Exist-development] on NULL password authentication will allways fail

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

Note: it wasn't changed. It's in plan.

On Tue, Apr 13, 2010 at 11:26 AM, Dannes Wessels <da...@ex...>wrote:

> Hi,
>
> On Tue, Apr 13, 2010 at 4:51 AM, Dmitriy Shabanov <sha...@gm...>
> wrote:
> > On Mon, 2010-04-12 at 19:58 +0000, di...@us... wrote:
> >> Collection root = DatabaseManager.getCollection("xmldb:exist://" +
> >> DBBroker.ROOT_COLLECTION, "admin", null);
> >
> > You should not use null as password, use "". On null password account
> > will be blocked (for now it have workaround at password check time, but
> > I do want to change it after next release).
>
> Aha. Is this what we want? What is the rationale? Probably there is
> lot's of code relying on the NULL since that is what we use ourself in
> our test code and samples code.
> Any changes in this area could be a bit dangerous...... should be
> communicated very well. Since I was not aware of it -yet-,
> communication on this change is still required......
>
> (e.g. update of javadoc)
>
> cheers
>
> Dannes
>
>
>
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
>



-- 
Dmitriy Shabanov

Re: [Exist-development] on NULL password authentication will allways fail

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

Hi,

On Tue, Apr 13, 2010 at 4:51 AM, Dmitriy Shabanov <sha...@gm...> wrote:
> On Mon, 2010-04-12 at 19:58 +0000, di...@us... wrote:
>> Collection root = DatabaseManager.getCollection("xmldb:exist://" +
>> DBBroker.ROOT_COLLECTION, "admin", null);
>
> You should not use null as password, use "". On null password account
> will be blocked (for now it have workaround at password check time, but
> I do want to change it after next release).

Aha. Is this what we want? What is the rationale? Probably there is
lot's of code relying on the NULL since that is what we use ourself in
our test code and samples code.
Any changes in this area could be a bit dangerous...... should be
communicated very well. Since I was not aware of it -yet-,
communication on this change is still required......

(e.g. update of javadoc)

cheers

Dannes



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

Re: [Exist-development] Regression with authorization default user

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

org.exist.fluent tests all clean on my site.

IMHO, it should delete dbx files before testing.

On Mon, 2010-04-12 at 19:17 +0200, Dannes Wessels wrote:
> All,
> 
> since some time we have test issues in trunk. For some time I thought it was a build server issue, but now I am pretty sure. Please find attached the junit report with all extensions enabled.
> 
> Clearly, we have a problem with the default user authorization (see fluent tests, they used to work!). In my own tests, i have seen that 'guest' cannot write in many collections, at least not in the collections that were writable in the past. I think we have a serious regression here.
> please could you, e.g. Dmitriy, enable all indexes and extensions and run the junit test suite?
> 
> Kind regards
> 
> Dannes
> 
> some highlights from logging:
> 
> java.lang.NullPointerException
> 	at org.exist.security.XMLDBSecurityTest.setup(XMLDBSecurityTest.java:231)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 
> expected:<[admin]> but was:<[guest]>
> junit.framework.AssertionFailedError: expected:<[admin]> but was:<[guest]>
> at org.exist.fluent.MetadataTest.topFolderOwner(MetadataTest.java:105)
> 
> 
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
> 
> 
> 
> 
> 
> 
> 
> 
-- 
Cheers,

Dmitriy Shabanov

Re: [Exist-development] Regression with authorization default user

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

MetadataTest on clean database pass. Wonder, do we have some test that
change permission?

Can we have all tests enable on TC?

On Mon, 2010-04-12 at 19:17 +0200, Dannes Wessels wrote:
> All,
> 
> since some time we have test issues in trunk. For some time I thought it was a build server issue, but now I am pretty sure. Please find attached the junit report with all extensions enabled.
> 
> Clearly, we have a problem with the default user authorization (see fluent tests, they used to work!). In my own tests, i have seen that 'guest' cannot write in many collections, at least not in the collections that were writable in the past. I think we have a serious regression here.
> please could you, e.g. Dmitriy, enable all indexes and extensions and run the junit test suite?
> 
> Kind regards
> 
> Dannes
> 
> some highlights from logging:
> 
> java.lang.NullPointerException
> 	at org.exist.security.XMLDBSecurityTest.setup(XMLDBSecurityTest.java:231)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 
> expected:<[admin]> but was:<[guest]>
> junit.framework.AssertionFailedError: expected:<[admin]> but was:<[guest]>
> at org.exist.fluent.MetadataTest.topFolderOwner(MetadataTest.java:105)
> 
> 
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
> 
> 
> 
> 
> 
> 
> 
> 
-- 
Cheers,

Dmitriy Shabanov

[Exist-development] on NULL password authentication will allways fail

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

On Mon, 2010-04-12 at 19:58 +0000, di...@us... wrote:
> Collection root = DatabaseManager.getCollection("xmldb:exist://" +
> DBBroker.ROOT_COLLECTION, "admin", null);

You should not use null as password, use "". On null password account
will be blocked (for now it have workaround at password check time, but
I do want to change it after next release).

-- 
Cheers,

Dmitriy Shabanov

Re: [Exist-development] Regression with authorization default user

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

Hi,

On Mon, Apr 12, 2010 at 7:17 PM, Dannes Wessels <da...@ex...> wrote:
> please could you, e.g. Dmitriy, enable all indexes and extensions and run the junit test suite?

By disabling some tests (yups, some validation tests) the suite seems
to be running again. Still I am pretty sure that behaviour regarding
'guest' has been changed, since +- begin of march.

I'll investigate further tomorrow.

cheers

Dannes

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

[Exist-development] Regression with authorization default user

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

All,

since some time we have test issues in trunk. For some time I thought it was a build server issue, but now I am pretty sure. Please find attached the junit report with all extensions enabled.

Clearly, we have a problem with the default user authorization (see fluent tests, they used to work!). In my own tests, i have seen that 'guest' cannot write in many collections, at least not in the collections that were writable in the past. I think we have a serious regression here.

Re: [Exist-development] My apology

[Tony R. <to...@go...>]

On Apr 12, 2010, at 1:55 AM, Thomas White wrote:

> Dan,
>  
> There is no need for apology. What make a community alive and thriving is to have people with strong opinions and high conviction to their own ideas. I beg you not to try to please everybody, stick to your original plan and go for it!

Agreed!  :)

I don’t think you offended anyone, and you happen to prefer XQuery to XSLT.  It’s not the first time that a developer has a favorite tool—and the mailing list managed to discuss it without getting into a "holy war”! :)

What you have done is participate in a community.  That’s all.  

If you feel guilty for having an idea that is not shared by everyone else, then try and find an example of a community where every member thinks exactly the same.  

(Okay, let me limit that last statement to HUMAN communities.  Maybe ants and such can get away with it. :)

Gotta go, late to campus…arrgh!… 

—Tony

Re: [Exist-development] My apology

[Thomas W. <tho...@gm...>]

Dan,

There is no need for apology. What make a community alive and thriving is to
have people with strong opinions and high conviction to their own ideas. I
beg you not to try to please everybody, stick to your original plan and go
for it!

We all enjoyed your first chapter. What better study case for a book than
making the book itself.
I can't wait to read your next chapter.

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



On 12 April 2010 03:42, Dan McCreary <dan...@gm...> wrote:

> I believe I owe the eXist developer's group an apology.  I have not done a
> good job of communicating our design ideas and I hope I did not upset
> members of the team.  I will attempt to do better in the future.  And you
> have my sincere apology.
>
> My intent was not to imply that I had made any decision for the group, only
> for our pilot documentation project.  The decision to migrate away from XSLT
> to typeswitch-style XQuery for all the transforms is really my own personal
> opinion and may may be rejected by the group if the architecture does not
> stand on its own merits after the pilot is complete.  I will take personal
> responsibility to complete our architectural evaluation process and present
> the options to the group in a clear way with detailed analysis of the pros
> and cons of the options. Others on this list have already provided good
> input to these pro/con arguments.
>
> OK, now I must get back to writing my new test document: "A Beginner's
> Guide to Typeswitch Transforms with XQuery". :-O
>
> - Dan
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>

[Exist-development] My apology

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

I believe I owe the eXist developer's group an apology.  I have not done a
good job of communicating our design ideas and I hope I did not upset
members of the team.  I will attempt to do better in the future.  And you
have my sincere apology.

My intent was not to imply that I had made any decision for the group, only
for our pilot documentation project.  The decision to migrate away from XSLT
to typeswitch-style XQuery for all the transforms is really my own personal
opinion and may may be rejected by the group if the architecture does not
stand on its own merits after the pilot is complete.  I will take personal
responsibility to complete our architectural evaluation process and present
the options to the group in a clear way with detailed analysis of the pros
and cons of the options. Others on this list have already provided good
input to these pro/con arguments.

OK, now I must get back to writing my new test document: "A Beginner's Guide
to Typeswitch Transforms with XQuery". :-O

- Dan

Re: [Exist-development] New list member offering services :)

[Thomas W. <tho...@gm...>]

Tony,

Asking about what is better XQuery or XSLT is like asking which car is
better Ferrari or Bentley. The answer is: "It depends"!  What are you
looking for, how are going to use it, who are you going to use it with etc.

To me XSLT and XQuery in the XML world are like the left and the right hand
- some tasks are better, quicker and easier to reach when implemented with
XSLT and other are better, quicker and esier when written in XQuery. There
is never a simple "right" answer. Are you are writing one off
transformation? How often you are going to change it and the most important
question - which of these languages comes more natural to you and makes you
more productive.

I used to write almost everything in XSLT using XQiery just as a glue layer
between the requests, the database and the XSLT. Recently because of time
constraints I switched to XQuery completely and I am very pleased with the
quick results. I still use XSLT here and there and I am convinced XSLT is a
place to lay very good foundations for XQuery.

I think one of strengths of XSLT is its simple mechanism for extensibility
when using pattern matching. All you need to do is to add an include file
with additional pattens and you are done. You can repeat this as many times
as you need without ever changing the original XSLT file. You can even
generate a list of include files as you need them, even in run time. XSLT is
perfect for creating highly reusable libraries.

Using the typeswitch in XQuery  is completely the opposite. The only way to
extend the original functionality is to add MANUALLY all new cases into the
ORIGINAL file. When we work with predictable, stable, slow changing data,
like documentation XQuery it perfectly OK. But if you do data driven
applications there the code adapts to the data then XQuery is still behind
XSLT. Having said that I have to add that using util:function and util:call
can find same way around and mimic the XSLT way. My point is the
extensibility in XQuery does not come out of the box as with XSLT.

Switching same functionality from one language to another could be very
educational and brings a lot of fun. If somebody wants to toy with it and
there is a need I say why not, go for it. There is always room to make
things better, faster and easier to maintain.

I hope this helps.

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



On 9 April 2010 21:30, Wolfgang Meier <wol...@ex...> wrote:

> > I dont think that doing basic document to document conversion in
> > XQuery makes any sense, XSLT is easier to develop this in and more
> > intuitive.
>
> I think this is a misunderstanding. A simple document to document
> transformation can sometimes be even more intuitive in XQuery ;-) All
> you need to learn is typeswitch plus a few function calls. I'm using
> this more and more in my own code (for example, see
>
> http://exist.svn.sourceforge.net/viewvc/exist/trunk/eXist/webapp/biblio/jquery.xql?revision=11607&view=markup
> ).
> Done in the right way, the control flow in an XQuery can be easier to
> understand and maintain than the template matching mechanism of XSLT.
>
> Don't misunderstand me. I like XSLT. I use a pretty large XSLT to
> generate multi-volume, 1000 pages PDFs from a set of TEI documents
> stored in eXist. The processing only takes a few minutes, despite the
> thousands of small queries it sends to eXist, e.g. to assemble
> bibliographies and SVG graphics. However, this also shows the
> limitations of XSLT: it becomes quite tricky once you need to
> integrate data from many sources. Native XSLT support in eXist would
> overcome this limit. It's on the way, but there's still a lot of work
> left to be done.
>
> Anyway, my main argument for using more XQuery for the website is that
> you want to keep the examples as simple as possible and reduce the
> number of standards new users have to learn.
>
> Wolfgang
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>

Re: [Exist-development] demo.exist-db.org down?

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

> Yes, I'm currently updating it. I need to test out a few things. Thanks,

Oh, okay!  Just checking!  I see it's back up now.

By the way, it looks like the long "jar:file..." issue with
http://demo.exist-db.org/exist/functions/ is now fixed.  Not sure if
this was an intended part of your work, but I thought I'd mention it.

Thanks,
Joe

Re: [Exist-development] demo.exist-db.org down?

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

> FYI
>
> http://demo.exist-db.org/exist/

Yes, I'm currently updating it. I need to test out a few things. Thanks,

Wolfgang