Re: Accessing an osgi service interface from another bundle

2014-03-13 Thread vs_mahesh
Hi Marco, The issue is that the package name is not getting resolved in the second bundle. ie when I try to import com.outotec.uom.mapping*;Its not getting resolved. What I need is that I need to call the function in com.outotec.uom.mapping.MappingInterface. So how can I make the interface packag

Re: Accessing an osgi service interface from another bundle

2014-03-13 Thread vs_mahesh
Hi Raul, The package name com.outotec.uom.mapping.*, is not getting resolved in the second bundle. How can I make it accessible in the second bundle . Thanks - Thanks And regards, Mahesh -- View this message in context: http://camel.465427.n5.nabble.com/Accessing-an-osgi-service-interface

Re: Accessing an osgi service interface from another bundle

2014-03-13 Thread Marco Westermann
Hi Mahesh, bundle 1 looks good so far. in your second bundle do the following: ad an instance variable to your bean which is of type of the interface like: class mypgm { private com.outotec.uom.mapping.MappingInterface mappingService = null; // here getter + setter for mappingService } then

Re: Accessing an osgi service interface from another bundle

2014-03-13 Thread Raul Kripalani
If Spring DM is able to resolve the OSGi reference correctly, 'mappingservice' becomes a local bean in the Spring Context of the second bundle. This means that you can inject it around like any other bean. For example: ... provided that com.ab.mypgm has a setter for property