The docs mention in section '2.4 Meta Data Access Improvements' that
Having noted that - I'd be interested to know what it means."It is also worth noting that Jobs can now be stopped via the database..."I mean understand - not assume.
However, this is what I assume. That one should update the database (via the JobRepository) using the JobOperator interface. I see JobOperator has a handy looking stop(executionId) method.
Also note the (Simple)JobService supports stop and stopAll calls.
I know it sounds obvious but just double checking that I've interpreted this correctly.
TIA,
David.


I mean understand - not assume. 
Reply With Quote