Class connectors do not honor server dictionary when resolving server class name
On the server, different classes of the same name may appear in multiple SymbolDictionaries on the user's SymbolList. The server resolution of a class name (for example, when compiling a method) searches the SymbolDictionaries in their order in SymbolList, and resolves the first class with that name that is found.
Creating a class connector to a class instance, when there are duplicate class names and the first one found with the SymbolList is not the intended target, should be possible by specifying the server dictionary name when creating the class connector. However, the specified dictionary was not used; class connectors always use the default GemStone lookup based on order in the SymbolList.
Last updated: 2/25/22