On Feb 5, 2008 5:56 AM, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> > with the release of the OSGi extension to Spring[1], it seems to be
> > reasonably easy to turn any spring app into an OSGi deployment ('bundle').
>
> Yes, but doing so seems backwards.Why? To me this seems very straightforward. > It appears that SpringSource is > conceding that OSGi is to Spring as JSF is to Struts, and that Spring will > go the way of Struts. Maybe, as I completely don't know what you are talking about. > So why not write directly to the standard in the > first place, I agree, having a pure osgi deployment makes sense. It would give as re-deployable components. (Setting aside the fact that our components are not build to be redeployed. It simply will not work without massive refactorings on a component-level.) But who is willing to take the pain of either * moving over our complete component framework to osgi, from one massive-invasive to another one (I didn't yet take a look at iPojo, though) and removing Avalon/Phoenix support * creating another wrapper around Avalon, like the one we have in spring-deployment. (at least spring is build for this task, see BeanFactory and BeanDefinitionReader.) > and discard the legacy Spring code? :-) LOL. You are trolling. Avalon is a legacy. Spring is widely used, easy to handle, well documented and in active development. There is no reason why spring-, phoenix- and eventually pure-osgi-deployment couldn't exists side-by-side. And guess what: Everyone who is looking for ease-of-integration with other POJOs is best served with spring-deployment. Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
