I am getting classloader permission exceptions with Aspectj. From the stack trace I believe that Aspectj tries to get the classloader.
The Aspectj runtime is deployed using a library. That library jar has classloader permission. Now the code weaving during compilation will weave the aspectJ calls into the SBB code. What is the security policy now? The SBB runs its classloader -> The aspectJ has permission -> The code of aspectJ is called -> Now as aspectJ is not calling priviledged action it is executed with SBB permissions -> Then it fails.
Is that the right interpretation? Do we have to enable class loader access for the complete container?
Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission getClassLoader)
|Register/login to use all DevPortal features - ( Log in | Sign up )|