In the database servicxes, we have an execution policy filter that is very similar to what your are describing; I think it even covers more uses cases. I propose to use the same mechanism (and code) for a default execution policy for the job SLA, will that do?

Furthermore, I also propose to add the methods setDefaultExecutionPolicy(ExecutionPolicy) and getDefaultExecutionPolicy() to JPPFClient (or one of its superclasses), so the same functionality can be achieved programmatically as well.

I propose to use the same mechanism (and code) for a default
execution policy for the job SLA, will that do?

sure, looks perfect

Furthermore, I also propose to add the methods
setDefaultExecutionPolicy(ExecutionPolicy) and getDefaultExecutionPolicy()
to JPPFClient (or one of its superclasses), so the same functionality can
be achieved programmatically as well.

Is this the right place for that method? What would happen if one submits job with policy set and client has default policy defined?

marcin

Is this the right place for that method? What would happen if one submits
job with policy set and client has default policy defined?

A non-null default policy would only apply to jobs whose policy is null. That's my understanding of what default policy means.

Also, keep in mind that you can have multiple instances of JPPFClient, each potentially with its own configuration (via the JPPFClient(TypedProperties config) constructor). We must preserve the flexibility this provides. So yes, I believe JPPFClient is where the default policy accessors should be.

Note that you can also easily implement a default policy feature by subclassing JPPFClient and overriding its submitJob(JPPFJob) method, for example like this:

final ExecutionPolicy defaultPolicy = new AtLeast("availableProcessors", 4);
try (final JPPFClient client = new JPPFClient() {
  @Override
  public List<Task<?>> submitJob(JPPFJob job) {
    if (job.getSLA().getExecutionPolicy() == null)
      job.getSLA().setExecutionPolicy(defaultPolicy);
    return super.submitJob(job);
  }
}) {
  // ... do some stuff ...
}

Implemented in master and branch 6.0. Published doc (v6.1):

• configuration
• development