By chetan_oct
via infoq.com
Published: Nov 26 2009 / 12:59
Porting great infrastructure to OSGi often means solving complex class loading problems. This article is dedicated to the frameworks that face the hardest issues in this area: those that do dynamic code generation. Incidentally these are also the coolest frameworks: AOP wrappers, ORM mappers, and service proxy generators are just a few examples.
Comments
MCII replied ago:
"Porting great infrastructure to OSGi often means solving complex class loading problems."
So, don't do it. Who really needs OSGi anyway?
Voters For This Link (10)
Voters Against This Link (1)