Paul Clapham wrote:Classes in "common/lib" don't have access to classes in any of the web applications. And when you load a class, that causes its superclass to be loaded first. In this case the superclass is in one of the web applications, so it can't be loaded.
It doesn't make sense (to me, anyway) for a plugin which is to be common to all web applications to have a superclass which isn't also common to all web applications.
I see your point - thank you for clarifying.
Would it be possible to somehow deploy the codeunit classes outside the webapplication folder. I have looked into dynamic jar loading, but i am reluctant to use this approach (gets very installation specific). Finally i had considered storing the .jar in DB blobs, and writing the files til WEB-INF/lib at application boot time - i just fear that i have to degrade performance / cause classloader leaks by activating WatchedRessource.