OK. Thanks, Colm. Let's release a new version with this fix.
On Fri, Nov 27, 2020 at 2:38 PM Colm O hEigeartaigh
wrote:
> Hi Jim,
>
> My opinion is it's not necessary to add an update note for a regression
> bug. Let's instead just release a new version before the end of the year
> with the
Hi Jim,
My opinion is it's not necessary to add an update note for a regression
bug. Let's instead just release a new version before the end of the year
with the fix, so users can upgrade to that version instead if they are
using CXFAuthenticator.
Colm.
On Thu, Nov 26, 2020 at 1:53 AM Jim Ma
Hi Colm,
Just to add more things, if cxf client with CXFAuthenticator is running in
a container(tomcat,glassfish, wildfly or osgi container karaf ?) , the
upgrade
will get this not working. I already fixed this issue
https://issues.apache.org/jira/browse/CXF-8378 in master and 3.3.x branch.
Where
Hi Colm,
I think this commit [1] caused the regression. We have some tests for
CXFAuthenticator in CXF, but they are running
with the single "flat" classloader and don't throw this exception.
[1]
https://github.com/apache/cxf/commit/58539be7c6367b0e7db354cd90467fe006ddef57
Cheers,
Jim
On Fri,
Hi Jim,
Do you know which CXF commit caused the regression. Do we have no tests for
CXFAuthenticator?
Colm.
On Fri, Nov 20, 2020 at 11:19 AM Jim Ma wrote:
> When upgrade cxf to 3.3.8/3.4.1, the cxf client with
> CXFAuthenticator throws NoClassDefFoundError like following :
>
When upgrade cxf to 3.3.8/3.4.1, the cxf client with
CXFAuthenticator throws NoClassDefFoundError like following :
java.lang.NoClassDefFoundError: org/apache/cxf/common/util/ReflectionUtil
at
org.apache.cxf.transport.http.ReferencingAuthenticator.tryWith(ReferencingAuthenticator.java:125)
at
