On Sunday 30 July 2006 19:25, Johan Compagner wrote: > Wicket doesn't have real big package dependicies besides the normal jdk. > Are you saying that it did try to extract the complete swing from the jdk??
No, not at all. swing.tree, swing.text and swing.event are the only packages in the reference path. Feel free to see the full traversal in my mail. The top package name is the "inspected" package and all packages below it are the ones being referenced from that package. OSGi framework needs this info to build the class space (as they call it). So for each package I export, I also need to declare which packages such export uses, so that the framework can either guarantee that either the classes are name space compatible or startup will not proceed. Constructing this manually for larger applications is impossible, and the reason why Eclipse still isn't a well-behaving OSGi application, and instead rely heavily on strongly coupled bundles (Require-Bundle: header). This also became apparent first time I ran my OSGified Wicket, as Equinox needed 1.5 minutes to resolve the classloaders. That has been fixed, but didn't make it for v3.2, but will show up in Equinox 3.2.1. Cheers Niclas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
