This chapter provides release notes for Oracle Communications Design Studio for ASAP.
Table 2-1 lists the Design Studio ASAP release 7.3.5 fixes and provides a brief description of the resolution.
Table 2-1 Fixes in Design Studio Release 7.3.5 ASAP
| Service Request (SR) Number | BugDB Number | Description |
|---|---|---|
|
SR:3-13237154481 |
24753204 |
A new field, Compound Parameter Identification Token, now appears on the Project editor Locations tab. Use this field to identify the logic necessary to read compound parameters. You use an existing field, Indexed Parameter Identification Token, to identify the CSDL label suffix pattern for Indexed type parameters. When importing projects from previous Design Studio versions, both of these fields are defined with the Indexed Parameter Identification Token field value. When you create new projects, both of these fields are initially defined with the [] Square Brackets value. Also, a new field, Index Parameters Default Suffix, now appears on the Oracle Design Studio Activation Preferences page. When enabled, the CSDL label suffix value for Indexed type parameters is defaulted with ++ in the generated ASADL.xml file for all the projects in the workspace. |
This section describes existing software problems and any workarounds recommended to avoid the problems or reduce effects:
BugDB: 21694483
Activation test cases fail intermittently (over VPN and when not using VPN) when running Design Studio 7.x versions with ASAP 7.x versions.
To work around this problem, add the following to the eclipse.ini file: "-Dweblogic.corba.client.bidir=true"
BugDB: 22960169
Users are unable to establish a connection to Oracle WebLogic Server through the NEP map option (NEP deploy fails intermittently).
To work around this problem, do the following:
Ensure that the base cartridge project (the source project that contains the NEs) is in an open state.
Ensure that the META-INF/activation-model.xml file has been generated, or complete a full clean and build to regenerate the activation-model.xml file.
NEP deploy fails intermittently if the activation-model.xml file corresponding to the mapped NE has not been generated and saved to the cartridgeBin/cartridgeBuild location.