Guillaume Nodet wrote:
I agree with most what you said. But when it comes to build an application, you can't really have your developers learn 3 different ways of doing the same thing, you kinda have to choose one and stick with it. I guess that's Charles' main concern here, because it's not about developping against *one* standard and eventually choose the implementation. You need to evaluate the different frameworks first. But I guess it's the same problem when building a web app, or even a jee app where you can choose between Spring or EJBs ... So that's far from a new story.
Except with OSGi this does not have to be a final decision. You can convert your bundles from one framework to another one bundle at a time and still have your entire application running at every stage of this process. This shows how both the modular (side-by-side deployment) and the service (implementation independence) layers combine to give you unparalleled migration capability. In the end there is no free lunch - you have to change the code. But you get to do it at your own pace rather than as one huge swoop. I'm not deeply familiar with EJB's and Spring but I believe OSGi is the first environment to provide this power. I suspect newcomers to OSGi need some time to grasp the full consequences of having strong isolation at both levels: sharing classes (modular) and sharing instances (service). Throw into the mix dynamics at both layers and the subsequent need to let go of predictable startup/shutdown and the learning curve rockets upwards.
Cheers, Todor --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
