It could be possible... the quartz library wants it's own database tables to use... but, if the scheduler object (the quartz JobStore) agrees with me serializing it (have not tested this yet), then it's entirely possible that object could be saved on the server via Private Data Store... but, this would essentially be the same as storing it in the users %APPDATA% directory... basically a file (the serialized object) written to disk somplace is what's needed, so that on spark launch, we can look for this file, deserialize it and use it.
↧