Hi all! to restart an older discussion (What happens after M1?) I have some more (naive) questions about this. Should Turbine support/be runnable in a OSGI container? Should this become a main focus of the next release? -> Create a new JIRA issue (feature request)!
Some more questions, which came into my mind are: - What would be the Proof of Concept for OSGI support? E.g. deploying into Apache Karaf (light weight OSGI)? - Configuration is up to now done using Yaafi component. Could Turbine/Yaafi/Avalon Container include a Service Registry? E.g. something like http://wiki.osgi.org/wiki/PojoSR, https://code.google.com/p/pojosr/wiki/Usage)? Dow e need support for Declarative Services/ Blueprint OSGI? Would it more easy to use these standards instead? - Refactoring: Do we need more than one Turbine bundle? E.g. expose an interface bundle and an implementation bundle? Some pPackage refactoring may be required at least. - Classloading: Cft. to http://wiki.osgi.org/wiki/Avoid_Classloader_Hacks ). There is an interesting discussion about class loading issues: http://www.mail-archive.com/[email protected]/msg05231.html. Class.forName classloading should be checked - Do we need Servicemix OSGI-enabled packages for dependencies? More helpful Infos, especially for Fulcrum Components: https://wiki.apache.org/commons/CommonsOsgi, https://issues.apache.org/jira/browse/COMMONSSITE-23, and commons-logging is a special case.. Best regards, Georg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
