Currently, when looking up a resource in response to a class loading request coming from a node, the JPPF client only uses a single class loader that was associated with the corresponding job right after it was submitted. This can cause problems if some of the tasks in the job were loaded with different class loaders, or in edge cases such as when a job is submitted from a task executing in a node, and a task in this job requires one or more classes that are not in the node's classpath, but are in the initial client's classpath.

This enhancement is about adding the ability, via a specific API, to add/get/remove other class loaders for the job. There should be an API available in JPPFClient or its super classes, and another in the JobConfiugration to use with a JPPFExecutorService.