Comment #17 on 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
I'm writing a container-based test at the moment to recreate this bug so it doesn't re-appear. Jesse do you still want the patch trimmed down to be an "on/off" switch? Or do we want to allow people to force the use of bridge class loaders? ie. some situations you don't need an extra class loader to bridge between types and so we wouldn't create one, but using an extra class loader would let you eagerly unload proxy classes... (hence the 'eager' setting in the patch) -- 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 -~----------~----~----~----~------~----~------~--~---
