Re: [Exist-development] betterFORM integration issues

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

I just checked the latest betterform integration in trunk. It works
well out of the box. I also tried to migrate some of my own examples
and found a few issues. Most important, the XForms filter seems to be
applied *before* eXist's URL rewrite filter. I often use
XQueryURLRewrite to transform an XML document into HTML, which would
then contain XForms markup. The XForms filter should thus be applied
*after* the URL rewrite filter. I tried switching both and it seemed
to work - basically. However, the HTML was messed up when first
passing an XML through my docbook stylesheets. I need more time to see
what's wrong.

> 2. Is there any plan for a generic error-page? We have one that is
> implemented in xquery but that's specific for our needs (Though it
> should not be hard to adapt for the more generic case) and is
> configured via the standard <error-page> element in web.xml. This
> works for our eXist / betterFORM bundling but of course is not
> appropriate for integration in eXist as its now triggered for every
> error occuring in eXist.

I will add a feature to specify a generic error-page in the
controller.xql. This will allow different error handlers to be
configured for different directories/collections/requests.

Wolfgang