41582012-09-28 14:37:00 +0000Job Repository not clearly defined in the spec2013-01-16 23:04:15 +0000111Unclassifiedjbatchsource1AllAllCLOSEDFIXEDP5normal---1mminellacvignolaissuesmk111283oldest_to_newest111800mminella2012-09-28 14:37:16 +0000The spec defines that there should be a repository, however outside of this provides no further guidance on it's purpose. To be thorough, should we include a more descriptive explanation of what functionality the repository is intended to facilitate (restartability, metrics, etc)?112371cvignola2012-10-05 19:03:46 +0000I agree further explanation is required.117482mk1112832012-12-03 01:44:46 +0000Also, Section 4.4 of the sepc says:
"A job repository holds information about jobs currently running and jobs that have run in the past. The JobOperator interface provides access to this repository. The repository contains job instances, job executions, and step executions."
The spec must mention when information about jobs that have run in the past are kept. At the minimum it must say one of the following:
a) Info / details about jobs (including the details about the jobs that have run in the past) created by a JavaEE application are removed when the JavaEE application is un-deployed
OR
b) Info / details about jobs (including the details about the jobs that have run in the past) created by a JavaEE application are retained even after the JavaEE application is un-deployed. The duration of how long these data are retained is unspecified117493mk1112832012-12-03 01:46:09 +0000Previous comment was posted by Mahesh.Kannan@Oracle.Com120774cvignola2013-01-16 16:13:19 +0000The spec has been updated to state what the job repository holds and further states the implementation of the job repository is an implementer decision.