You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HttpClientHTTPConduit never gained any real traction within Quarkus CXF. When CXF started using it as a default, we were forced to introduce our own default (URLConnectionHTTPConduitFactory) to avoid bugs like #992, CXF-8885, CXF-8951, CXF-8946, CXF-8903 and possibly others.
Now that we have VertxHttpClientHTTPConduit that we can support very well on Quarkus, there are no more reasons for us to spend resources on HttpClientHTTPConduit.
We should mark it as deprecated in our documentation, add some warnings on startup for the case that somebody is still using it
The text was updated successfully, but these errors were encountered:
ppalaga
added a commit
to ppalaga/quarkus-cxf
that referenced
this issue
Dec 2, 2024
HttpClientHTTPConduit
never gained any real traction within Quarkus CXF. When CXF started using it as a default, we were forced to introduce our own default (URLConnectionHTTPConduitFactory
) to avoid bugs like #992, CXF-8885, CXF-8951, CXF-8946, CXF-8903 and possibly others.Now that we have
VertxHttpClientHTTPConduit
that we can support very well on Quarkus, there are no more reasons for us to spend resources onHttpClientHTTPConduit
.We should mark it as deprecated in our documentation, add some warnings on startup for the case that somebody is still using it
The text was updated successfully, but these errors were encountered: