I would either use integration tests based on pax-exam, or even easier, deploy your bundle (using osgi:install mvn:groupId/artifactId/version-SNAPSHOT) in a standalone karaf instance and use the "dev:watch *" command. Each time you rebuild your project using maven, the bundle in karaf will be automatically updated.
On Tue, Nov 29, 2011 at 09:14, Alexander Krauss <alexander.kra...@qaware.de> wrote: > On Tue, Nov 29, 2011 at 8:12 AM, Guillaume Nodet <gno...@gmail.com> wrote: > >> The cxf-example-osgi-blueprint only can be ran inside of OSGi container. >> You can not run it as a stand-alone Java process. > [...] >> There's a way actually. You need to use PojoSR which is a small> library to >> emulate an OSGi framework but without the classloading> (only the registry >> really). I've been able to have it run Blueprint. > Thanks for the pointer. > > Actually, I was more expecting a solution in terms of the build process, > such as being able to build both a blueprint bundle and a stand-alone > Java application > from the same source tree. But I realize that this is tricky, since > the dependencies > are quite different in both cases, and also the actual camel context > xml seems to be > different, too, even if the actual route spec is the same... > > Instead, what is the recommended way for developing blueprint bundles? Do > people > usually run Karaf locally or Felix in the IDE? > > Alex > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
