Introduce abstraction over scheduling configuration

[GoogleCodeExporter]

Issue #2 describes an enhancement that - as a side effect - allows users 
to move job configuration out of the NCron.exe.config file. By introducing 
an abstraction over the schedule configuration, it would be possible to 
also allow users to move this part out of the XML file (the part that 
currently lives in the <plans> element).

The two enhancements, in combination, makes it possible to move all 
"business relevant configuration" to a separate configuration system. By 
allowing configuration to come from arbitrary file, network or database 
sources, it gets a lot easier to NCron with other systems.

Original issue reported on code.google.com by jsr%mala...@gtempaccount.com on 6 Jan 2010 at 2:27

[GoogleCodeExporter]

Original comment by jsr%mala...@gtempaccount.com on 7 Jan 2010 at 5:06

• Added labels: Component-Framework

[GoogleCodeExporter]

Original comment by jsr%mala...@gtempaccount.com on 17 Jan 2010 at 1:30

• Added labels: Priority-High
• Removed labels: Priority-Low

[GoogleCodeExporter]

Original comment by jsr%mala...@gtempaccount.com on 17 Jan 2010 at 4:54

• Changed state: Fixed

[GoogleCodeExporter]

Issue #13 has removed the entire configuration system, and there is no support 
for 
have scheduling configuration outside of the service application.

The functionality should be reimplemented in a way that allows registrations 
like:

service.AddScheduleSource(new SomeScheduleSourceImplementation());

Original comment by jsr%mala...@gtempaccount.com on 25 Jan 2010 at 9:42

• Changed state: Accepted

[GoogleCodeExporter]

Replaced by issue #14.

Original comment by jsr%mala...@gtempaccount.com on 26 Jan 2010 at 8:39

• Changed state: Fixed