Peaberry 1.2 not working in Karaf 2.2.4?

[Raman Gupta]

Trying to use Peaberry 1.2 in Karaf 2.2.4. It doesn't work when installing the Guice and AOP bundles into the Karaf environment as regular bundles. The Peaberry activator does run the configure() method of the modules, so the activator is working -- but the service consumer gets a org.ops4j.peaberry.ServiceUnavailableException when trying to access the service.

When installing the Guice and AOP bundles into the boot classloader as described here http://code.google.com/p/google-guice/wiki/OSGi, Peaberry does work properly, so this seems to be a classloader issue of some sort.When installing as regular bundles, I am not seeing any Exceptions in the log, including the ReflectUtils exception as described on the referenced page.

[Stuart McCulloch]

On 22 October 2011 18:07, Raman Gupta <rocke...@gmail.com> wrote:

Trying to use Peaberry 1.2 in Karaf 2.2.4. It doesn't work when installing the Guice and AOP bundles into the Karaf environment as regular bundles. The Peaberry activator does run the configure() method of the modules, so the activator is working -- but the service consumer gets a org.ops4j.peaberry.ServiceUnavailableException when trying to access the service.

Can you create a testcase that recreates this and attach it to a new issue?  Also which version of Guice are you using?

 

When installing the Guice and AOP bundles into the boot classloader as described here http://code.google.com/p/google-guice/wiki/OSGi, Peaberry does work properly, so this seems to be a classloader issue of some sort.When installing as regular bundles, I am not seeing any Exceptions in the log, including the ReflectUtils exception as described on the referenced page.

--
You received this message because you are subscribed to the Google Groups "Guice and OSGi" group.
To view this discussion on the web visit https://groups.google.com/d/msg/guice-osgi/-/nEKmVrbbGC8J.
To post to this group, send email to guice...@googlegroups.com.
To unsubscribe from this group, send email to guice-osgi+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/guice-osgi?hl=en.

--
Cheers, Stuart

[Raman Gupta]

On Saturday, October 22, 2011 7:50:22 PM UTC-4, Stuart McCulloch wrote:

On 22 October 2011 18:07, Raman Gupta <rocke...@gmail.com> wrote:

Trying to use Peaberry 1.2 in Karaf 2.2.4. It doesn't work when installing the Guice and AOP bundles into the Karaf environment as regular bundles. The Peaberry activator does run the configure() method of the modules, so the activator is working -- but the service consumer gets a org.ops4j.peaberry.ServiceUnavailableException when trying to access the service.

Can you create a testcase that recreates this and attach it to a new issue?  Also which version of Guice are you using?

Using Guice 3.0. 

In creating the test case I was able to isolate the cause -- my service bundle Module was:

bindService(ServiceImpl.class).export();

bindConfigurable(String.class).annotatedWith(named("configvalue")).from("service.pid").named("config");

but the config value "config" was not available in ConfigAdmin. However, there was also no place on ServiceImpl to inject the config anyway so it shouldn't have mattered.

In this case, it seems like Peaberry failed to create the service at all. I would have expected one of two things to happen -- either the bindConfigurable was ignored because the ServiceImpl had no place to inject the config value (like what seems to happen when guice is in the boot classpath), or that I would have seen some sort of Exception in the logs indicating that the bindConfigurable could not locate the config, and the bundle in that case would not have gone to STARTED state.

Before I create the issue I wanted to follow up on the list to verify my thinking about what should have happened here...

(The classloader thing was a red herring -- I think in the environment where I had guice loaded from the boot classloader, the service configuration value *was* defined, and so it worked there without any issue).

[Todor Boev]

Hi Raman,

The peaberry activation extension does not start your bundle until all
declared configurations are available. Therefore the bundle services
won't be exported and the bundle start()/stop() methods won't be
called until that condition is met. I am not sure how easy it will be
do detect if the configurable is not used anywhere in the module. I am
not sure if it is a good idea to add such validation unless it can
catch 100% of the cases. Otherwise we will give the users false sense
of security.

I am thinking about adding a timeout option after which the activation
fails with a BundleException. I can also add some java.util.logging
logs that tell how the activation proceeds.

Cheers,
Todor

> --
> You received this message because you are subscribed to the Google Groups
> "Guice and OSGi" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/guice-osgi/-/NydLP6lVr5oJ.

[Raman Gupta]

On Monday, October 24, 2011 3:33:20 AM UTC-4, Rinswind wrote:

I am thinking about adding a timeout option after which the activation
fails with a BundleException. I can also add some java.util.logging
logs that tell how the activation proceeds.

I created http://code.google.com/p/peaberry/issues/detail?id=68 to track this enhancement.

Regards,

Raman Gupta