This link has been bookmarked by 2 people . It was first bookmarked on 06 Aug 2008, by Lubos Pochman.
-
18 Apr 09
-
Classy
-
I start to see that the whole Aspect Oriented Programming (AOP) business is not about aspect oriented programming, but it is about hammering an existing code base into its intended slot.
-
In the real world, class loaders are (ab)used for configuration and ad-hoc plugin systems.
-
Creating a proxy is class loader magic.
-
you need to define this class in a class loader and this is where the modularity comes into play.
-
In OSGi, the imported packages are all a bundle can see
-
3 bundles involved: the proxy generator, the bundle needing the proxy, and the client bundle.
-
Spring solved this problem with a special class loader that chained the class loader from the client bundle together with the class loader of the Spring bundle.
-
when the generated proxy class is instantiated, it will need access to all the classes that the
DocumentEventrefers to: the super class, classes used as parameters in method calls, exceptions thrown, etc. -
a proper modular system.
-
the class loader that we need must be able to see each of the interface classes class loaders.
-
It can then create a combining class loader for each bundle that uses the Proxy Generator service. This class loader will then be associated with the class space of that bundle and should therefore not be polluted with classes from other class spaces.
-
-
06 Aug 08
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.