|
Re: RequiresBundle, ImportPackage and virtual providers: msg#00092ide.eclipse.equinox.devel
On Thursday 30 March 2006 21:55, Neil Bartlett wrote: > Post-291, developers will still have to find a solution to the > problem, and there is nothing to stop them using OSGi Service Layer. > However this "lowest common denominator" approach is a little > disappointing. I disagree. You are right for the short-term, but once JSR291 has settled in and OSGi has adjusted to it, we are then free to experiment with more than a single approach to the Service layer on top of JSR-291. Perhaps the OSGi model does not suit all needs, or perhaps it is too complex for some. I am generally not in favour of large "all-or-nothing"/"kitchen sink" specs, as they become monolithic, hard to use, inflexible and doesn't call for innovation and evolution to the same degree as smaller ones. So expect to see more JSRs on top of 291, but we need to start somewhere. ;o) Cheers Niclas |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Re[2]: RequiresBundle, ImportPackage and virtual providers: 00092, Neil Bartlett |
|---|---|
| Next by Date: | Re: RequiresBundle, ImportPackage and virtual providers: 00092, Jeff McAffer |
| Previous by Thread: | Re: Re[2]: RequiresBundle, ImportPackage and virtual providersi: 00092, Neil Bartlett |
| Next by Thread: | Re[2]: RequiresBundle, ImportPackage and virtual providers: 00092, Peter Kriens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |