[SCHEDULER-245]  Simplify internal profile logic
Type Enhancement
Priority High
Severity Trivial
Component Dispatch Scheduler Engine
Fixed In Version [8.0] 8.0
Versions Affected [3.0.1, 3.0] 3.0 Hot Fix 1, 3.0
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 4/4/2015

Description 
Look at the way Profile items are handled in the VOEvent Receiver, including generation of the initial set of XML values. It is much simpler. Do this in the main dispatcher engine as well, simplifying things and reducing the places where defaults need to be set (and matched with each other).

Comments
4/5/2015 7:41:09 AM   Bob Denny 
Looking good. I now have it working the way I want for demo customers, broken license customers, and full ones. When it can't see profile info ("engine" section) it displays the Config window, which initialized the XML profile from the defaults in the config grid iself.
4/4/2015 9:38:41 PM   Bob Denny 
May be completed. Needs more test and review. Mainly for what happens if the XML is deleted and the demo period has expired. Chicken and egg?
4/4/2015 9:36:50 PM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

  Repository
  svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 

 

  SVN Revision
  573
 

 

  Affected files
  /trunk/Scheduler/ConfigForm.cs (Modified)
/trunk/Scheduler/Engine.cs (Modified)
/trunk/Scheduler/Scheduler.csproj.user (Modified)

 

 

  Check-in comment
  ==checkpoint== Simplify internal profile logic and defauting. Now show Config on first start. This is incompletely tested yet.
GEM:245
4/4/2015 8:40:21 PM   Bob Denny 
Yeah, I just wrestled with this one for several new properties. Do it.