Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Subject: Re: Java 9 java.net.Authenticator api change
To: dev@cxf.apache.org
References: <OFBAF6863B.90471383-ON00258123.00797B31-86258123.0079AE9B@notes.na.collabserv.com>
From: Sergey Beryozkin <sberyozkin@gmail.com>
Message-ID: <b0b9bba0-9347-60a6-e061-9326e890c52d@gmail.com>
Date: Thu, 18 May 2017 09:58:18 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <OFBAF6863B.90471383-ON00258123.00797B31-86258123.0079AE9B@notes.na.collabserv.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
archived-at: Thu, 18 May 2017 08:58:37 -0000

Hi

Request for Option2 (or something similar like clone()) is more likely 
to be accepted IMHO

Cheers, Sergey
On 17/05/17 23:09, Adam T Anderson wrote:
> 
> 
> Hello,
> 
> In CXF we use org.apache.cxf.transport.http.ReferencingAuthenticator to
> create a chain of org.apache.cxf.transport.http.CXFAuthenticators.
> Every time we add a new CXFAuthenticator we set the new link as the default
> authenticator and link to the old head. This is so we can delegate the
> static call Authenticator.requestPasswordAuthentication() to a non-static
> list of instances of CXFAuthenticator.
> 
> When Authenticator.requestPasswordAuthentication() is called, the JDK pass
> es in the requesting host, port, protocol, scheme etc... which get set as
> private variables on the current head ReferencingAuthenticator and then
> ReferencingAuthenticator.getPasswordAuthentication() gets called.
> ReferencingAuthenticator.getPasswordAuthentication() uses deep reflection
> to copy the private non-static variables of java.net.Authenticator from the
> head to each link in the chain before calling getPasswordAuthentication()
> on each of the wrapped CXFAuthenticators.
> 
> This will no longer work in Java 9 with the new jigsaw module changes. We
> need a mechanism in Java 9 to copy those private variables from one
> authenticator to another for our Authenticator chain to work.
> 
> The 2 options I see are:
> 
> 1. Request Oracle to add setter methods for each variable (there are
> already getters) to the Authenticator API.
> 2. Request Oracle to add a "copyState" method to the Authenticator API
> which copies all private non-static variables of one Authenticator to
> another.
> 
> Right now I am leaning towards options #2.
> 
> What are your thoughts? Are there any other options to make this work with
> Java 9?
>