Hello Oliver,
"Don't program to the OSGi api" !!!
What do you mean by that?
In our very first osgi steps my team and I had made more often this mistake. In my solid experience you have to use (micro) Services (declarative services, blueprint, ...) directly !
I have several years of OSGi experience and developed some projects from scratch using it. I am using DS since it was introduced. Never used the blueprint before, I wonder what its benefits are.
You can start with your "non-osgi" application, launching an embedding osgi framework (see core spec) and aggregating the first parts into a service/component approach, step by step.
That was the plan. Put everything into one bundle and start up the application. If its still running and behaving like it did before start to carve out small parts into OSGi services. Like Peter suggested.
Lately I have been doing this technique successfully many times. Good luck from germany,
And greetings back ;) Cheers, Phil _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
