Right now only Java standard library classes/interfaces can be used in lambda code as only those classes are available on classpath during the compilation process. If user could add custom directories/jar files to the compilation classpath it should be possible to compile lambdas that use other classes or interfaces.
Class loading mechanism should also be checked as Java treats same classes as different if they were loaded by a different classloaders - it might cause problems if user loads his class/interface and then lambdaFromString loads it again using its class loader when loading lambda code.
Interface proposition: classpath entries as List configured the same way as imports in LambdaFactoryConfiguration
Right now only Java standard library classes/interfaces can be used in lambda code as only those classes are available on classpath during the compilation process. If user could add custom directories/jar files to the compilation classpath it should be possible to compile lambdas that use other classes or interfaces.
Class loading mechanism should also be checked as Java treats same classes as different if they were loaded by a different classloaders - it might cause problems if user loads his class/interface and then lambdaFromString loads it again using its class loader when loading lambda code.
Interface proposition: classpath entries as List configured the same way as imports in LambdaFactoryConfiguration