Hey Achim, inline.
On 04/23/2015 02:14 PM, Achim Nierbeck wrote: > commandline doesn't mean it's running inside an OSGi container. But it does mean that there are no missing dependencies. All the classes it needs are there and can be loaded. > > regarding ANT, If I where you I'd switch to Maven real fast, and let the > > maven-bundle-plugin do the Manifest generation > > together with embedding all "compile"-scoped dependencies. :D > > That seems like a lot of time to completely reconfigure how things are > built and deployed and packaged in the hope that it might make the > problem go away magically. I'd rather just figure out what is wrong. > > > hmm, not if you have the right setup. Actually a nice maven pom or > gradle build is clean > and reproducable. I think what I have now is clean and reproducable. But mostly a dependency manager is there to make it easier to have the whole team use the same set of libraries without having to put them in a version control system. This is not the issue right now, I have the right libraries. Perhaps there is a different way to package everything I'd love to hear about that. > erf. if you don't want to do a modularized application, why use karaf or > OSGi at all? A modularized application is certainly the goal in the end. But right now I have a single bundle that implements just 1 application that is part of the family of applications that runs within production. I want to start small and build from there, not do everything all at once. > If you just want to have an executable Jar that contains everything with > it. You don't need this > Boilerplate code. Running and managing multiple applications is hard. I need to maintain multiple upstart scripts and point them to the right version of the code. Which complicates deployment. There is also no way to let them make use of any shared code the way you can with Karaf. I can't have them use a shared database pool or thread pool. Karaf should allow me to do that eventually. Again I'm starting small by creating just one application now and I'm taking the route that should cause the fewest problems by bundling everything into a single jar. And I was hoping Karaf would come with some nice monitoring and management porn out of the box that I can use. > But if you want to work with a modular application, then you'll get the > benefits of karaf and OSGi > instantly. Only update one of your bundles if needed, the rest will stay > the same. But you have to start small. I ported 1 application now and I'm adding the other 8 later. Simple first, more complicated later. > For easier deployment you'll have feature descriptors (an xml) so the > "easier to deploy" doesn't count. Dumping a self contained uber-jar into a directory seems like the easiest way to get something to work. The code should load and I can test that I haven't made any errors in the manifest file or class definitions. The only problem I have now is that Karaf seems to load jars in a really weird way. The standard java interpreter loads the jar and runs the code just fine. Jurgen
