Status: New Owner: ---- Labels: Type-Defect New issue 343 by mcculls: BytecodeGen uses system classloader when applying AOP to system types http://code.google.com/p/google-guice/issues/detail?id=343
We currently assume that classloader bridging is not required for types from the system classpath. For such cases the BytecodeGen.getClassLoader() method just returns the type's classloader, which will be the system classloader. While this assumption is correct most of the time, it won't work when an application loads Guice in a non-system classloader and then proceeds to apply AOP to a system type. In this scenario the system classloader won't have access to the internal AOP types, leading to a runtime exception. This situation appears to be uncommon, because I've only just come across one example of this very recently. Because fixing this requires changing the algorithm in BytecodeGen (which would then entail re-testing) I would be OK with this being postponed until 2.1 to avoid further slippage of Guice 2. -- 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 -~----------~----~----~----~------~----~------~--~---
