| Previous | Table of Contents | Next |
A data provider exports the three services above. In addition, the data provider may need to locate a ResourceIDService to
translate standard URI’s to ResourceIDs (see the Data Access Interfaces chapter).
The data provider exports its three services by binding the respective objects in a CosNaming::NamingContext, which it implements
directly or creates within the CORBA Naming service implementation. It uses the same names as a client, given in the table
above.
The data provider obtains the ResourceIDService to translate standard URIs from this NamingContext. It does so by resolving
the following standard name.
The location of the NamingContext used must be configurable for each data provider. If the context contains multiple data
providers, then a different NamingContext will be used by each and the clients will use the NamingContext of a proxy data
provider (see the Proxies chapter).