Defining Design Studio Activation Preferences

To define activation preferences, from the Window menu, select Preferences, then expand Oracle Design Studio in the Preferences navigation tree, and then select Activation Preferences.

Field	Use
Allow NE Template Deployment	Select this check box to cause Design Studio to generate artifacts for NE templates and package them in the .sar file. If this check box is not selected, NE Templates will not appear as an available option in the Activation Project editor Packaging tab. This check box is selected by default.
Service Model Package Format	These options determine how the XML files are generated when the activation cartridge is built. Do one of the following: Select Single file per type if you would like all of the service actions to be packaged into the cartridgeBuild/ServiceModel/CommonService.xml file and all of the atomic actions to be packaged into the cartridgeBuild/ServiceModel/AtomicService.xml file. Select Single file per instance if you would like separate XML files for each of the atomic actions and service actions in the cartridgeBuild/model directory. The default option is Single file per instance.
Complex Type Delimiter	Enter the character to use to separate the parent and child elements of a "scalars" runtime-type parameter. Valid values are period (.), hyphen (-), and underscore (_). The default is underscore. See "Grouping Scalar Parameters using Structured Elements" for more information about scalars parameters.
Allow CSDL Label Overwrite	Select this check box if you want to be able to overwrite the CSDL labels (Service Action Label) for data schema elements. The Service Action Label field is available on the Activation tab of the data schema element. By default, this check box is not selected and, in this case, the Service Action Label field is read-only and is the same as the Atomic Action Label.
CSDL Primitive Type Merge Diagnostic Level	If two or more atomic actions are using the same data element name with a different type, and are contributing to a single CSDL, Design Studio attempts to resolve the primitive type merge for the data element in the CSDL. If Design Studio is unable to resolve the merge type, it diagnoses the issue as either an error or a warning. Do one of the following: Select Error. Select Warning. The default option is Error. The message is displayed in Design Studio Problems view.