On Fri, Apr 3, 2009 at 12:40 PM, James Strachan <[email protected]>wrote:
> 2009/4/3 Toni Menzel <[email protected]>: > > I am also torn into the possibilities.Putting Karaf under felix will keep > > e.g. equinox advocates away (thats why Alex refer's to the devil :) ?) > > Also, any possible shortcoming (technical or political) of felix will > > directly affect Karaf as a higher level "enterprisy" solution. > > Not really - already Felix hosts lots of code which is independent of > the actual OSGi runtime code - including a runtime adapter code so > most of the Felix project itself can be used on equinox. Yeah, but then its because felix contains just too much ? You could also ask from felix perspective: Does felix describes itself as a osgi r4 framework + (default) compendium implementations OR an osgi ecosystem providing it all? Its basically all about measuring the Apache Felix brand (=put karaf into felix tpl project) against the chance to start rising an independent osgi enterprise eco system (where smx4knl already started at) > > > On the other hand, the one-shop stop for osgi sounds nice and convinient. > > But then you never stop and at best eat up ops4j pax tools as well next > > time. > > > > But to be honest, i never looked at smx4 before it was brought to the > felix > > list. And Karaf has to "earn" the brand that felix already has. > > No real "best" solution at this point i guess. > > Maybe someone should (from smx4) should try to formulate a positioning > > statement. > > Then things may become more clear probably. > > I wonder if this helps... > http://servicemix.apache.org/SMX4KNL/index.html how did i miss that? But i would suggest to add the fact that is a kind of "batteries included" solution because all those features are promises felix itself could make when giving it a the right provisioning setup (fileinstall,url handlers,configadmin ..) The main benefit of caraf to me is - that everything is at its place by default ("batteries included") - higher level provisioning: feature concept (not really highlighted on the page currently) - one shop stop for the features and their documentation (no true currently, a real must TODO when opening karaf) Don't get me wrong, as an osgi maniac its all fine & great but putting on the standard J2EE-Hat we heard those days complaining about osgi ("not ready for enterprise") it is not clear immediately that smx4knl is a good start for starting with osgi. Caraf really could start changing their minds when presented properly. > <http://servicemix.apache.org/SMX4KNL/index.html> > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ > -- Toni Menzel Software Developer Professional Profile: http://www.osgify.com [email protected] http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
