Quartz 2.0 Beta1: XML validation is failed with job_scheduling_data_2_0.xsd

581 views
Skip to first unread message

Geng Jinhao

unread,
Oct 27, 2011, 3:31:44 AM10/27/11
to Quartz.NET
I tried Quartz with v2.0 Beta 1 version, but found that the XML
configuration "quartz_sample.xml" can not pass the validation with
job_scheduling_data_2_0.xsd.
Could somebody help to confirm if it is a bug?
You can find these files under "doc\xml".
thanks!

Annie Tsai

unread,
Nov 3, 2011, 5:53:20 PM11/3/11
to Quartz.NET
I have the same issue too. Is the following your error message?

"Quartz.Xml.ValidationException: the 'http://quartznet.sourceforge.net/
JobSchedulingData:quartz' element is not declared" ?

Geng Jinhao

unread,
Nov 7, 2011, 8:30:48 PM11/7/11
to Quartz.NET
Yep. It prompts that quartz element is not declared.
> > thanks!- Hide quoted text -
>
> - Show quoted text -

Annie Tsai

unread,
Nov 9, 2011, 8:59:58 PM11/9/11
to Quartz.NET
Hi Geng,

the XML included in the xml is not updated. Here's an example of the
working one if you need one:

<job-scheduling-data
xmlns="http://quartznet.sourceforge.net/JobSchedulingData"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0">

<processing-directives>
<overwrite-existing-data>true</overwrite-existing-data>
</processing-directives>

<schedule>
<job>
<name>jobName1</name>
<group>jobGroup1</group>
<job-type>MasterSchedulerJobs.TestJob1, MasterSchedulerJobs</job-
type>
<durable>true</durable>
<recover>false</recover>
</job>
<trigger>
<cron>
<name>testTrigger1</name>
<group>group1</group>
<job-name>jobName1</job-name>
<job-group>jobGroup1</job-group>
<cron-expression>0/5 * * ? * MON-FRI</cron-expression>
</cron>
</trigger>
<job>
<name>jobName2</name>
<group>jobGroup2</group>
<job-type>MasterSchedulerJobs.TestJob2, MasterSchedulerJobs</job-
type>
<durable>true</durable>
<recover>false</recover>
</job>
<trigger>
<cron>
<name>testTrigger2</name>
<group>group2</group>
<job-name>jobName2</job-name>
<job-group>jobGroup2</job-group>
<cron-expression>0/5 * * ? * MON-FRI</cron-expression>
</cron>
</trigger>
</schedule>
</job-scheduling-data>
Reply all
Reply to author
Forward
0 new messages