[ https://issues.apache.org/jira/browse/CXF-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664731#comment-16664731 ]
Freeman Fang commented on CXF-7361: ----------------------------------- Hi Romain, I'm a little bit confused. Currently CXFAuthenticator just use Classloader defineClass, but you mentioned {code} unsafe should be used to define the class instead of the failing ClassLoader.defineClass. {code} when you reported this problem. Could you please elaborate it? Thanks! Freeman > Java 9 support for CXFAuthenticator > ----------------------------------- > > Key: CXF-7361 > URL: https://issues.apache.org/jira/browse/CXF-7361 > Project: CXF > Issue Type: Improvement > Affects Versions: 3.1.11 > Reporter: Romain Manni-Bucau > Assignee: Freeman Fang > Priority: Major > > with java 9, Authenticator getDefault() should be used instead of field.get() > (setAccessible fails) + unsafe should be used to define the class instead > of the failing ClassLoader.defineClass. > All that with reflection of course and in fallback mode probably since for > java 8 it is better to not do it (or it is not available - getDefault() > typically). > Workaround ATM is to call CXFAuthenticator.addAuthenticator(); manually and > ignore the exception, it initializes the instance then it doesn't fail but > the feature is lost until it gets fixed as mentionned before. -- This message was sent by Atlassian JIRA (v7.6.3#76005)