Hi, Is it possible that your instance is valid and immediately becomes invalid ?
If you're able to reproduce it, please open a jira issue. Regards, Clement On 24.06.2010, at 23:54, Joel Schuster wrote: > I believe that I've fixed this issue with a work around in my code. > > Oddly, the code worked... sometimes. Most of the time it did not. > > There must have been some kind of race condition in setting the @Property > members via setX() methods. > > I changed everything to using just @Property without the setX() methods and > then 'set' the methods within the @Validate method and everything works every > time. > > The WARNING has now also gone away. > > - Joel > > -----Original Message----- > From: Joel Schuster [mailto:[email protected]] > Sent: Thursday, June 24, 2010 3:22 PM > To: [email protected] > Subject: Issue with iPojo 1.6.2 > > Just upgraded to Felix 3.0.1 and iPojo 1.6.2 > > A component that was working stopped: > > [ERROR] com.navsys.boreal.utils.comms.serial.rxtx.SerialRxTx : The method > org.apache.felix.ipojo.util.callb...@1b67d6a does not exist in the > implementation class com.navsys.boreal.utils.comms.serial.rxtx.SerialRxTx > > Not as big a deal but I also use the following line: > > @Requires > private LogService logService; > > where LogService is a org.osgi.service.log.LogService. > > [WARNING] com.navsys.boreal.utils.comms.serial.rxtx.SerialRxTx : > [com.navsys.boreal.utils.comms.serial.rxtx.SerialRxTx.ad025360-3d9e-4f8d-92e8-f6969b174e70] > The dependency is not optional, however no service object can be injected in > logService -> org.osgi.service.log.LogService > > Any ideas of how to handle would be appreciated. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
