Hi For the start can try the non persistent scheduler setting first. Which the settings are read from the TR.props. Like this you would not neeed to test it against the database first.
How come nobody pointing this out ? *scratch* Regards ========== Ian Lim email: [EMAIL PROTECTED] homepage: http://www.webappcabaret.com/mallim ----- Original Message ----- From: "Ian Huynh" <[EMAIL PROTECTED]> To: "Turbine Users List" <[EMAIL PROTECTED]> Sent: Saturday, December 15, 2001 02:45 AM Subject: RE: Scheduler service > We are using Turbine Scheduler Service as a stand-alone app > embedded inside our WEB app. > > It took a bit of reading but I finally got it figured out > > 1. Download and install the TDK > 2. Make sure that you have the required jar file in your class path > To find out which jar file you needed, you also need to download the source code > and read through the build instructions. Somewhere in there it tells you the minimum required > jar files you needed. > > 3. Depending what DB u are using, select the correct link from this page and follow the instructions > http://jakarta.apache.org/turbine/turbine-2/services.html > > Note here that unless you are planning to rebuild the source code , the default > scheme for Scheduler Service is to use IDBroker when it creates entries in > the TURBINE_SCHEDULED_JOB table. > > 4. Read this link on how to setup your Scheduler Service > > http://jakarta.apache.org/turbine/turbine-2/services/scheduler-service.html > > 5. Next u need to decide how u want to bootstrap turbine during startup. We chose to > follow J2EE pattern and use startup-servlet to bootstrap and initialize Turbine , since we > already have a servlet that did a number of other startup tasks, we just added Turbine > into the list. But here's the jist. See the link below. > > http://jakarta.apache.org/turbine/turbine-2/getting-started.html > > 6. Next you need to write your own handler class and submit your class name into Turbine. > Note that your package name for the handler class needs to have a qualifier in there called > "scheduledjobs" . eg. com.mycompany.jobs.scheduledjobs.MyHandlerClassName > > THen you need to edit TurbineResource.properties (i belieive it's the modules.package entry) > to include the package qualifer (com.mycompany.jobs <<-- NOTE : exclude the scheduledjobs level ) > > Hope that helps u get started. It took a while for me to get it to work. But those were the > major stumbling blocks > > -----Original Message----- > From: Leandro Rodrigo Saad Cruz [mailto:[EMAIL PROTECTED]] > Sent: Wed 12/12/2001 4:52 AM > To: Turbine Users List > Cc: > Subject: Re: Scheduler service > > > > If you want to use the scheduler only by itself you should use fulcrum. > fulcrum is the service framework extractedc (and decoupled) from turbine > 2.1 > > > On Wed, 2001-12-12 at 08:51, Kazandjian Erik wrote: > > Hello, > > > > I'm completely new (and therefor lost) in turbine. What I would like to do > > is the following. I would like to use the scheduler-service in a J2EE > > application server. Can anyone give me a hint what I should install and how > > to proceed ? > > > > Thanks in advance > > > > Erik > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- > Leandro Rodrigo Saad Cruz > IT - Inter Business Tecnologia e Servicos (IB) > http://www.ibnetwork.com.br > > > -- > 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]>
