Review beans that bind in JNDI to add a dependency on Naming

There are a number of services/beans that bind things in JNDI that just assume a naming server is available. This assumption is only valid because historically the local Naming server has been deployed in a "deployment phase" prior to when those services are deployed. A proper dependency should be declared to make server startup more robust.

The MC name of the bean to depend on is "LocalNamingBean" but IMHO we should give it a different name or an alias. Perhaps just "LocalJNDI". "JNDI" sounds tempting but some I think the name should make clear that no remote capability exists.