I don't find it as clean as you do for the simple reason that it's
yet one more moving part I have to deploy and test. It's yet one more thing
a potential client could forget about, and it's yet one more thing I have to
educate my support folks on.
"Ok, so, lets learn a little about the crontab file ..."
<Blank looks>.
"It's a file, you know, that tells the cron daemon when to run
certain tasks..."
<blank looks>.
"So you've heard of this thing called cron, right?"
<nervous coughs>.
"Cron, Chronous, timing... none of this rings a bell?"
It usually goes downhill from there.
If it's just on one of my own servers that I'm going to manage,
sure, cron, while not optimal in my mind, is fine. As soon as I have to
actually deploy my application though, I want *everything* inside that war
file. I want the war to unpack and for it to just work. If my installation
doc includes sections on editing the crontab file, I may as well just send a
technician out to do the install because 80% of the customer base is going
to either do it wrong or get so baffled they call support rather than try it
themselves :).
--- Pat
> I actually find the cron job separation quite clean and reasonable.
> Die hard Java developers get stuck in the rut of thinking every
> solution must run within a JVM. The operating system has a built-in
> facility to run jobs, so it seems foolish to dismiss it and only seek
> solutions that fit within the confines of a JVM.
>
> I want a nightly job to rebuild some caches, nothing wrong with cron
> running it.
>
> RoR has a very nice "script/runner" facility to run code within a
> selected environment (production, test, development, or custom ones
> you create). Firing up a cron job to do a task is as easy as coding
> the task, which for cache rebuilding may only be 5 lines or less, and
> then adding one entry to the cron jobs. You can't touch that level
> of cleanliness, succinctness, or productiveness with *any* Java
> scheduling solution.
>
> Erik
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
