Comment #1 on issue 400 by mcculls: Pull out CGLib and reexport in in OSGi http://code.google.com/p/google-guice/issues/detail?id=400
My latest round of changes to the classloading/proxying code means that you'll only need to make classes public or protected if you are using method-interception. This should drastically cut down on the number of classes that you need to expose. I'm also improving the error message to identify exactly which class is involved. Often it's just the implementation class and its constructor that you need to make protected or public, and only when running in strict containers like OSGi. Also if you're using OSGi, you could keep these hidden in a non-exported package to avoid leaking details. BTW the reason CGLIB is internalized is because it's an implementation detail that we don't want clients to rely on. Similarly it's repackaged to avoid clashes with other versions of CGLIB on the classpath when running in standard Java containers. So in summary: I very much doubt we'll be extracting CGLIB as a public dependency, but the 2.1 release should allow you to keep classes package-private unless using method-interception. -- 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 -~----------~----~----~----~------~----~------~--~---
