This is not the default since it could create memory leaks
But in a server it is quite easy to use setServiceManager/resetServiceManager
to handle it (either from the server itself or from an app in lightweight containers).
base class handling:
- classloader enriched with libs folders (and subfolders)
- Lifecycle (allow to start/stop a container)
Note: the classloader is created from libs command, it is handy to organize batches
by folders to be able to run them contextual using this command.
When a partitioned step is run, this controller will only be used for the partition threads,
NOT the top-level main thread that the step executes upon.