Is there a way to stop JForex from using multiple classloaders when doing the historical testing? I'm looking to see if it is possible to have a Singleton span all running strategies. With multiple classloaders, it creates multiple Singletons. If we're able to do this, then we should be able to increase testing speed.

I understand the need for multiple classloaders, to create a new environment for each strategy so that anything assigned to class variables (static) doesn't crossover between running strategies... but would love to have the option to turn them off.

AFAIK there is no way to add new jar to the system class loader when program is already running. Second problem is that JForex runs from web start and has security manager. All our code is signed with trusted certificate and granted full access (asks your permission of first run), but strategy code is not signed and shoud be loaded with custom class loader to grant access to Strategies/files directory and full access if @FullAccess anotation is used