cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <>
Subject Re: Is it a bug in the cron block?
Date Thu, 24 Feb 2005 16:50:05 GMT
Frank Rennekamp wrote:
> I tried to use the cron block and found some difficulties. Before I
> forget it, I'm working with cocoon 2.1.6, java SDK 1.4.2, tomcat 5.0.28
> and linux (debian).
> Activating the cron block with standard values in the cocoon.xconf
> worked fine. 
> But I wanted to save the cron jobs in a database, so I made one change
> in the configuration and was using the JobStore 'tx':
>       <store type="tx"
> delegate="org.quartz.impl.jdbcjobstore.HSQLDBDelegate">
>         <datasource provider="jndi">jdbc/personnel</datasource>

There is also provider="excalibur".

>       </store>
> (By the way, the only documentation found here was:'tx' and 'cmt' stores
> require datasource configuration. Attributes delegate and provider are
> optional. Not very helpfull, and which database structure do I have to
> use? In the end I found this information on the quatz-scheduler
> homepage, but it would be nice to bundle this with the cron block)

Send in a patch to the documentation / configuration file, via BugZilla.

> First I hoped I could use the datasource defined in the cocoon.xconf,
> but I didn't find a solution.

See provider "excalibur" above.

> So I had to configure the same datasource again, this time for use as
> JNDI Datasource.


> I don't know enough about JNDI to tell if this is a bug or if this is
> just a house made problem. Can anyone tell me?

It is a house made problem. You used wrong JNDI URL, in your case it should be:



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message