Although EAServer supports the CORBA CosNaming interface to instantiate proxies in client applications, this technique is not recommended. You do not need to use the CosNaming API in clients to realize the benefits incurred by using logical component names. EAServer uses the CosNaming API to resolve component names in the implementation of the Session::lookup and Session::create methods. “Instantiating component proxies” describes the recommended technique for stub instantiation.
Unlike earlier releases, clients must be authenticated to perform name service lookups using the default EAServer 6.0 configuration. To enable name service lookups for clients that haven't been authenticated yet, you must set the minimumPasswordLength property for the default security domain to zero and set an empty password for the “guest” user. Sybase does not recommend this configuration, because allowing “guest” access could be a point of security vulnerability.
Use of the CosNaming interface also requires use of deprecated or unsupported SessionManager::Factory methods, in particular the create methods that take parameters. These methods are not compatible with Enterprise JavaBeans components with multiple create methods in the home interface. These methods are not supported for use in C++ or PowerBuilder clients.
