You have to standardize your services and use as far as possible composition rather than inheritance. Start from the usage point of view (customer) rather than from your hardware (provider). You can also take a look to aspects.
JP [@@ OPEN @@] -----Message d'origine----- De : [email protected] [mailto:[email protected]] De la part de Snorre Lothar von Gohren Edwin Envoyé : lundi 9 décembre 2013 13:55 À : users Objet : Re: Reflection Ok I see where you are going with this. But what if one have a standard api with different hardware types behind, which have different methods that can be called. Im having troubles in seeing how this can be done dynamically? On Mon, Dec 9, 2013 at 1:51 PM, Neil Bartlett <[email protected]> wrote: > On Mon, Dec 9, 2013 at 12:44 PM, Snorre Lothar von Gohren Edwin < > [email protected]> wrote: > > > Is reflection the way to go to handle a dynamic OSGi environment > > > No. > > > > or are > > there other customs or patterns to use? > > > > SERVICES! :-) > > > > In other words, is this heavily used in OSGi? > > > > No. > > > > > > -- > > Mvh > > Snorre Lothar von Gohren Edwin > > MeetMe: http://doodle.com/vonGohren > > +47 411 611 94 > > > -- Mvh Snorre Lothar von Gohren Edwin MeetMe: http://doodle.com/vonGohren +47 411 611 94 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
