Hey Matt, On Wed, Aug 3, 2011 at 00:58, Matt Madhavan <[email protected]> wrote:
> Hello, > I have seen couple of email threads on this topic. But did not really get a > definitive answer. > > Currently we do not use Karaf. We use Felix and other related bundles via > pax runner. I have seen recommendations about using Karaf. Why cannot I > just > start the Felix container in debug via mvn pax:provision and do a remote > debug? What do I get out of Karaf that I donot get from Felix and its > webconsole (started using pax web and jetty etc). > A very good feature information is presented by http://karaf.apache.org/. While it depends on your needs I personally start any OSGi based toplevel (!) project without Karaf. The configuration support, features(.xml) support, the "fancy" command line, easy packaging, hotdeployment, remote access... All of them are feature you simply do not want to miss in your final server. It's not that you cant configure such a system from ground up yourself. The question is rather: why would you want to do it? Projects like geronimo, smx, talend, openengsb, (and many more) already proof that it is pretty easy to develop toplevel projects based on Karaf. My absolute favorite in the entire development tool-chain here is the "dev:watch *" command in Karaf which automatically reload snapshot bundles asap they are build by maven. Using this together with an on-file-changed mvn install script you'll get really (!) fast reload cycles. IMHO Karaf is definitely worth a look for every new OSGi project! If you're looking for more user reports here you may like to write directly to the karaf user list. > Also when using PaxExam (2.x.x), if I'm using the third type "lesson-junit" > my understanding is that: > > 1. I cannot use Native Container > 2. And so I can only do remote debugging. > > Please let me know if my understanding is OK! > I can't give any qualified answer on that (still on pax-exam 1.x; shame on me), but for non-native container the "only-remote-debugging" thing is definitely true. Since the itests does not run in the same "container" as your unit-tests you'll have to work with the remote debugger. I hope this helps. Kind regards, Andreas > > Thanks in advance! > > Matt >
