There are 2 possibilities for dealing with the SPI based services issue: 1) Interceptor pattern at runtime to look at services definitions and generate OSGi services when a bit of text is detected - as done by the JBoss interceptor (http://docs.jboss.org/osgi/userguide/html_single/#SecServiceLoader). I believe such an interceptor does not need to be part of geotools per-se, but part of the OSGi runtime the ServiceLoader based jar's are deployed under. This point outlines my modifications to Mathieu's option 1.
2) The declarative services and compile time rejigging of META-INF/services to OSGI-INF/*.xml - The only sore point for me here is how we are going to do the compile time hackery. The osgi maven plugins don't really cover this. May be it is time to get the Bnd author (Peter Krien's) wisdom on this matter. I have a preference for option 1 but I would rather do the LifecycleInterceptor outside of Geotools. Thanks for the offer to prototype Mathieu, putting code where your mouth is. Cheers, Tisham. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/geotools-library-as-an-OSGI-plugin-tp6238602p6298586.html Sent from the geotools-gt2-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
