[
https://issues.apache.org/jira/browse/CXF-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647335#comment-16647335
]
Andriy Redko commented on CXF-7870:
-----------------------------------
Hi [~sarasota7], thank you for this issue, you are right, the usage of
JAXRSUtils is not justified in JAX-WS context.
> 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
>
> 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)
