Bug 4286 - Schema allows for an empty job
Schema allows for an empty job
Product: jbatch
Classification: Unclassified
Component: source
All All
: P5 normal
: ---
Assigned To: cvignola
Depends on:
  Show dependency treegraph
Reported: 2012-11-09 22:21 UTC by mminella
Modified: 2013-01-16 15:27 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description mminella 2012-11-09 22:21:17 UTC
Per the XSD provided in the spec, an empty job (no listeners, flows/steps/etc) is valid.  We probably should require that a job either contain the elements required to run or be extended from.
Comment 1 cvignola 2012-11-17 20:20:28 UTC
Well, I dunno ...  if people want to pass their time running empty jobs,  who are we to say no?  

One might similarly argue the Java spec should disallow classes that have no members, or perhaps methods that have no code,  or ...  well you see where I'm going.  

I don't think this is worth worrying about.  If others feel strongly about it, we can consider adding validation to kick out the job with an exception if there's nothing in it.  But I'm reluctant to do that because it adds more surface area to the spec and I'm unconvinced the addition has substantive value.