Status: New Owner: ---- New issue 401 by Sebastian.Zarnekow: SecurityException in environments with signed jars http://code.google.com/p/google-guice/issues/detail?id=401
A SecurityException is raised when a dynamic class is created in a package, that contains signed classes. To overcome this, we have to patch Guice and substitute the net.sf.cglib.core.NamingPolicy and prefix the package of the generated classes with a $ the same way, as it is done for classes from java.* packages. It would be very nice, if either the naming policy were customizable or the NamingPolicy would somehow validate the "base class" and choose another package on its own, if the class is signed. This behaviour was observed with Guice 1.0. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en -~----------~----~----~----~------~----~------~--~---
