Hi David, Thanks for the heads up. One of the developers on the team was encountering this issues when the bundle first became active. If he stopped the bundle and the started it again, it would discover all of the services, so it sounds like this will address the issue. I just pulled the latest code from SVN and rebuilt it. We are in the process of doing some testing right now and do not want to introduce a new variable until we finish this. Once completed, we will deploy the new bundles and see if does address the issue we are encountering as well. Will let you know.
Thanks again. Regards, Todd -----Original Message----- From: David Bosschaert [mailto:[email protected]] Sent: Wednesday, May 06, 2009 7:01 AM To: [email protected] Subject: Re: dosgi - Problems with Client binding to more then one remote service Hi Todd, Just to let you know that I stumbled across some additional issues regarding consuming multiple remote services even in the non-spring DM case (sometimes it was only finding one). I've committed a fix for this just now, which should be in the 1.0 release when it's out or you can pick it up from the nightly snapshots from tomorrow... Cheers, David 2009/5/4 Nist, Todd (IHG) <[email protected]>: > > Hi David, > > Thanks a lot for taking the time to look into this and providing a interim > solution. I applied the recommended changes to my class for now and it is > working like a charm; this is a huge load of my mind. > > Again, thanks for the recommended solution and I will let you know if I find > out anything else on how to get it to work with pure Spring DM and the > osgi.reference tag. > > Regards, > Todd >
