reta commented on a change in pull request #806:
URL: https://github.com/apache/cxf/pull/806#discussion_r671849724
##########
File path: rt/rs/microprofile-client/pom.xml
##########
@@ -185,6 +185,26 @@
<scope>test</scope>
</dependency>
</dependencies>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.felix</groupId>
+ <artifactId>maven-bundle-plugin</artifactId>
+ <configuration>
+ <instructions>
+
<_removeheaders>Bundle-ActivationPolicy</_removeheaders>
Review comment:
Hey @brevilo , sorry for the delay, but I managed to look at the issue
with activation policy. There are a few interesting findings with respect to
bundle activation policy and Aries SPI Fly. I will try to summarize them here,
my apologies if I repeat the things you have already mentioned / knew about:
> Lazy Activation Policy: A lazy activation policy indicates that the
bundle, once started, must not be activated until it receives the first request
to load a class.
(https://docs.osgi.org/specification/osgi.core/8.0.0/framework.lifecycle.html#i3270439)
Basically, the important thing in our context is `... once started ... `
because Aries SPI Fly will be tracking all bundles in STARTING or ACTIVE
(started) state:
https://github.com/apache/aries/blob/trunk/spi-fly/spi-fly-core/src/main/java/org/apache/aries/spifly/BaseActivator.java#L97.
From all the tests I have done (I have used Apache Karaf 4.3.2), the consumer
was able to properly find
`org.eclipse.microprofile.rest.client.spi.RestClientBuilderResolver` service(s)
once the `cxf-rt-rs-mp-client` is started / starting.
May be you could share the sample project to look at with respect to lazy /
eager activation policy? In any case, I have added
`cxf.bundle.activation.policy` to allow activation policy overrides:
https://github.com/apache/cxf/pull/827.
Thank you.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
