-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make replacement of cxf easier #203
Comments
I created an example implementation that works with my setup: schabe77@c27bb64 In this implementation cxf dependencies are only referenced in This implementation is also able to shutdown the client, what is good for jersey: jersey creates a thread "jersey-client-async-executor". When the client is not shut down properly this thread prevents the jvm shutdown for a while. This is the class that I could use as my own implementation of a HttpClientProvider:
|
Hi,
I try to get rid of BingAds's cxf dependencies.
CXF is not a good product. it's not thread safe, I get these exceptions from time to time:
and with the version 4.0.2 it also includes a vulnerability: CVE-2024-28752 8.3 Transitive Server-Side Request Forgery (SSRF) vulnerability with High severity found
I tried to exclude all artifacts of group
org.apache.cxf
and to use jersey instead. Unfortunately that doesn't work, becausecom.microsoft.bingads.HttpClientProvider
has direct (GZIPFeature) and indirect (CxfUtils) dependencies to CXF, which leads (when using spring) toI would be great, if you could get rid of the cxf-references at HttpClientProvider, so it's possible to remove all cxf dependencies
The text was updated successfully, but these errors were encountered: