It just so happens that this particular implementation of a scheduler saves
the jobs to a database (which is a _good_ idea), and that it so happens that
Turbine uses Torque for most if not all of its object persistence to db.

I'm sure there are a couple of other schedulers out there which might be
easier to use...:)

Kelvin

----- Original Message -----
From: Kazandjian Erik <[EMAIL PROTECTED]>
To: 'Turbine Users List' <[EMAIL PROTECTED]>
Sent: Friday, December 14, 2001 8:44 PM
Subject: RE: Automatic creation of turbine_scheduled_job


> I do search the archives but I can't find an answer to my question. The
only
> thing I would like to do is use the scheduler service in another
application
> although everybody says this is trivial I don't see how it must be done.
Do
> I really have to go through all this torque-stuff to get the scheduler
> working. I though these components were there to make everything
> transparent.
>
> Erik
>
> -----Original Message-----
> From: Kelvin Tan [mailto:[EMAIL PROTECTED]]
> Sent: vrijdag 14 december 2001 12:34
> To: Turbine Users List
> Subject: Re: Automatic creation of turbine_scheduled_job
>
>
>
> ----- Original Message -----
> From: Kazandjian Erik <[EMAIL PROTECTED]>
> To: 'Turbine Users List' <[EMAIL PROTECTED]>
> Sent: Friday, December 14, 2001 3:50 PM
> Subject: RE: Automatic creation of turbine_scheduled_job
>
>
> > Can I you this on an existing database, will it add the table ?
> > Some more stupid questions : how can I increase logging, where do a
> specify
> > which database to connect, because now I copied the file
Torque.properties
> > and modiefied the URL for jdbs to my existing database but when I run
run
> > Torque.init(config_file) and ask for all my tables in the db I only get
> > ID_TABLE. Any suggestions. Is there some step bu step getting started
> > documentation ?
>
> Try
> http://www.mail-archive.com/[email protected]/msg03639.html
>
> Do search the archives before posting. Chances are, someone has asked the
> question you're asking before and has received an answer on that...:)
>
> Good luck
>
> Kelvin
>
> >
> >
> > Erik
> >
> > -----Original Message-----
> > From: Kelvin Tan [mailto:[EMAIL PROTECTED]]
> > Sent: vrijdag 14 december 2001 08:09
> > To: Turbine Users List
> > Subject: Re: Automatic creation of turbine_scheduled_job
> >
> >
> > Check the main directory for Fulcrum.
> >
> > There should be a scheduler-schema.xml file. Run torque using that file
as
> > your schema. That should do the trick. Alternatively, if you're already
> > using Torque, you can copy and paste the contents of
scheduler-schema.xml
> > into your existing schema file too.
> >
> > Kelvin
> >
> > ----- Original Message -----
> > From: Kazandjian Erik <[EMAIL PROTECTED]>
> > To: Turbine Users List (E-mail) <[EMAIL PROTECTED]>
> > Sent: Thursday, December 13, 2001 11:03 PM
> > Subject: Automatic creation of turbine_scheduled_job
> >
> >
> > > Hello,
> > >
> > > I finally managed to get fulcrum running. When I now want to use the
> > > scheduler service the program complains
> > >
> > >  ERROR:  Relation 'turbine_scheduled_job' does not exists.
> > >
> > > I could of course manually create this table in the database but isn't
> > there
> > > a way that torque does this automatically ?
> > >
> > > Erik
> > >
> > > --
> > > 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]>
> >
>
>
> --
> 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]>

Reply via email to