This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
sorry for creating a new thread for each small question. I just don't want to mix all kinds of topics in one post
So here's the actual question: Do you no of any limitations/situations/application types where OSGi definitely can't or at least should not be used? OK, obviously the combination of OSGi and Spring can be used anywhere Spring alone can, I guess. But I'm thinking of use inside other frameworks, some kind of container or anything like that which constrains the usage of OSGi. As I don't know how different OSGi implementations work under the hood, I have no idea with this question...
I think osgi is so simple and easy to use. It is not very different from traditional Java applications. What is the barrier here is, I think, the learning curve to get started with OSGI. Given that documents and sample applications in OSGI is so limited.