reta commented on a change in pull request #806:
URL: https://github.com/apache/cxf/pull/806#discussion_r673532326
##########
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:
> Just to avoid misunderstandings, did your tests involve any changes to
CXF (like using the property added in #827) or did it work for you out of the
box? IOW, could you reproduce my original problem at all?
I pulled your PR as-is, created a sample bundle to consume
`RestClientBuilderResolver` and played w/o `lazy` `cxf-rt-rs-mp-client` bundle
activation policy. I was not able to reproduce your original problem, once the
bundle is started, the service loader mechanism kicks in (with `lazy` and
`eager`).
> Looks like setting that to eager should do the trick.
Just leave it empty, like `<cxf.bundle.activation.policy />`, it will be
equivalent to eager activation.
> If it does, do you want me to amend my PR and use that property instead
of my header removal?
In general, yes, but it would be great to have reproducer for the problem,
to understand why it happens. If it is easier for you, we could get
capabilities merged (it is good addition) and troubleshoot the bundle
activation later on.
> Would be great to get rid of the CXF fork I have to use right now :)
Certainly eager to help you here.
Thanks!
--
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]
