I'm thinking about improving our jsp (and other scripting) support. One problem I see atm is our class loading for compiled scripts.
At the moment, we have the RepositoryClassLoaderProvider which allows to get a class loader for a user which is able to load classes from somewhere out of the repository. All the scripting support for writing classes into the repository have to know where in the repository classes are located. The scripting engines write the compiled script to this configured locations and later on the class is loaded by the RepositoryClassLoader. Obvioulsly this has at least two drawbacks: - The repository path where classes are located has to be configured properly at several places - The scripting support is tied to jcr which makes it unusable in non JCR environments I think we should come up with a solution for these problems by introducing a ResourceClassLoaderProvider with a similar interface as the RepositoryClassLoaderProvider. I'm not sure about the user argument especially if we plan to use the OSGi User Admin stuff. The provider could provide a ResourceClassLoader which extends ClassLoader and has an additional method for writing class files and maybe removing them (perhaps we need more functionality?) WDYT? Carsten -- Carsten Ziegeler cziege...@apache.org
