I have some questions regarding the usage of classloaders in dynamic java. According to the documentation, DynamicJava apparently uses two separate classloaders during the course of execution. (1) the Java ClassLoader and (2) the DynamicJava package's TreeClassLoader (an extension of the Java ClassLoader itself). Which classes is the TreeClassLoader responsible for loading and which classes will be loaded through the JDK ClassLoader?
I am using classes - defined in classes external to DynamicJava scripts - that use class.forName(). Will this still yield the "unexpected results" described in the documentation regarding the use of Class.forName()? Or are classes defined external to DynamicJava immune from this behaviour of the interpreter?
We are planning to use DynamicJava in an RDF-based development environment for content aggregation. Originally we had intended to use JPython, but feel that DynamicJava meets the requirements better. Thanks for the excellent tool you've created!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> Which classes is the TreeClassLoader responsible for loading and which classes will be loaded through the JDK ClassLoader?
The TreeClassLoader first looks after compiled classes using the system classloader. If no class was found, it tries to find a source file and then interprets it.
> I am using classes - defined in classes external to DynamicJava scripts - that use class.forName(). Will this
still yield the "unexpected results" described in the documentation regarding the use of Class.forName()?
This is no problem with compiled classes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have some questions regarding the usage of classloaders in dynamic java. According to the documentation, DynamicJava apparently uses two separate classloaders during the course of execution. (1) the Java ClassLoader and (2) the DynamicJava package's TreeClassLoader (an extension of the Java ClassLoader itself). Which classes is the TreeClassLoader responsible for loading and which classes will be loaded through the JDK ClassLoader?
I am using classes - defined in classes external to DynamicJava scripts - that use class.forName(). Will this still yield the "unexpected results" described in the documentation regarding the use of Class.forName()? Or are classes defined external to DynamicJava immune from this behaviour of the interpreter?
We are planning to use DynamicJava in an RDF-based development environment for content aggregation. Originally we had intended to use JPython, but feel that DynamicJava meets the requirements better. Thanks for the excellent tool you've created!
> Which classes is the TreeClassLoader responsible for loading and which classes will be loaded through the JDK ClassLoader?
The TreeClassLoader first looks after compiled classes using the system classloader. If no class was found, it tries to find a source file and then interprets it.
> I am using classes - defined in classes external to DynamicJava scripts - that use class.forName(). Will this
still yield the "unexpected results" described in the documentation regarding the use of Class.forName()?
This is no problem with compiled classes.