15 Oct
2018
15 Oct
'18
3:38 p.m.
Hi Christian,
thank you as usual for your attention.
With standalone I mean basexhttp which is what we usually do. This time
we have requirement for running inside tomcat...
The jobs.xml file looks like:
<jobs>
<job id="startup">if (db:exists('onedb')) then () else
db:create('ondedb')</job>
</jobs>
but we have also tried with:
<jobs>
<job id="startup">admin:write-log(current-dateTime())</job>
</jobs>
which presents the exact same issues: basexhttp runs ok but
jobs:services() doesn't list them whereas tomcat doesn't run the scripts
but services are listed.
Thank you again,
Marco.
On 15/10/2018 15:25, Christian Grün wrote:
> Hi Marco,
>
> I see your question didn’t get an answer yet. Maybe we can first try
> to find out what Jetty does (or does not):
>
>> When running standalone with Jetty, the scripts are executed even if, in
>> this case, we are getting empty results when running jobs:services() in
>> the DBA after startup.
> Some questions back:
> 1. By 'standalone', do you mean that you are running 'basexhttp', or
> do you run Jetty and deploy BaseX as WAR file?
> 2. How does the jobs.xml file in the database directory look like?
>
> Cheers,
> Christian