You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andriy Redko (JIRA)" <ji...@apache.org> on 2018/10/13 02:17:00 UTC
[jira] [Resolved] (CXF-7870) JAXRSUtils referenced in
AbstractBraveClientProvider
[ https://issues.apache.org/jira/browse/CXF-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andriy Redko resolved CXF-7870.
-------------------------------
Resolution: Fixed
> JAXRSUtils referenced in AbstractBraveClientProvider
> ----------------------------------------------------
>
> Key: CXF-7870
> URL: https://issues.apache.org/jira/browse/CXF-7870
> Project: CXF
> Issue Type: Bug
> Components: Tracing Brave
> Affects Versions: 3.2.6
> Reporter: sarasota7
> Assignee: Andriy Redko
> Priority: Major
> Fix For: 3.3.0, 3.2.7, 3.1.18
>
>
> Hello,
> We are using cxf for its web service (WS) components (not RS), along with brave tracing, i.e.,
> cxf-rt-frontend-jaxws
> cxf-rt-transports-http
> cxf-core
> cxf-rt-ws-policy . and
> cxf-integration-tracing-brave.
> When the call stack references AbstractBraveClientProvider (from an instantiation of BraveClientFeature, which is used on the WS side), a "java.lang.NoClassDefFoundError" error is thrown because of a missing org/apache/cxf/jaxrs/utils/JAXRSUtils.
> If we include a jar that has JAXRSUtils, then we run into a bunch of catch 22 situations with the whole RS side of things. Did you really intend to include JAXRSUtils in the AbstractBraveClientProvider class? From the documentation, it looks like BraveClientFeature is only to be used on the WS side, and not the RS side, unless I'm missing something.
> [http://cxf.apache.org/docs/using-openzipkin-brave.html]
>
> Thanks
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)