Hi all, @Thomas true, support for Servlet 3.x, that´s of course a good point (for the next major release?). OSGI as a concept and the various kinds of how to implement it (declarative services, activator..) have enough inertia (I think), that I got curious and I am still thinking, there is some value to explore this more (I´ll check the proposal, of course). If it would be of a bigger value to get Turbine running in an OSGi environment, I don´t know and to get Turbine running there, with all whistles and bells would be probably a major release. At the end, support for the new servlet features are more in line with how Turbine is currenty used.
@Jürgen Running another container (of type OSGi) in Tomcat may be possible, but makes not so much sense, I agree. And what OSGi addresses could may be better achieved with support for modular concepts in Java 9, true! @Siegfried Thanks for the Avalon explanation and the hint to Spring (I forgot about it). I think this summarizes and justifies, why we still use Avalon. It is a robust and simple container. Thanks! Best regards, Georg Von: Thomas Vandahl <[email protected]> An: Turbine Developers List <[email protected]> Datum: 25.09.2015 08:05 Betreff: Re: [DISCUSS] OSGI in Turbine 4 Final Hi Georg, On 24.09.15 10:03, Georg Kallidis wrote: > 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? I wrote a proof-of-concept implementation of a OSGi service provider for Turbine based on Apache Felix. You can find it in proposals/tv/osgi It makes OSGI services available to a Turbine application. With some polishing and some testing this could be included into Turbine Core. I don't see much advantage in running Turbine in an OSGi environment. I'd rather focus on the new servlet features such as async processing and web socket. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
