On 18.05.2017 00:20, Andrew Guibert wrote:
Hi Alan, I've checked within IBM and it appears we do not have any OpenJDK
committers. Still trying to chase down if we have anyone in IBM who can
drive this commit. Do you know of anyone?
Hi Andrew,
you can find a list of JDK 10 Committers at
> From: Alan Bateman
> To: Andrew Guibert
> Cc: core-libs-dev@openjdk.java.net
> Date: 05/12/2017 04:02 AM
> Subject: Re: Proposal:
> javax.naming.spi.NamingManager.clearInitialContextFactoryBuilder()
>
> On 11/05/2017 22:25, Andrew Guibert wrote:
> Alan, could you p
On 11/05/2017 22:25, Andrew Guibert wrote:
Alan, could you please commit this patch for me? We've tested it
locally and all of the jdk_other tests pass with this change on jdk9.
93d92
< * Once installed, the builder cannot be replaced.
101d99
< * @exception IllegalStateException If a factory h
lready set");
<
Alan Bateman wrote on 05/10/2017 07:32:47 AM:
> From: Alan Bateman
> To: Andrew Guibert , core-libs-dev@openjdk.java.net
> Date: 05/10/2017 07:32 AM
> Subject: Re: Proposal:
> javax.naming.spi.NamingManager.clearInitialContextFactoryBuilder()
>
>
On 10/05/2017 14:33, Andrew Guibert wrote:
:
I need to check with my management to get all the legal approvals
before proposing a patch, so it might take a while. Since it's likely
a very small code change I won't be offended if someone else proposes
the patch for me =)
I don't see too ma
> From: Alan Bateman
> To: Andrew Guibert , core-libs-dev@openjdk.java.net
> Date: 05/10/2017 07:32 AM
> Subject: Re: Proposal:
> javax.naming.spi.NamingManager.clearInitialContextFactoryBuilder()
>
> On 08/05/2017 23:27, Andrew Guibert wrote:
>
> > :
> >
>
On 08/05/2017 23:27, Andrew Guibert wrote:
:
I am not sure why the "no resetting" restriction is on the NamingManager
API in the first place. Is anyone aware why the API has this restriction?
In any case, the solution outlined above seems rather messy (as it only
solves the problem by mitigati
Hi all,
I've been cleaning up code that I work on to be Java 9 compatible, but have
ran into a blocker due to limitations of the Naming API. I could work
around the blocker with an --add-opens, but I'd rather find a proper
solution.
*** Background
Currently the javax.naming.spi.NamingManager a
