function placeControlAt(oDomRef, oControl) {
		assert(typeof oDomRef === "string" || typeof oDomRef === "object", "oDomRef must be a string or object");
		assert(oControl instanceof Interface || BaseObject.isObjectA(oControl, "sap.ui.core.Control"), "oControl must be a Control or Interface");

		if (oControl) {
			oControl.placeAt(oDomRef, "only");
		}
	}
Retrieves a resource bundle for the given library and locale.

If only one argument is given, it is assumed to be the libraryName. The locale
then falls back to the current {@link module:sap/base/i18n/Localization.getLanguage session locale}.
If no argument is given, the library also falls back to a default: "sap.ui.core".

<h3>Configuration via App Descriptor</h3>
When the App Descriptor for the library is available without further request (manifest.json
has been preloaded) and when the App Descriptor is at least of version 1.9.0 or higher, then
this method will evaluate the App Descriptor entry <code>"sap.ui5" / "library" / "i18n"</code>.
<ul>
<li>When the entry is <code>true</code>, a bundle with the default name "messagebundle.properties"
will be loaded</li>
<li>If it is a string, then that string will be used as name of the bundle</li>
<li>If it is <code>false</code>, no bundle will be loaded and the result will be
    <code>undefined</code></li>
</ul>

<h3>Caching</h3>
Once a resource bundle for a library has been loaded, it will be cached by this method.
Further calls for the same library and locale won't create new requests, but return the already
loaded bundle. There's therefore no need for control code to cache the returned bundle for a longer
period of time. Not further caching the result also prevents stale texts after a locale change.

<h3>Asynchronous Loading</h3>
The asynchronous variant of {@link #loadLibrary} will evaluate the same descriptor entry as
described above. If it is not <code>false</code>, loading the main resource bundle of the
library will become a subtask of the asynchronous loading of the library.

Due to this preload of the main bundle and the caching behavior of this method, controls in
such a library still can use the synchronous variant of <code>getLibraryResourceBundle</code>
in their API, behavior and rendering code. Only when the bundle is needed at module execution
time (by top level code in a control module), then the asynchronous variant of this method
should be preferred.

@param {string} [sLibraryName='sap.ui.core'] Name of the library to retrieve the bundle for
@param {string} [sLocale] Locale to retrieve the resource bundle for
@param {boolean} [bAsync=false] Whether the resource bundle is loaded asynchronously
@ui5-omissible-params sLocale
@returns {module:sap/base/i18n/ResourceBundle|undefined|Promise<module:sap/base/i18n/ResourceBundle|undefined>} The best matching resource bundle for the given
  parameters or <code>undefined</code>; in asynchronous case a Promise on that bundle is returned
@public
@deprecated Since 1.119. Please use {@link sap.ui.core.Lib.getResourceBundleFor Lib.getResourceBundleFor} instead.