Limitations of OSGi

Hello there again,

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...

Marco

Hm, I think this is a very broad question. It's like asking that what the limitations of Java are.

It would be better if you give some context.

I know this question is a bit vague. Unfortunately, as I don't know how OSGi works internally I can't even imagine any situations where it can't be used for any kind of application.

I just wanted to see if there are any well-known limitations to the OSGi approach for managing application modules...

Marco

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.