Just my two cents... XML sounds great. The file version has quite a few problems in it. (I think I sent a bug report on one of them). I am trying to figure out JUnit, and could maybe try to put some tests together for the scheduler.
Eric -----Original Message----- From: David Wynter [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 03, 2002 2:39 PM To: Turbine Users List Subject: RE: One Time run of Scheduler Job? Jason, I can probably only add those methods as I have time constraints to solve a problem with my application. While digging around thou I should be able to at least put together some notes to help towards the creation of a XML or properties file version. David -----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED]] Sent: 03 January 2002 19:29 To: Turbine Users List Subject: Re: One Time run of Scheduler Job? On 1/3/02 2:14 PM, "David Wynter" <[EMAIL PROTECTED]> wrote: > Mine usage is of the database Scheduler. Good point, I had not thought of > the file based version, I'll look into it tomorrow. I was just thinking if we were going to start afresh that it would be easier from an XML configuration or simple properties file. -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
