-
1. Re: Class Hierarchy not working with Blueprint
ulrichromahn Nov 5, 2012 4:20 PM (in response to charlie7)Hi Charlie7,
I don't think anybody will be able to help you without getting a few details about your project.
- Would it be possible to post or attach the entire stack trace?
- Could you post or attach the MANIFEST.MF files from both bundles?
The reason for your issue could be related to some generic OSGi issues and may have nothing to do with Blueprint.
-
2. Re: Class Hierarchy not working with Blueprint
thomas.diesler Nov 6, 2012 10:20 AM (in response to ulrichromahn)Yes this sounds like a generic OSGi issue. If the abstract thing is supposed to be private to the service thing - it needs to be embedded witht the appropriate Bundle-Classpath set. If it is intended to be shared it needs to export some package capability (i.e. Export-Package: some.package.other.than.the.service.package) - the service bundle then needs to have a package requirement (i.e Import-Package: some.package.other.than.the.service.package)
-
3. Re: Class Hierarchy not working with Blueprint
charlie7 Nov 6, 2012 5:21 PM (in response to thomas.diesler)yes . that was the issue
Both the projects , interfaces and the one with abstarct classes were having the same package structure. (com.link.si.services)
After changing them and the Export-Package structure its working now.
Thanks Thomas