I have trouble using bsh in an application that must use a custom
classloader. When I try to instantiate Interpreter using new
Interpreter(), the custom class loader gets a request for java.lang.bsh
in findClass(name). The name is bogus, it is obvious that it cannot be
loaded from anywhere. It is not even a class, just a package name!
It seems the standard class loader gives up and asks our classloader to
What should I do? Outside of the custom classloader bsh runs fine. Do
you want to see my findClass()?
Is the beanshell willing to cooperate with custom class loaders at all
or is there a known conflict with custom class loaders?
I'm using the current bsh-2.0b2.jar.
Get latest updates about Open Source Projects, Conferences and News.