Browse Source

Corrected bug where Hold action cannot complete because the reader is not available. Previous "improvement" was based on a bad assumption that responses were emitted during the job. Actually, responses are emitted after the job is finalized and sent to the output processor so that theory was incorrect. Earlier problem was related to something else & this code was ok.

git-svn-id: https://svn.microneil.com/svn/SNF4CGP/trunk@57 59e8e3e7-56fa-483b-b4b4-fa6ab0af3dfc
master
madscientist 11 years ago
parent
commit
6978ec4c3f
1 changed files with 1 additions and 1 deletions
  1. 1
    1
      SNF4CGP/JobPool.cpp

+ 1
- 1
SNF4CGP/JobPool.cpp View File

void Job::doFILE() { void Job::doFILE() {
doInitialRead(); doInitialRead();
doScan(); doScan();
closeReader();
doAction(); doAction();
closeReader();
} }
RuntimeCheck CheckMessageReaderIsValid("Job::Reader() Check(0 != Reader_)"); RuntimeCheck CheckMessageReaderIsValid("Job::Reader() Check(0 != Reader_)");

Loading…
Cancel
Save