Re: [Exist-open] Programmatically call the view.xql module

[Alasdair D. <ala...@gm...>]

Hi Dannes,

Thanks for the reply.

An update for you and anyone else interested.

I have dropped the idea, due to the tricky nature of getting things to work
as a trigger.  As I have already done the development work and it generates
the appropriate webpages, I am resigned to running a xquery script that
locates all recipe documents created after a given date and writes out the
CURL command to create the web page and saves it as a text file.

So, I don't need to reach into the structured filestore of eXist, and
simply can run an 'all documents' command if ever I need to
generate updated web pages.  Also, if the 'page' file is not found, Nginx
proxypass will simply call the eXist-db web server to get the dynamic page.

Alasdair


On Sat, Nov 28, 2020 at 11:11 PM Dannes Wessels <da...@ex...> wrote:

> Hi,
>
> On 25 Nov 2020, at 23:48 , Alasdair Dougall <ala...@gm...>
> wrote:
>
> As I have moved to Nginx, I am now using the try_files option before going
> to eXist to render the page. It is very quick to return the page.  So, if a
> new recipe is added that has not had the static part generated, eXists
> takes care of it without a single issue.
>
>
> “try_files” … does this mean that you refer directly to the files visible
> in webapp/WEB-INF/data/ ?
> I guess that is attractive but also tricky. In eXist-db 5.x this will not
> work anymore as we found this direct access too risky (and we needed to
> have additional features like deduplication)
>
> regards
> Dannes
>
>
>
> eXist-db Native XML Database
> http://www.exist-db.org
>
>