The service interface represents the standard API. It is not necessary for clients to use reflection to find the methods of the service: they are compiled against the service interface.
However at runtime, the service implementation can change... so long as it provides the methods specified in the service interface. On Mon, Dec 9, 2013 at 12:54 PM, Snorre Lothar von Gohren Edwin < [email protected]> wrote: > 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 >
