I would like to second the suggestion to look at Amdatu, as well as the 'warning' that a lot of tutorials are unquestionably Eclipse-biased. We don't use eclipse at all, and happily build / test all our (complex, multi-module) OSGi systems with Maven, and the Bundle and Pax plugins, and code using the IntelliJ IDE. Don't get locked into any particular IDE...
One final suggestion: I'm not sure how serious you are about the "distributed Java" statement, but if you really are looking into Distributed computing, OSGi is not the best framework for you. Look at: * The Rio Project <http://rio-project.org/>, which is built on top of * Apache River <http://river.apache.org/concepts.html> (formerly called Jini) These allow you to build true services-oriented architectures in pure Java, where the physical location of services don't matter, and the fallacies of distributed computing are addressed head-on. We're using it quite successfully, and alongside OSGi (still waiting for the mythical, magical technology to merge the best of both technologies). If you are happy to be relegated to e.g. RESTful web services, however, OSGi is a treat - it's just a beautiful, lean, productive infrastructure which has given us such good results over the years. OSGi is all about choice. iPojo is effectively a service publishing / injection framework, and there are a couple of options to you: Declarative services, Felix dependency manager, iPojo, Blueprint container. None of these have anything to do with publishing a service as an HTTP resource. A service published with any mechanism (like the above) can be exposed as a REST resource using Amdatu (or similar). OSGi is like Arch Linux / Gentoo Linux - you effectively create your own environment with many available building blocks. I would also urge you to look at Java EE. It is like Mac OS X - you get EVERYTHING in the box, making it rather easy to use, but less flexible. I mention this, because Java EE has very strong qualities like transaction management, asynchronous communication, security, persistence, general resource management, object- and thread pooling (for performance/scalability) etc built-in, where you have to assemble each of these capabilities yourself using OSGi. There are many open-source containers that implement the Java EE spec, like Glassfish, Wildfly, etc. Good luck with your search! kind regards, Dawid On 17/09/2014 19:21, Ivanhoe Abrahams wrote: > Hi andrew > > Have a look at the amdatu website > They use felix dependency manager in their examples not ipojo but their > examples are complete and u can use ipojo or any other osgi capable > dependency injection framework. > > You should be up and running in about an hour if you follow and read the > getting started pages... warning ... it is heavily slanted towards > eclipse... hope you are ok with that. > > Regards > Ivanhoe > On 17 Sep 2014 7:14 PM, "Andrew Beechey" <[email protected]> wrote: > >> Dear, users Felix Apache, I work for a large financial institution that is >> looking to move is development from mainframe Cobol cics db2, into >> distributed Java. The types of applications we need to develop are JAX RS >> web services accessing a mainframe hosted db2 database. These web services >> need to perform the classic CRUD actions. I have been investigating OSGi >> and feel it has much to offer, my problem is I have no idea where to start, >> then I came across ipojo, what I can't seem to find is any mention of ipojo >> creating JAX RS web services. Is it possible to expose JAX RS web services >> with ipojo? Where can I find examples and/or tutorials to learn how to >> develop these types of services with ipojo? >> >> Warm regards >> >> Andrew Beechey
