Proposal: javax.naming.spi.NamingManager.clearInitialContextFactoryBuilder()

[Andrew Guibert]

> From: Alan Bateman <Alan.Bateman at oracle.com>
> To: Andrew Guibert <aguibert at us.ibm.com>
> Cc: core-libs-dev at 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 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 has already been
installed.
> 109,111d106
> < if (object_factory_builder != null)
> < throw new IllegalStateException("ObjectFactoryBuilder already set");
> <
> 739,740c734
> < * the security manager to do so. Once installed, the builder cannot
> < * be replaced.
> ---
> > * the security manager to do so.
> 747d740
> < * @exception IllegalStateException If a builder was previous installed.
> 754,757d746
> < if (initctx_factory_builder != null)
> < throw new IllegalStateException(
> < "InitialContextFactoryBuilder already set");
> <
> I assume you will be able to get an IBM contributor to sponsor this.
> It will need an issue in JIRA and tests. All API changes for Java SE
> 10 and beyond will be reviewed by the CSR group [1], that process
> will be opening soon.
>
> -Alan
>
> [1] https://wiki.openjdk.java.net/display/csr/Main

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?

Also, you mentioned adding this API change to Java SE *10*.  Are we past
the cutoff for making changes in JDK 9?  I was hoping this (and a handful
of other proposals I have brewing) could be made for JDK 9.  If not, we're
going to be stuck using the JVM options for the lifetime of JDK 9.