Hello Aggelos,
Basically, I agree with what Niclas and Simon already said.
On Apr 21, 2007, at 3:15 , Aggelos Mpimpoudis wrote:
Continuing my exploration of OSGi, I found that
ServiceActivatorToolkit developed by BandXi would make my life
easier with the service registry and all the matters that come to
you, when you hear about a bundle that is importing services.
/*SAT, for those who never heard of it, is a part of OHF project
(dont know if it started as part of this project) (look it up, at
eclipse.org)*/
Would you encourage a new OSGi developer, to try SAT from his first
steps?
From a teaching point of view, I would first make sure developers
understand the dynamic nature of the service registry. Next step
would then be to introduce them to the service listener, followed by
the service tracker. Make them use those for a little while, giving
them some excercises. They will discover for themselves that these
become harder to use once the number of service dependencies increases.
Once they fully understand the problem, you can present them with
solutions (of which there are many):
- service binder;
- declarative services (R4 spec);
- dependency manager;
- iPOJO;
- SAT.
Is it safe to dump the servicetracker and switch to SAT method at
this early steps or would you suggest to keep on with the first?
Thank you very much in advance!
Just like Simon is a bit biased towards SAT probably, I'm more biased
towards the dependency manager (I wrote). The latter has been used in
several commercial projects already, where we have seen gains in
developer productivity because they did not need to worry about
"getting the dependencies right" (of course, they still need to be
very aware of the dynamic environment, you can't and should not try
to hide that).
Greetings, Marcel
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
