JobData Serialization

[Keith]

It seems like it would be helpful for the serialization of the JobData
to use XML rather than binary. The reason is to promote using SQL
scripts to setup jobs in different environments (dev, test, prod).

[Marko Lahma]

Hi Keith,

I need to think about this. You can have the same thing with scheduler
initialization code / upcoming XML configuration, poking around with
the database isn't endorsed - you should use the API for accessing the
data.

-Marko

[Keith]

So what is the recommended way to migrate data from test to prod?
Doesn't seem to be production friendly if I can't script the
deployment. I guess I can write code to use the API to deploy to
production.

On Oct 2, 3:52 pm, "Marko Lahma" <marko.la...@gmail.com> wrote:
> Hi Keith,
>
> I need to think about this. You can have the same thing with scheduler
> initialization code / upcoming XML configuration, poking around with
> the database isn't endorsed - you should use the API for accessing the
> data.
>
> -Marko
>

> On 10/2/07, Keith <kfarr...@yahoo.com> wrote:
>
>
>
>
>
> > It seems like it would be helpful for the serialization of the JobData
> > to use XML rather than binary. The reason is to promote using SQL

> > scripts to setup jobs in different environments (dev, test, prod).- Hide quoted text -
>
> - Show quoted text -

[Marko Lahma]

For now its tedious API based deployment, I've already started work
with XML based configuration but it'll take some time as I'm knee-deep
in work right now.

Hopefully I have good news soon in this area.

Cheers,

-Marko

[Marko Lahma]

There's now initial version of XML job configuration support in trunk.
Example 15 with quartz_jobs.xml should give a clue how to use this. If
you Keith (and others of course) have time to give it a whirl and
report possible problems it would be nice.

-Marko