Harald wrote: > Here are some intermediate results on using the FactorySPI pattern in an > OSGi environment: > > - I've verified that it works as expected as long as you do not use > wrapped JARs in your bundles and configure buddy classloading appropriately.
What's preventing it to work with wrapped JAR's? Is there any workaround? It would be so simple just to add the buddy classloading to their wrapper manifest files and use them "as is". Just today I run into the same issue like udig: I wanted to have gt-shapefile in a different plugin than geotools basic jars and realized the shapefile data store would not be found. Adding buddy classloading didn't solve it ... and now that I read your above comment I guess why it doesn't. Since I really don't want to BUILD and repackage GeoTools (as you have done) just for USING it in an OSGI application I strongly support the notion of creating real OSGI-ready bundles by the GeoTools project in the first place, as you suggest. The reward seems worth the work from my POV. P.S. Almost every library I write myself becomes an OSGI bundle right from the start. This proved helpful already. -- Matthias Basler [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
