Fails to start RMIConnectorServer if jdk.naming.rmi module is not observable

As described in javax.management.remote.rmi package summary, java.management.rmi supports both JNDI form and the encoded form of RMI connector addresses. So the support for JNDI form address is not optional.

However, if jdk.naming.rmi module is not observable, RMIConnectorServer will fail to start and its cause is:

Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or in an application resource file: java.naming.factory.initial
    at java.naming/javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:685)
    at java.naming/javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)
    at java.naming/javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:342)
    at java.naming/javax.naming.InitialContext.bind(InitialContext.java:417)
    at java.management.rmi/javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:713)
    at java.management.rmi/javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:496)
    ... 9 more

Is the JNDI form an optional part of java.management.rmi? Or should it?