I prefer the NetBeans module system to OSGi. OSGi is not the only viable modular system for Java!
@Mirko,
"it is funny to read that even Java savvy people have problems wrapping their head around the concepts of OSGi"
<[...]Some of the questions listed above may actually kill an OSGi-based project when the business case for using OSGi is not well-grounded. However, so[...]
Hi Adam,
I am interested in point 9 JPA.
If I have a module with JPA entities, how can I deploy this module in different version[...]
The question behind OSGi and modularity in general is not about technical issues, It's all about the famous "Time to market".
Y[...]
(I realise in the previous comment, the phrase "incantation to the OSGi fairies" sounds rather cavalier. The point is that to our plug[...]
Frankly, we've just included OSGi for two very simple reasons:
1) It's actually pretty easy and integrates well with the Maven build process<[...]
Hi Adam,
it is funny to read that even Java savvy people have problems wrapping their head around the concepts of OSGi. It is true that i[...]
Hi Phil,
I'm glad, that you only disagree with the introduction to this post :-)
Enforcing IoC during the build process may be t[...]
"it is right now (future may change it) the only viable way to split your application into modules with well-defined dependencies"
[...]