On Wed, Aug 4, 2010 at 15:40, Les Hazlewood <[email protected]> wrote:
> Hi Chris, > > Thanks so much for filling in those gaps. Based on that, I have some > follow up questions: > > - So, if one were to make a parallel, Karaf is closer in its mission > to what Virgo provides due to the additional runtime/server services > it provides on top of Blueprint support. Correct? > Indeed. > > - Are Apache Sling and Karaf related in any way? My assumption is > that Sling could have been built on top of Karaf it it isn't already. > And if it's not - perhaps its because Sling's foundation predated > Karaf and it wasn't available at that time for consideration. > Sling is using OSGi at a low level, but I think it can be packages several ways, one of which does in fact use Karaf. I have just started looking at Sling myself, so I am no authority. > > - There are quite a few sub-projects under the Felix project umbrella > (http://felix.apache.org/site/subprojects.html). Does Karaf use most > of them? For example, I noticed Karaf has shell access - does this > mean that it builds on top or uses one of the Apache Felix Shell, > Apache Felix Remote Shell, Apache Felix Shell TUI subprojects? > Karaf uses a few by default, such as fileinstall, and we do build on top of the new gogo shell (which is an implementation of a new OSGi spec). However, we also provide a bunch of other things that are nice to have but weren't provided anywhere else, such as the ssh server and shell integration (built on top of Mina), and some additional logging features such as per bundle logging and enhanced logging output. > > - Is there any relationship with Apache Geronimo's 3.x OSGi/Aries > support and Karaf? Does one use components of the other and/or vice > versa? I'm trying to understand the value of Karaf independent of > Geronimo - the lines are very blurry to me on this one. > I could be wrong about this, but I thought Geronimo 3 was building on Karaf and using it as a base runtime for OSGi. The Aries project would be providing the specific implementations of some of the 4.2 EE specs. > > Thanks for being patient with these questions - I hope to assimilate > the information and help other people along the way if possible. > No worries, I'm happy to help. We have integration with Shiro on our roadmap: https://issues.apache.org/activemq/browse/SMX4-433 so we may need the same back from you some day soon :-) Thanks, Chris > > Thanks again, > > Les > > On Wed, Aug 4, 2010 at 2:11 PM, Chris Custine <[email protected]> > wrote: > > You have pretty much nailed it. Karaf is a convenience packaging of > common > > libraries and utilities and is fairly well suited to branding and > > repackaging to create other OSGi based projects on top of it. We also > try > > to fill a few gaps on our own (features descriptors, enhanced command > line > > shell, etc) that we found a need for. All of the parts can be replaced, > > swapped out for different versions, etc. We also have some maven plugin > > work that makes it easier to create and verify assemblies with your own > OSGi > > bundles. > > Aries is largely an implementation of parts of the OSGi 4.2 EE spec plus > I > > think some additional bits that are under consideration for future specs > > versions. So technically you could swap the Aries bits out of Karaf for > > other implementations just as you can swap out Apache Felix in favor of > > Equinox if you wish. > > The whole scene is evolving rapidly so I know some of this is unclear at > > first glance. We are just trying to keep spec implementations separate > from > > Karaf so that it can continue to be general purpose. > > HTH... > > Chris > > -- > > Chris Custine > > FUSESource :: http://fusesource.com > > My Blog :: http://blog.organicelement.com > > Apache ServiceMix :: http://servicemix.apache.org > > Apache Felix :: http://felix.apache.org > > Apache Directory Server :: http://directory.apache.org > > > > > > On Wed, Aug 4, 2010 at 13:22, Les Hazlewood <[email protected]> wrote: > >> > >> Hello all, > >> > >> I'm new to the Apache OSGi ecosystem and I'm having a hard time the > >> roles of some projects. I understand Karaf has recently become a TLP > >> (congrats!), but I'd like some clarification if someone would be so > >> kind as to oblige. > >> > >> I understand the Felix OSGi is the core OSGi container supporting > >> bundles, classloading, etc. (e.g. parallel to Eclipse Equinox). What > >> I don't understand is how Aries and Karaf might fit in or work in a > >> symbiotic relationship. > >> > >> If I continue with the Eclipse analogy, I assumed Aries was parallel > >> to Eclipse Virgo, but that may not be correct: > >> Virgo is a simple port of Spring DM Server donated to the Eclipse > >> foundation, with continued modifications. DM Server (and Virgo by > >> extension) is essentially a complete OSGi application server and > >> supports things like startup/shutdown scripts, logging, server > >> diagnostics, as well as supporting the OSGi 4.2 Blueprint deployment > >> model. > >> > >> If Aries was an exact parallel to Virgo, I assume it would also be a > >> standalone server. But it appears this is incorrect per the Aries > >> Incubator proposal: > >> > >> "... The project is not expected to deliver a complete application or > >> integration server runtime but will instead deliver enterprise > >> application componentry that can be integrated into such runtimes. > >> ..." > >> > >> So, is that were Karaf comes in? Is Karaf this complete OSGi > >> application server? > >> > >> Thanks for any clarification! > >> > >> Best, > >> > >> Les Hazlewood > > > > >
