osgi

I just recently stumbled upon the fact that Declarative Services in OSGi can set the configuration of a component to required so that the component receives it upon activation, removing the gap between component activation and configuration. I also realized with this that you can receive configuration updates via the modified -method. It seems to me like this functionality is quite similar to that provided by implementing the ManagedService interface and publishing that as one of the "services" you provide. It seems like I could completely ignore ManagedService & just use the DS configuration

I'm just trying to get my head around the Managed Extensibility Framework ( MEF ) at the moment and digging into a bit. I have an Eclipse background so in my brain I currently have the equation: MEF =~ OSGi for .NET Based on what I have heard so far. Am I on the right lines? Scott Hanselman helped to highlights the specifics about MEF in his podcast 148 with Glenn Block. Compared to OSGi, MEF is built upon "Inversion of Control" and OSGi is not: it (OSGi) will discover new bundle through a different mechanism based on a Life Cycle Layer. MEF is focused on application extensibility. It uses DI

We recently started to develop a Java desktop app and management has requested that we make use of Rich Client Platform. I know of four for Java namely: Eclipse RCP - www link to ecipse rcp , Netbean RCP - Netbeans RCP web site , Spring RCP - spring rich client Valkyrie RCP - Valkyrie rich client Has anyone got any experience in any of these and if so what are the strength and weaknesess of each? thanks I recommend that you take a look at JSR 296 - it's not complete yet by any stretch, but I think it hits the sweet spot for providing certain core functionality that you really, really need in

There are two main approaches when developing an OSGi application with Maven: POM-first and MANIFEST first. I'm looking for an answer that is in a form of a table that shows pros and cons of each method. To be more specific, I would also like to know how it relates to: Maturity of toolset Vendor independence Development ease (which includes finding people who can do the development on the tooling) Compatibility Avoiding ClassNotFound Avoiding manual work At present this is what I can come up with POM-First Pros (using maven-bundle-plugin) Leverages existing Maven skills, repositories and

When a bundle is updated (say to fix a bug), what happens to other bundles that are currently using the one being updated? Say that there are two bundles service and dao. Say that classes in service bundle are using classes in dao bundle when I issue command to update dao layer. Will the class in service layer using dao code get an exception? Thanks for your response . I meant to say updated with the same version. until a bundle refresh occurs which includes the dependent bundle. Bundle refresh operation is invoked by the user updating the bundle, right? Say that when user invokes refresh to

I am pretty new to the whole Java and OSGi world and I have trouble understanding the eco system of a OSGi web application. To be more precise I am at the moment trying to understand how all the parts of the eco system are related to each other: OSGi Framework (e.g. Apache Felix, Equinox, Knoplerfish) OSGi Runtime (e.g. Spring DM Server, Pax Runner, Apache Karaf) Web Extender (e.g. Pax Web Extender, Spring Web Extender) Web Container (e.g. Apache Tomcat, Jetty) To give you a visual representation of my actual understanding of their relationship check out this image: As far as I know the OSGi

I've been using OSGi for a while now and I have various solutions to the problems I encountered. I wanted to revisit one of these and see if people had come up with different solutions. One of the most common issues I have with OSGi (Equinox 3.4.2) is the frequent unavailability of the Thread's context ClassLoader. I know this is partly an Equinox problem, but I have encountered the issue with Felix as well. I encounter this mostly with 3rd party libraries that start their own Threads or ThreadPools. When these are started during Bundle or DS activation, they can end up without their