Hi Thomas, 5. I think the main difference between SM3 and SM4 is JBI vs NMR. NMR is OSGi + Camel. Am I right?
>> No. The Normalized Message Router is part of the JBI specification. Camel is a routing engine (a Charles Moulliard Senior Enterprise Architect Apache Camel Committer ***************************** blog : http://cmoulliard.blogspot.com On Fri, May 15, 2009 at 8:34 AM, Thomas Joseph <[email protected]>wrote: > Thanks Charles and Guillaume for your responses. > > > > Note that ServiceMix Kernel has been moved to Felix and is now Karaf. > > > Happy to learn that. I ve been following your blogs, that has pretty much > caused an interest in Service Mix/Karaf. > > > > Note that Karaf can now be started with Equinox. > > To answer your question, if you use your native osgi container + all > > the bundles that come from Karaf, you end up with ... Karaf mostly. > > > > Good to learn that I can switch the OSGi container. > > > > > 2. I want to build OSGi based applications. How can Service Mix help me > > in > > > doing integrations with CXF or Drools, over my native approach to > > integrate > > > them with the OSGi container. What additional benefits? > > > > Nothing really. It will just save you some time because we've worked > > hard on finding all the dependencies, make the OSGi bundles and test > > everything. > > If you just want to use OSGi + CXF, you can try and redo the same work > > if you want. > > > Good to learn on that. Charles, your tutorial is cool. > > > > > > > 3. How is it better to/compatible to/compared to SpringSource DM > server? > > > > The license is first a big difference in itself (Apache Licensed vs > > GPL). Spring dm server afaik also defines some non standard > > extensions to OSGi so if you go that route, you'll be kinda locked to > > it. > > Ok, so you confirmed my belief. > > > > > > > > > 4. Pax Runner recently provides the service mix profiles. How good or > bad > > is > > > that approach when compared to using service mix as such? > > > > The main problem I have with Pax Runner is that it *downloads* > > everything. You have no easy control over what happen when you boot > > the framework and a lot of people can't allow that. > > > > > I think the value of Karaf lies in both its bundles that provides some > > additional features on top of a bare OSGi framework, but also from the > > fact that it's a pre-built server that you can just download and > > install. If you prefer using pax-runner for that, feel free to do so. > > Karaf just aims to save you some time in building your server. > > > I ve been using Pax Runner for some time, and I ve been happy over it on > development. I would be happy to use my learning from there over here. > Actually, my setup with Pax Runner very much looks like the SM distribution > > Now few more questions to add: > > 5. I think the main difference between SM3 and SM4 is JBI vs NMR. NMR is > OSGi + Camel. Am I right? > > 6. As a new user to SM4, I would not want any kind of JBI stuff and just > want OSGi with all the "goodies" that the SM can provide me. Is there any > way (profiles or something like that) which I can use fo fulfill this > requirement. Actually I want a sleek profile thats just right for a OSGi > entrant like me. Plus an optional profile to add NMR + other components > like > Drools. Possible? > > I am sorry if these things are already mentioned somewhere in documentatons > and presentations at SM/FuseSource site, but I would go to spend some time > on it if I can decide if I want to use SM at the first place. > > If some of these things are already not there is SM, I would be happy to > extend my support to develop them. > -- > Thanks and Regards, > /Thomas Joseph > > LinkedIn: http://www.linkedin.com/in/ethomasjoseph > Twitter: http://twitter.com/ethomasjoseph > Blog: http://openthoughtworks.blogspot.com > > ------------------------------------------------------------ > Promote Open Source - Promote Liberty of Ideas and Software. > ------------------------------------------------------------ >
