Re: Injecting BundleContext Issue
Looks like I have to also use the @Immediate annotation for BundleContext to be injected. -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Injecting BundleContext Issue
Hello, I am having trouble injecting BundleContext into my service class object. It appears that the BundleClassLoader for my class got swapped out at some point by the BundleContextImpl back to the ContextFinder. So when it is time for the component to be created and fields to be injected, the ContextFinder does not have the correct BundleClassLoader to resolve to the BundleContext. Has anyone seen this? I am using the snapshot 1.0.0-SNAPSHOT version but also see this in 1.0.0.RC2. Is there a workaround for this? Or Am I doing something wrong? Thanks, Tyler -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Failed to load PAX CDI 1.0.0-SNAPSHOT feature
Hi Grzegorz, Thank you for making it happen so quickly. I appreciate it.! Tyler -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Failed to load PAX CDI 1.0.0-SNAPSHOT feature
Hello, I am looking to try out PAX-CDI 1.0.0-SNAPSHOT since it got a few fixes from 1.0.0.RC2 but having problem loading it. The feature indicates that it is using karaf.feature v1.5.0 schema but Karaf 4.1.4 (which PAX CDI depends on) still supports up to v1.4.0. I also tried it out on ServiceMix 7.0.1 with same schema issue. Any reason to update to 1.5.0 schema for the feature.xml? Any recommendation how to work around this? Thanks, Tyler -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.