geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Neal Sanche <>
Subject Re: GBeans representing separately persistent data
Date Mon, 12 Jun 2006 03:23:14 GMT
Personally I like the idea presented here, Aaron. J2EE doesn't have a 
nice way to schedule things, so you end up having to add something on to 
do it. I've been fortunate to have applications that didn't need to 
schedule much, and when I did, all I really needed was something to wake 
up every once in a while and see what needs to be done.

I can certainly see the usefulness of a simple 'cron' statement. Having 
spent most of the weekend trying to get a simple GBean thread to fire 
messages to an MDB to do extremely simple timed pulses, I can see the 
utility of having this.



Aaron Mulder wrote:
> I'm more looking at the case of an application that needs to run a
> daily import, daily export, and monthly report.  Who wants to learn a
> new set of admin tools just for that?  Instead of fooling with
> specialized tools, just put your job classes in a JAR and deploy that
> JAR along with the rest of your application.  Voila!  Scheduled jobs.
> If you update the jobs, you can redeploy them just like any other
> code.
> Thanks,
>    Aaron
> <jobs xmlns="">
>    <environment xmlns="">
>        <moduleId>
>            <artifactId>TestJobs</artifactId>
>        </moduleId>
>    </environment>
>    <job>
>        <job-name>Frequent Job</job-name>
>        <job-class></job-class>
>        <cron-expression>0/15 * * * * ?</cron-expression>
>    </job>
>    <job>
>        <job-name>Uncommon Job</job-name>
>        <job-class></job-class>
>        <cron-expression>0 10 10 * * ?</cron-expression>
>    </job>
> </jobs>

View raw message