Try OpenEdge Now
skip to main content
Open Client Introduction and Programming
Generating Proxies and Web Service Definitions : Object naming in ProxyGen : Naming side effects and restrictions

Naming side effects and restrictions

Automatic name conversions can cause two methods or parameters in the same namespace to acquire the same name, even when the original names in a procedure file are different. This also can occur if you have two procedure files with the same name under different directories. You can override method names in ProxyGen to handle method name conflicts, but you must change any conflicting parameter names directly in the procedure files, because you cannot customize parameter names in ProxyGen.
When ProxyGen generates an Open Client proxy or SOAP Web service definition, a separate .java file for Java proxies, a separate class (.cs) file for .NET proxies, and a separate <binding> element for Web service definitions is created for each AppObject, SubAppObject, and ProcObject. To avoid naming conflicts for all these object representations, ProxyGen does not allow you to generate if any two objects in the Open Client interface have the same name.
For example, if you have two persistent procedures with the same name but in different directories, you must customize the ProcObject name for at least one of these procedures, to prevent a filename conflict. You can do this by customizing one of the procedures and editing the name, or by including the relative path in the name. Similarly, you must ensure all your AppObject, SubAppObject, and ProcObject names are unique within a single Open Client interface.