Customer is looking for the ability to alter JNDI bindings at runtime without necessarily forcing a restart/reload. Very similar to https://issues.jboss.org/browse/WFLY-3239.

Customer provided a quick list of use cases where this capability would be an enabling feature:

"Per our discussion some use cases of dynamic application reconfiguration that might be served by modifying JNDI at runtime include:

1) Dynamic network service endpoint reconfiguration, based on versions or demand (that is in essence what the developers are hoping to use this for)
2) Application-level feature toggles
3) Facilitation of canary and A/B testing

From our perspective we expect these capabilities to be used much more widely in the future. There are certainly other ways of achieving those capabilities, but JNDI is in our opinion a valid way."

*
SCOPE CLARIFICATION AS DECIDED IN THE CUSTOMER RFE (See Cloned Link below):
This RFE is limited in scope to naming bindings that are included by the user in the persistent configuration of the naming subsystem, and other JNDI bindings (e.g. those created by other subsystems, deployment unit processors etc) are out of scope.*