Package names are used to allow similarly named methods to be properly referenced. For example, CA could produce a class named Address. There is nothing to prevent you from creating a class by the same name. But by declaring a package name, such as com.ca.gen, when the class is defined, the effective class name becomes com.ca.gen.Address.
Although most situations do not require that you set the Java package name for your application(s) in your CA Gen model, you may find it useful to do so. By convention, the package name is the reverse of the customer's internet domain name. For example, www.ca.com would become com.ca.<facility-name>.
Note: If you use CBD techniques, you must set the Java package names in your models.
Package names can be specified at the business system and model levels. If no package name is specified at the business system level, the package name at the model level is used. If no package name is specified at either level, a version of the short model name that conforms to the rules listed below is used.
The following list describes the rules for package names:
|
Copyright © 2013 CA.
All rights reserved.
|
|