A 'code smell' in the 'fart sensor impl' LOL!! This stuff is hilarious! :)
-Stijn -----Original Message----- From: Dave Smith [mailto:[email protected]] Sent: zondag 8 december 2013 16:21 To: [email protected] Subject: Re: Instance reference issues My guess is that the fart sensor component is not setup a immediate , so when it is not required it is deactivated and then reactivated when required. Thus the different instances .. otherwise you have a code smell.... On Sun, Dec 8, 2013 at 9:44 AM, Snorre Lothar von Gohren Edwin < [email protected]> wrote: > Hi, im currently developing with DS optional dynamic configurations. > Im experiencing reference issues which have bubbled down in my application. > Meaning that it holds different instances of the service. > > Providing problems around in the application. > > Example: > At first initiation this is passed around: > fartsensordriver.impl.FartSensorImpl@5cc91eb1 > > At reinitiation when the service arrive again, this is passed around: > fartsensordriver.impl.FartSensorImpl@237098e7 > > This is ofcourse very logical and understandable. > But im having problems in handling this issue. > > So my question is, are there any patterns or something that exists to > handle this issue? > I believe there is but I would like to ask the experienced OSGi developers. > > > > -- > 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]
